Kanban is a method that doesn’t prescribe much at all.
In (simple) reality, there are only 3 main constructs to Kanban: A board, a Work-In-Progress limit (WIP), and a simple scheduling system. This doesn’t quite fit delivery planning and predictability in Agile software development and you can choose many other options.
If you have a fully robust and solid Scrum team, you may not want to go Kanban. So why is Kanban getting so much press these days? Would a fully complex development environment with all its issues and process needs go to a Kanban system?
Well, that’s what Peter Schuh asked a little while back, and found that his conversation opened him up to a newer realization: Kanban is great for n00bs (new Agile teams).
“Kanban is ideal for teams that have yet to take the agile plunge. Kanban is a quick hit of simple rules that fills a process void. For the uninitiated, Kanban is a grand welcome into the agile community. Many teams (although not all) can invest a little effort in Kanban and reap significant reward. Then the teams get comfortable and even excited about adopting additional agile practices.”
“Hey, wait. I don’t even know what Kanban is!” – Ok. You’re a noob.
- Go here for wikipedia answer.
- Go here for how to build a Kanban board.
- Go here for limitedWIPsociety’s answer.
- Go here for personalKanban’s answer.
- Go here for AgileScout’s Kanban board.
- Go here for 15+ Kanban tools list.
Sounds good to us. What are your thoughts?