Frontend Estimation: My Story of Delivering Tasks on Time
summary
Practical guidance on estimating frontend work and delivering tasks on time, focusing on real-world issues like hidden complexity when a small request (e.g., “add an icon”) expands into hours of code changes, library or framework swaps, or custom hacks. Covers causes of bad estimates, techniques to make better estimates and decisions under uncertainty, and advice for juniors and teams on handling tasks that are hard to evaluate until work begins.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:30Task estimation problem
- 4:04Why estimation matters
- 5:08Task estimation types
- 6:13Estimation error causes
- 8:41Learning to estimate
- 10:46Task detail tips
- 11:51Team task estimation
- 12:55Re-estimation practice
- 14:23Risky tasks and buffers
- 15:49Estimation factors
- 17:34Stats for improvement
- 20:44Communication and teamwork
- 21:27Productivity techniques
- 23:12Summary
- 23:55Q&A
related talks
07mThe art of precision: strategies and challenges of estimations...
01h 45mEstimates or NoEstimates
03h 00mBeyond Estimates (Estimates and NoEstimates ) - Let's Explore the Possibilities
29mUnreasonable Estimates and Improbable Goals
47mCreating efficient, accurate, software estimations
46mEstimates and complexity: a tale in 42 and a half minutes
29mSoftware estimation – embracing nuance and controlled chaos
31mI want to grab the next 23 minutes and 11 seconds to discuss time estimations