Kanban is a tool derived from Lean manufacturing and is associated with the branch of agile practices loosely referred to as Lean software development. Like a task board, Kanban visually represents the state of work in process. Unlike a task board, the Kanban constrains how much work in process is permitted to occur at the same time. The purpose of limiting work in process is to reduce bottlenecks and increase throughput by optimizing that segment of the value stream that is the subject of the Kanban. A principle difference between Kanban and Scrum is that Scrum limits work in process through timeboxing (i.e. the sprint) and Kanban limits work in process by limiting how much work may occur at one time (e.g. N tasks or N stories).

Related Articles

Why Should Scrum Teams Consider Kanban? [Agile Amped Podcast] A Very Agile Thanksgiving – Using Personal Kanban [Blog] Personal Kanban: One Coach’s Agile Journey [Blog]

What’s Next?

Turn words into action by taking an introductory course in Agile. Check out our upcoming Certified ScrumMaster training courses.