Cracking the WIP
summary
Compares single-piece flow to multitasking with a live marshmallow enactment and uses Little's Law plus Kanban principles to argue limiting WIP improves outcomes beyond raw speed. Shows microservices and smaller releases at the Financial Times cut complexity and risk, letting teams release multiple times a day and drive rollback rates down from 20% to 0.01%. Demonstrates shorter feedback loops, easier measurement, less rework and much lower stress for people doing the work.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:40Volunteers
- 2:30Context switching
- 4:00Volunteering
- 6:00Time
- 7:30Littles Law
- 10:00Complexity and risk
- 12:40Dealing with small problems
- 14:30Release
- 16:15Cost of delay
- 17:15Feedback loops
- 21:25Measuring delivery
- 23:20Delivering value early
- 24:10Uncertainty
- 24:35Opportunities
- 25:10Experience
- 29:00Achievement
- 30:05Stress
- 30:55Effects of Stress
related talks
30mHow to Visualize Impacts to Your Workflow & Metrics
33mTaming The Chaos: After The Quick Wins
50mHow Flow Works & Other Curiosities
30mTaming the Chaos: Beyond the Quick Wins
43mIt's a small world after all
50mHow Flow Works
29mHow thinking small is changing software development big time
34mFrom Waterfall To River – A Story Of Transitioning To Flow