Uploaded byAaron Sanders
A Kanban Primer
The document serves as a primer on the kanban methodology, emphasizing its origins in Japanese culture and core practices such as making work visible and managing flow through kanban boards. It discusses key concepts like work in progress limits, cycle times, and the identification of bottlenecks, while providing examples from organizations like Disneyland. Additionally, the document includes breakout questions for further discussion on the application and effectiveness of kanban.
A Kanban Primer
- 1.
- 2. Introductions Aaron Sanders Rally Software aaron@sanders.name JeffPatton AgileProductDesign.com jpatton@acm.org
- 3.
- 4.
- 5. Not a NewConcept
- 6. The Kanban conceptis common in Japanese culture
- 7.
- 8.
- 9.
- 10.
- 11. Building a KanbanBoard
- 12. Using a Kanbanboard
- 13. Display and managecycle times • Reduce WIP Limits • Reduce size of development items • Identify and act on bottlenecks immediatel Disneyland’s public display of current cycle- times by ride
- 14. Use cumulative flowdiagrams to visualize work in progress www.agilemanagement.net/Articles/Papers/BorConManagingwithCumulat.html 14
- 15. Use cumulative flowdiagrams to visualize work in progress • www.agilemanagement.net/Articles/Pa pers/BorConManagingwithCumulat.html 15 www.agilemanagement.net/Articles/Papers/BorConManagingwithCumulat.html
- 16. Shippable Items Aren’tWork items • Minimal Viable Product the smallest product that can generate value when shipped • Minimal Marketable Feature the smallest feature that customers and users would value • User Story or development item small, testable piece of working software, building it helps us learn
- 17.
- 18. Breakout questions picture ofa huddle or something Questions to answer in small groups - discussion + share-out When is OK to break the WIP limit What are the best ways to deal with the bottleneck? What happens when you ignore a bottleneck? Should every item be the same size? Where is Kanban appropriate? How do you know when you're done?
- 19.
- 20.