Taming The Chaos: After The Quick Wins
summary
Claims that shallow Kanban plateaus owe to visualizing alone and not addressing flow and handoffs and offers concrete fixes: adopt system thinking to map value streams and cross-team dependencies, add pull indicators or subcolumns and limit work in process to surface bottlenecks, change metrics so they reward throughput not local utilization, run cadenced standups and blameless retros that design an experiment to test fixes. Case notes: WIP limits and experiments shorten lead time and yield system-wide gains.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:35Embracing Reality
- 2:58The J Curve
- 4:06Getting Deeper
- 4:34The Initial Click
- 4:55Visualizing Work
- 5:28Limit Work In Process
- 6:18Focus On Continuous Improvement
- 6:54Getting Stuck
- 8:40Whats The bottleneck
- 9:44How can you go from shallow to deep
- 10:35Systems thinking
- 12:14Building relationships
- 13:39Visualization
- 15:32Measuring the wrong things
- 17:02Flow of customer value
- 17:44Antipatterns
- 18:51Pull
- 21:44Limit
- 24:02Dont Give Up
- 24:30Assess Improve
- 27:00Cast A Wide Net
- 27:46Focus On Outcomes
- 29:07Systemwide Improvements
- 30:36Tracking Progress
- 31:14Summary
related talks
30mTaming the Chaos: Beyond the Quick Wins
30mHow to Visualize Impacts to Your Workflow & Metrics
57mDon't Panic - how to get back into your learning zone!
47mHow it goes to heck in a handbasket
45mThe 7 Deadly Sins of Using the Kanban Strategy
42mObstacles & Patterns To Maximize Flow in IT Operations
35mCracking the WIP
01h 04mDevOps Kaizen: Empowering Teams to find and fix their own Problems