The Kanban method
Download as PPTX, PDF1 like718 views
Kanban is a pull-based system that uses signaling cards or mechanisms to limit work in progress (WIP) and avoid overloading a system. The Imperial Palace Gardens in Japan used a kanban system where visitors received admission cards that were returned upon departure to limit the number of simultaneous visitors. In software development, a virtual kanban system uses a card wall and WIP limits rather than physical cards to pull in new work only when there is available capacity. The main goals of kanban are to achieve sustainable pace, maintain good work-life balance, and enable continuous evolutionary change through visualization and explicit process policies.
The Kanban method
- 1. What is the Kanban method? Kanban - Chapter 2
- 2. Introduction: Trip to Imperial Palace Gardens • every visitor gets a card • on departure the cards are handed back • no money transfer is involved
- 3. Perception: Imperial Palace Gardens uses a Kanban System • restrict the quantity of visitors in the gardens • card available? → hand out a card • no card available? → visitors have to wait think beyond manufacturing with respect to kanban systems
- 4. What is a Kanban System?
- 5. Setup • a number of cards == agreed capacity of the system each card acts as a signaling mechanism
- 6. Rules for process flow • only if a card is available a new piece of work may be started • if there is no free card work must be queued until a card becomes available
- 7. Rules for process flow • each piece of work has a card attached • card remains attached while the work travels through the system • on work complete detach card and recycle card
- 8. Kanban is a pull system • work is pulled into the system when there is free capacity • work is not pushed into the system on demand • if the number of signal cards has been set appropriately, the system cannot be overloaded
- 9. In the imperial gardens example • the gardens are the system • the visitors are the Work In Progress (WIP) • the admission cards are the signal cards • the capacity is limited by the signal cards in circulation
- 10. Limiting the visitor count helps • maintain the gardens in good condition • avoid damage caused by too much foot traffic and overcrowding
- 11. Benefits • simple • cheap • easily implemented
- 12. Kanban applied in software development
- 13. Use a virtual Kanban system to limit WIP • there are cards used in most implementations • those cards are not the signal cards to pull more work • they represent the work items • there are no physical cards therefore it’s called virtual
- 14. The signal to pull new work is derived • check the current WIP • check the agreed capacity • subtract WIP from capacity • if the result is not null and positive • pull in new work
- 15. Card walls are commonly used • using a card wall doesn’t make the system kanban • it’s a means to track the flow of work inside a system • if there is no WIP limit and no signaling then the system is not a Kanban System
- 16. Main purpose of card walls • visually observe WIP • allow self-organization • allow to self-assign tasks • navigate work through the system • drop the need of dedicated management
- 17. Why use a Kanban system? • achieve a sustainable pace of development • maintain good work-life-balance for everybody involved • „Kanban is a catalyst for the emergence of a more agile organization through evolutionary cultural change“ (David J. Anderson)
- 18. Three basic principles 1. Start where you are right now. 2. Find consensus that everybody wants incremental and evolutionary change. 3. Honor the process in place as well as existing roles, responsibilities and job titles.
- 19. State of the art 1. visualize workflow 2. limit WIP 3. measure and manage flow 4. make process policies explicit 5. use models to recognize improvement opportunities
- 20. What Kanban is not • a software development lifecycle methodology • an approach to project management
- 21. Conclusion Kanban as a permission giver: • try Kanban • modify the underlying process • be different