Kanban 101 - 3 - Kanban Essentials
•
47 likes•8,092 views
Kanban 101 workshop by John Goodsen and Michael Sahota. This covers everything you will need to know to play Russell Healy's Kanban Game: visualizing the work, metrics, and creating explicit policies. Slides are available on request. Please email me.
![Core Properties of Kanban ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Kanban 101 - 3 - Kanban Essentials
Similar to Kanban 101 - 3 - Kanban Essentials (20)
More from Michael Sahota
More from Michael Sahota (20)
Recently uploaded
Recently uploaded (20)
Kanban 101 - 3 - Kanban Essentials
- 1. Kanban Essentials Michael Sahota & John Goodsen
- 5. Start with your value stream map
- 7. Visualize Work Across Specializations
- 10. Kanban Works for Any Project
- 11. MEASURE AND OPTIMIZE FLOW
- 13. Collect key metrics on card
- 14. Lead time at Disney World
- 15. Tell ‘em how long it will take Copywrite
- 16. Cycle Time – Remember Little’s Law?
- 17. Control Charts measure Cycle Time Avg. Cycle Time Normal Variation Let’s investigate!
- 18. Visualize metrics with Continuous Flow Diagram (CFD) WIP Cycle Time Problem
- 19. Real project: lot’s of WIP at start… Yikes!
- 20. … improvement later on WIP reducing
- 22. Classes of Service - Standard
- 23. Class of Service - Fixed Date
- 24. Class of Service - Intangible
- 25. Class of Service - Defects
- 27. Expedite if you must…
Editor's Notes
- A team that is truly following Kanban will exhibit these 5 core properties. An example of Model’s are concepts like Theory of Constraints, Systems Thinking, Understanding Variability as taught by Deming or the concept of “muda” from TPS TODO : These are already old - Incorporate David Anderson’s recent post resetting the conversation on the kanbandev list and re-stating the current set of properties as they’ve changed over the last couple years: Reference Material: - Kanban, pp 16-17 -
- Many Agile teams use some type of workflow visualizations using Stickies on whiteboards, cards on bulleting boards, etc. This in itself is not Kanban - it is merely a Visual Control System. Kanban requires that the team exhibit the core properties. At this point, we only talk about cards as user stories … it will evolve into a discussion of Classes of Services later.
- Many Agile teams use some type of workflow visualizations using Stickies on whiteboards, cards on bulleting boards, etc. This in itself is not Kanban - it is merely a Visual Control System. Kanban requires that the team exhibit the core properties. At this point, we only talk about cards as user stories … it will evolve into a discussion of Classes of Services later.
- References: Kanban, pp 70-71
- For purposes of this workshop, we will cover enough Classes of Service to play the game, but not get sidetracked into the differing work items within a class of service (for example - grain of sand, story, feature, epic) The four most typical classes of services are addressed slide by slide immediately following this intro slide: - Expedite - Fixed Delivery Date - Standard Class - Intangible Class References: Kanban pp124-128
- Use the example of the customer who decides to spend some money in the last quarter of the fiscal year. They’ve been delaying the purchasing decision, but now are ready to spend the money just as time runs out. If we cannot deliver in time, we lose the sales opportunity completely. The order is placed, but payment is contingent on delivering in the fixed timeframe. It must be fulfilled, delivered and invoiced before the time expires. Expedite gives us the ability to say “Yes!” in these difficult situations, but comes at a big cost to the rest of the organization: - Expediting increases work in process and increases lead times for other non-expedited orders. - Kanban enables us to make expedition a consciouse decision. References: