How long is a piece of string? Solving the conundrum of software estimation
summary
Compares common techniques — story points, spikes, Monte Carlo — and argues the single most important element is trust between tech and product. Tells a concrete failure: team estimates 6–12 months, CTO demands delivery by year end and adds four people, the product ships after massive overtime and most of the team leave within six months. Uses a card-sorting exercise and a coastline “bad step” example where routes turn out 50% longer or obstacles create 75–300% overruns.
AI-written summary · about
chapters (6)
- 0:00Introduction to software estimation
- 2:29Story of a failed estimation
- 5:20Common estimation techniques
- 8:11The no estimates movement
- 10:29Building trust in estimation
- 18:49Why estimation matters
related talks
11mThe key to solving the conundrum of software estimation
46mEstimates and complexity: a tale in 42 and a half minutes
05mHow lng is a Piece of String
47mCreating efficient, accurate, software estimations
58mThe State of NoEstimates
42mEstimates: Is There a Silver Bullet?
03h 00mBeyond Estimates (Estimates and NoEstimates ) - Let's Explore the Possibilities
41mI Estimate this Talk will be 20 Minutes Long, Give or Take 10 Minutes