OK...

They both have their place. Scrum had been more widely adopted than any other agile process. But Scrum isn't for every team. In my environment, it wouldn't work. We're not dedicated to a single project and interruptions and common. Kanban allows us to keep track of the big things and move stuff around when needed. One of the keys is to keep tasks small, no more than 16 hours. If we get an interruption that's going to take more than a couple of hours, we add it our Kanban board and move a current task into the "Blocked" column. We have a maximum of two tasks in the "Current column". There's no limit to Blocked or Backlog. And Backlog can be big items, then break them down when moving to Current.


Not sure if that answers your question.


>Not necessary. I took SCRUM Master training from Winnow Management back in 2009. I know the benefits of SCRUM - we've used it since then. I was interested in your personal perspective of using Kanban compared to the link I posted (since you have been using Kanban for some time now)