Download presentation
Presentation is loading. Please wait.
Published byMary Linscott Modified over 9 years ago
1
© AgiliX Agile Development Consulting 看, カン 板, バン Kan Ban 30 min intro Cesario Ramos
2
© AgiliX Agile Development Consulting
3
Focus on FLOW Cycle Time = Work In Progress Avg Completion Rate (Little’s Law)
4
© AgiliX Agile Development Consulting OverproductionDelayHand-offsTask SwitchingDefectsInventoryRelearning Seeing WASTE
5
© AgiliX Agile Development Consulting Why KanBan By reducing the WIP all kinds of WASTE will emerge. Bottlenecks in the process become clear. You’ll get an average cycle time. You’ll get an average wait time.
6
© AgiliX Agile Development Consulting Scrum v.s. KanBan Velocity Sprint WIP per sprint Roles Cannot change sprint. Item must fit in sprint Cycle Time No timebox WIP per state No Roles Can change at any time. No timebox…
7
© AgiliX Agile Development Consulting | | WIP and Cycle Time Source: M Griffiths
8
© AgiliX Agile Development Consulting | | Bottlenecks Source: M Griffiths
9
© AgiliX Agile Development Consulting
10
One metric to rule them all Lead Time = CycleTime * Work In Progress + Delay Between Sub-Processes
11
© AgiliX Agile Development Consulting Improve Kan Ban bottlenecks using A3 Lead Time gives us a clear indication for potential wastes. Analyze waste to determine current situation Specify future state Find root cause by walking the gemba Propose counter measures for attacking root cause. Make a plan. Sell it to management.
12
© AgiliX Agile Development Consulting 看, カン 板, バン Kan Ban 30 min intro
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.