What is Kanban and how does it relate to Agile?
|
2
|
The wikipedia articile doesn't really have much to say about the specific meaning of 'kanban' as applied to software development. I think THIS is one of the better introductions to Kanban and I wish that had been available to me when I started reading about it. There is a link to the Limited Wip Society site at the foot of that page, and that's very good for follow-up reading. |
||
|
|
|
1
|
Kanban may be considered a framework process similar to Scrum. Both do not imply any low-level development practices but in other hand give you some rules and practices for your management process. When I think of Kanban vs. Scrum the main difference is that Scrum is iterative and timeboxed, while Kanban relays on the flow of work. Both are good for running a project the agile way, but fit better in different contexts. Scrum is best for projects where it's easier to have some exact points in time to for example gather all stakeholders and the team in one place for a planning session or retrospective. After that you have a piece of time or delivering a package of what you've committed to. Kanban in other hand is focused on delivering single pieces whenever they're ready. So there are usually no official iterations. Development just flows and is best suited for collocated teams which prefer ad-hoc meetings culture and peer-to-peer communication. |
||
|
|
|
-1
|
http://en.wikipedia.org/wiki/Kanban Take a look at the papers in the External Links at the bottom of the page. |
||
|
|
