Wasteful Waste or Why Everything Is Usually So Slow in Development
summary
Explains why software delivery is slow by identifying concentric layers of waste — organizational, process, team, and technical — that reduce actual throughput. Uses numbers (ideal focus factor ~0.64 vs 0.1–0.2 in large dysfunctional organizations) and examples like meetings, poor facilities, heavyweight scrum ceremonies, long builds, defects and technical debt to quantify lost hours. Recommends measuring specific wastes, fixing the largest (organizational) issues first, and tracking real customer-facing delivery speed.
AI-written summary · about
chapters (17)
- 0:00Slow development intro
- 1:35Speaker background
- 6:51Measuring efficiency
- 17:27Focus-factor inefficiencies
- 19:56Waste types
- 24:52Org waste examples
- 30:04Scrum waste
- 31:09Team waste roles
- 35:44Technical waste effects
- 39:43Fighting waste for speed
- 46:04Honest efficiency metric
- 47:07Q&A
- 49:40Q&A
- 52:31Q&A
- 55:27Q&A
- 58:13Q&A
- 1:01:01Q&A
related talks
45mSoftware's Seven Deadly Wastes
45mAccelerating Software Delivery: Why Your Team Is Slowing Down
11mValue and waste in software engineering
30mThree value inhibiting dysfunctions of enterprise software development
52mUnderstanding UnHealthy Syndromes of Software Delivery
29mEconomies of Speed
47mMaster the 10x Delivery System for Superior Software Engineering
47mContinuous Deprovement will eat your product for breakfast