Work that hasn’t been deployed, shipped, or otherwise delivered to a customer has no real value. Value is only realized when the work is available for use by the customer. The naive assumption is that the more work in progress there is, the more work will get to ‘Done’. Yet evidence is to the contrary. More work in progress results in less work done. (See The Impact of Agile Quantified for more).
The use of a Kanban board is a simple way to help limit Work in Progress by having a column that visually displays the work that exists in that state, and setting a maximum limit of the quantity. The idea is that we shouldn’t start new work before the existing work gets to done. Once a column has a WIP limit and the column fills up, then we’re forced to move downstream to help get the most downstream work to truly done.
Over time, teams often reduce their WIP limit to improve flow. Each reduction will challenge the team to cross-skill and collaborate more.
Scrum by Example – The Story of an Incomplete Sprint
Resource Links:
- How to Set WIP Limits on Your Columns When You’re Just Getting Started
- Limiting Work in Progress (WIP) in Kanban
- Scrum With Kanban WIP Limits
- Why you should limit work in progress and stop multitasking
- WIP Limit Definition
See Also:
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.
