Many people interpret Kanban as a mechanical method that does not consider people. This is a mistake. Kanban prioritizes sustainability by limiting WIP (work in progress), which preserves people’s creative capacity to solve problems and propose systemic improvements.
Understanding the Zeigarnik Effect
The Zeigarnik effect explains that unfinished tasks are remembered more than completed ones, creating tension that is only released when the task is finished. This can lead to burnout if not managed well. Limiting WIP respects people’s autonomy, reducing overload and increasing productivity.
Benefits of WIP Limit
- Overload Reduction: Avoids task switching, allowing greater focus.
- Increased productivity: Facilitates a constant flow of work and learning.
- Cycle Time Reduction: Reducing delivery times and rework.
Practical Application
Setting and adjusting your WIP limit is crucial to optimizing your workflow. Experiment, measure, and adjust as needed to ensure your team maintains a healthy balance between capacity and demand.
Studies and Evidence
Several studies show that limiting WIP improves team efficiency and productivity. Simulations and analyses of real processes confirm the effectiveness of this practice, showing that teams with well-defined WIP limits perform better.
Conclusion
Kanban, with its emphasis on sustainability and workflow, values and respects people’s capabilities. Limiting WIP is a fundamental practice to ensure a productive and healthy work environment.
References:
- Anderson, David J. (2010). Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press. ISBN: 0984521402.
- Anderson, David et al. (2011). 'Studying Lean-Kanban Approach Using Software Process Simulation'. In: Agile Processes in Software Engineering and Extreme Programming. Ed. by Alberto Sillitti et al. Vol. 77. Lecture Notes in Business Information Processing. Springer Berlin Heidelberg, pp. 12–26. ISBN: 978-3-642-20676-4. DOI: 10.1007/978-3-642-20677-1_2.
- Birkeland, JørnOla (2010). 'From a Timebox Tangle to a More Flexible Flow'. In: Agile Processes in Software Engineering and Extreme Programming. Ed. by Alberto Sillitti et al. Vol. 48. Lecture Notes in Business Information Processing. Springer Berlin Heidelberg, pp. 325–334. ISBN: 978-3-642-13053-3. DOI: 10.1007/978- 3- 642- 13054-0_35.
- Burke, W. Warner. (2011). A perspective on the field of organizational development and change: The Zeigarnik effect. The Journal of Applied Behavioral Science, 47(2), 143-167.
- Cocco, Luisanna et al. (2011). 'Simulating Kanban and Scrum vs. Waterfall with System Dynamics'. In: Agile Processes in Software Engineering and Extreme Programming. Springer, pp. 117–131.
- Concas, Giulio et al. (2013). 'Simulation of software maintenance process, with and without a work-in-process limit'. In: Journal of Software: Evolution and Process 25.12, 1225–1248. ISSN: 2047-7481. DOI: 10.1002/smr.1599.
- Ikonen, M. et al. (2011). 'On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation'. In: Engineering of Complex Computer Systems (ICECCS), 2011 16th IEEE International Conference on, pp. 305–314. DOI: 10 . 1109 / ICECCS.2011.37.
- Middleton, P. and D. Joyce (2012). 'Lean Software Management: BBC Worldwide Case Study'. In: Engineering Management, IEEE Transactions on 59.1, pp. 20–32. ISSN: 0018-DOI: 10.1109/TEM.2010.2081675.
- Shinkle, C. M. (2009). 'Applying the Dreyfus Model of Skill Acquisition to the Adoption of Kanban Systems at Software Engineering Professionals (SEP)'. In: Agile Conference, AGILE '09. pp. 186–191. DOI: 10.1109/AGILE.2009.25.
- The-Kanban-Way (2011). Importance of Kanban work-in-progress (WIP) limits. URL: Importance of Kanban work-in-progress (WIP) limits (visited on 14/10/2013).
- Zeigarnik, B. (1927). Das Behalten erledigter und unerledigter Handlungen. Psychologische Forschung 9, 1-85.
