Uploaded byMichael Sahota
Kanban 101 - 3 - Kanban Essentials
The document outlines the essentials of Kanban, emphasizing the importance of visualizing workflow, limiting work-in-progress, and making policies explicit. It discusses techniques for measuring and optimizing flow using metrics and control charts, along with practical exercises to engage teams in enhancing their workflows. Key topics include establishing WIP limits, visualizing work across specializations, and communicating policies effectively within a team.
More Related Content
Similar to Kanban 101 - 3 - Kanban Essentials
Kanban 101 - 3 - Kanban Essentials
- 1. Kanban Essentials MichaelSahota & John Goodsen
- 2. Core Propertiesof Kanban Visualize Workflow Limit Work-in-Progress (already covered) Measure and Optimize Flow Make Policies Explicit
- 3.
- 4. EXERCISE How doyou visualize your work flow today?
- 5. Start with yourvalue stream map
- 6.
- 7. Visualize Work AcrossSpecializations
- 8.
- 9.
- 10. Kanban Works forAny Project
- 11.
- 12. Table Talk Whatkind of measurements and metrics do you use today?
- 13. Collect key metricson card
- 14. Lead time atDisney World
- 15. Tell ‘em howlong it will take Copywrite
- 16. Cycle Time –Remember Little’s Law?
- 17. Control Charts measureCycle Time Avg. Cycle Time Normal Variation Let’s investigate!
- 18. Visualize metrics withContinuous Flow Diagram (CFD) WIP Cycle Time Problem
- 19. Real project: lot’sof WIP at start… Yikes!
- 20. … improvementlater on WIP reducing
- 21.
- 22. Classes of Service- Standard
- 23. Class of Service- Fixed Date
- 24. Class of Service- Intangible
- 25. Class of Service- Defects
- 26.
- 27. Expedite if youmust…
- 28. EXERCISE What Policiesdo you have now? How do you communicate them with your team? What new Policies do you want to consider when you get back to work on Monday?
Editor's Notes
- #3 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 -
- #7 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.
- #8 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.
- #14 References: Kanban, pp 70-71
- #23 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
- #28 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: