Respect estimates
summary
Claims that estimates are random by design and that starting work is the only way to shrink variance; shows planning poker and story points map to time, not abstract complexity; reports a common empirical multiplier — actual work is often three times longer than initial estimates; points to sprint cadence, burn‑down gaming and Tetris scheduling as sources of waste; contrasts fixed‑price needs with everyday pointless estimating and recommends coarser sizes (1/2/3/∞), more discovery before estimating, and fewer, cheaper estimates.
AI-written summary · about
chapters (25)
- 0:00Welcome
- 1:50Monkey experiment flaws
- 5:02What is estimation
- 10:03Construction vs IT estimates
- 12:31Tools over repetition
- 13:57Business impact on estimates
- 15:19Berlin airport failure
- 16:03Management needs estimates
- 18:11Precision matters?
- 20:17Planning poker suffering
- 22:23Estimation value beyond Tetris
- 24:49Velocity in scrum
- 26:34Story points as time
- 27:41Alternatives to estimation
- 29:47No time for quality myth
- 31:52Ideal Sprint reality
- 33:18Burn down frustration
- 35:27Demos illusion
- 36:30Agile vs spiral models
- 38:38XP remains niche
- 40:01Time vs energy
- 42:36Q&A: Three-times rule
- 43:40Q&A: Gold plating
- 45:05Q&A: Trust and agile
- 46:33Q&A: KPIs illusion
related talks
51mRespect estimates
01h 45mEstimates or NoEstimates
46mEstimates and complexity: a tale in 42 and a half minutes
03h 00mBeyond Estimates (Estimates and NoEstimates ) - Let's Explore the Possibilities
42mBeyond Estimates (Estimates and "NoEstimates") - Let's Explore the Possibilities
45mBeyond Estimates
58mThe State of NoEstimates
47mCreating efficient, accurate, software estimations