Beyond WIP Limits (short version)
Limiting work in progress (WIP) is a concept widely popularized by Kanban, but in different forms it also exists in other agile approaches. Despite that, applying limits is a practice which many teams find either counterintuitive or non-value adding and eventually skip it. We should however start with answering a couple of basic questions. Why do we introduce limits in the first place? What do we get thanks to them? After all we don’t apply limits just to make our work less convenient, do we? The session will discuss limiting work in progress revealing a bit of mechanics of the concept and pointing false beliefs which we often embrace in software development teams. It will show how this mechanics can be exploited to improve our processes in both expected and unexpected ways. After the session you should be tempted to apply WIP limits in your process or, if they are already a part of the process, to adjust them accordingly. And most of all, you should know why and how limits are working, which will help you to make a decision when you should introduce them and how strictly a team should respect them.
Recomendados
Más contenido relacionado
Destacado
Destacado (17)
Más de Pawel Brodzinski
Más de Pawel Brodzinski (20)
Último
Último (20)
Beyond WIP Limits (short version)
- 1. Beyond WIP limits Pawel Brodzinski @pawelbrodzinski
- 5. Why?
- 7. That is so wrong
- 10. On a highway
- 11. In a call center
- 12. On a computer
- 13. Ball Flow Game
- 14. No WIP Limits
- 15. Using WIP Limits
- 16. Why something that intuitive seems so counterintuitive when we talk about management?
- 17. …and they lived happily ever after
- 18. WIP limits! 5O
- 21. Why?
- 22. Slack time
- 26. We don’t live in ideal world
- 27. Automation
- 28. Code quality
- 31. Slack time introduced by WIP limits drives continuous improvement
- 32. Help others
- 33. Learn
- 34. Do nothing
- 35. Takeouts
- 36. 100% utilization is a myth 1OO%
- 37. Introducing WIP limits results in improved efficiency
- 38. Slack time sets us on path of continuous improvement
- 39. Thank you Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski