So you think you can estimate? The lost art of useful estimates
summary
Estimates are unreliable by design: exact hours create unspoken deadlines and fail as complexity and unknowns grow. The session runs hands-on experiments — a bottle-volume guess (only 1 of 8 correct), a sliced-bread/zombie supply-chain role play and group relative-sizing — and promotes use relative sizing not absolute dates, observe velocity and adjust empirically, and stop promising calendar commitments up front. It teaches collaborative context-based estimation techniques and exercises to convert intuition into repeatable team data.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:57When can I have it
- 4:36The product
- 9:36The estimate
- 15:21The ingredients
- 16:59Time is no object
- 18:49Assumptions
- 25:59Project Managers
- 26:59Semantics
- 27:59What can it typically
- 28:59Can we estimate it
- 29:59Developers dont have control
- 30:59Collaborate
- 31:59Empirical
- 32:59Where do we start
- 33:59How much does it hold
- 34:59The fatal assumption
- 35:59The question
- 37:59The chicken egg
- 38:59Losing confidence
related talks
01h 45mEstimates or NoEstimates
29mSoftware estimation – embracing nuance and controlled chaos
47mCreating efficient, accurate, software estimations
46mEstimates and complexity: a tale in 42 and a half minutes
47m[Workshop] NoEstimates: Forecasting with Less Effort and More Accuracy
11mThe key to solving the conundrum of software estimation
54mEstimates – the Enfant Terrible of Software Development
17mDevelopers, Stop Estimating Your Tasks! #noEstimates