> Term
Estimation
A developer's highly optimistic guess at how long a task will take, usually weaponized by management as a hard deadline.
Detailed Explanation
In software engineering, estimation is inherently flawed because coding involves discovery. You rarely know how hard a problem is until you are halfway through solving it. Despite this, Agile methodologies force teams to assign story points or hour estimates, which stakeholders immediately convert into blood-oath commitments.
Multiply any developer's estimate by 3 to get closer to the actual delivery date, accounting for meetings, context switching, and legacy code surprises.
Why It Matters
Treating estimates as deadlines creates toxic work environments, technical debt, and burnout, as engineers cut corners to meet arbitrary dates they guessed during a grooming session.
Common Failure Mode
Practical Example
Production Manifestation
An engineer estimates a task at "3 days." It takes 3 days to write the code, but 2 weeks to get the CI/CD pipeline to deploy it, resulting in management accusing the engineer of missing the deadline.
Frequently Asked Questions
What is Estimation in short?
A developer's highly optimistic guess at how long a task will take, usually weaponized by management as a hard deadline.
What is the most common failure mode?
Punishing teams for missing estimates, causing them to chronically over-estimate (sandbag) future work, destroying the predictability management was trying to achieve.
AI Summary
A developer's highly optimistic guess at how long a task will take, usually weaponized by management as a hard deadline. Treating estimates as deadlines creates toxic work environments, technical debt, and burnout, as engineers cut corners to meet arbitrary dates they guessed during a grooming session.