Get the elephant off the road!
summary
Gets the central claim across: focusing on team flow yields enterprise predictability and replaces guesswork with data driven forecasting. Uses a road metaphor with concrete numbers — 100 km road, 50 km/h, theoretical 20,000 cars per hour versus congested 2,000 — and prescribes concrete practices: a two hours of recurring backlog refinement per week, a definition of ready, planning under 15 minutes per week, request‑intake “traffic light”, and a sliding dependency board; shows how uniform work sizes and team throughput produce usable forecasts.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:27Common organizational problems
- 3:59Road throughput analogy
- 8:18Two throughput strategies
- 11:28Request intake process
- 13:54Team estimation process
- 16:24Backlog refinement practices
- 20:59Predictable delivery
- 23:51Enterprise forecasting
- 24:36Excuses for poor flow
- 26:22Road maps vs release plans
- 29:10Managing dependencies
- 33:46Dynamic planning
- 35:08Where to start
- 37:23Q&A
related talks
45mHow to not shoot yourself in the foot with estimation
41mYour Project Behaves Like a Hurricane--Forecast It Like One
16mPractically predictable – Forecasting delivery when nothing is certai
43mPredictable Delivery
44mPredictably Agile
47mMap and Measure your way to Performance
47mCreating efficient, accurate, software estimations
44mCreating flow at Waters out of thin air