Estimates – the Enfant Terrible of Software Development
summary
The talk examines why effort estimates in software development are distrusted, identifying a key problem: single-number estimates are treated as commitments or plans without context. It explains how to produce better estimates that depend on the specific question being asked and reveals why estimated effort tends to increase as estimates become more precise.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 0:28Cost Estimates
- 1:30The Overestimation Book
- 2:51Why Do We Need Estimates?
- 5:28Why Do We Estimate?
- 13:29Understanding Together
- 16:48How Do We Arrive at the Estimate?
- 17:54What Is It That We Are Estimating?
- 18:43Why Do I Even Estimate?
- 24:33Effort or Duration?
- 26:13How Accurate Does It Need to Be?
- 27:48Faulty Estimates
- 33:23Formal and Informal Estimates
- 39:48The Cost-One Paradox
- 44:42The Rule of Thumb
- 46:00Gaps Between Parts
- 50:53Closing
related talks
46m¿Por qué estimamos tan rematadamente mal?
01h 32mNo Estimates?
11mThe key to solving the conundrum of software estimation
42mBeyond Estimates (Estimates and "NoEstimates") - Let's Explore the Possibilities
29mSoftware estimation – embracing nuance and controlled chaos
40mEstimations: from guessing to weighing in grams
17mDevelopers, Stop Estimating Your Tasks! #noEstimates
03h 00mBeyond Estimates (Estimates and NoEstimates ) - Let's Explore the Possibilities