Beyond Estimates (Estimates and NoEstimates ) - Let's Explore the Possibilities
summary
Claims that time/cost estimates are guesses that regularly mislead decision makers, illustrated by a 200‑developer project planned for three months that runs three years and burns tens of millions. Uses simple tools — Post‑it exercises and a stopwatch tic‑tac‑toe task — to show wide variability, queuing delays and hidden constraints. Proposes slicing work into discrete, cohesive pieces, delivering the 8020 8020 (tiny slices that prove value) and steering from feedback; gives a real case where one‑day slices start delivering ~€30k/week value.
AI-written summary · about
chapters (8)
- 0:00Introduction and personal background
- 15:01Why estimates fail in software
- 32:57The cycle of continuous no improvement
- 1:00:04What is an estimate really?
- 1:40:55Why we use estimates and their purpose
- 2:02:28Exercise: Estimating simple tasks
- 2:45:54Beyond estimates: A new approach
- 2:59:58Summary and Q&A
