Story Point Estimation Anti-Patterns

Story Point Anti-Patterns

Even experienced teams fall into estimation traps. Recognizing these anti-patterns early prevents dysfunction and keeps story points useful.

1. Velocity Gaming

Symptom: Estimates inflate over time. A story that would have been a 3 six months ago is now an 8.

Root cause: Management uses velocity as a performance metric, so the team learns that higher velocity = less pressure.

Fix: Never use velocity to compare teams or evaluate performance. Velocity is a planning tool, not a productivity KPI.

2. Anchoring Bias

Symptom: Whoever speaks first dominates the estimate. Junior developers defer to seniors.

Root cause: Estimates are discussed before individual assessment.

Fix: Use simultaneous reveal (planning poker). Ban estimate discussions before the reveal.

3. Precision Obsession

Symptom: The team debates whether a story is a 5 or a 6 for fifteen minutes.

Root cause: Using a linear scale or treating estimates as commitments.

Fix: Switch to Fibonacci scale. Remind the team that estimates are forecasts, not promises.

4. Individual-Based Estimation

Symptom: "Well, if Alice does it, it's a 3. If Bob does it, it's an 8."

Root cause: Estimating based on who will implement rather than inherent complexity.

Fix: Estimate as if the "average team member" will do the work. Points should be team-stable regardless of assignment.

5. Never Re-estimating

Symptom: Estimates are carved in stone even when requirements change mid-sprint.

Root cause: Treating estimates as immutable contracts.

Fix: Re-estimate when scope significantly changes. Adjust the sprint backlog accordingly.

6. Skipping the "Why"

Symptom: The team assigns numbers without discussion. Nobody knows why something is an 8.

Root cause: Estimation fatigue or time pressure.

Fix: Always ask the highest and lowest voter to explain. The discussion is more valuable than the number.