Back
Estimation is the part of planning everyone hates and everyone needs. Story points done well give you a shared language for complexity. Done badly, they become time-in-days with extra steps.
What story points actually measure
Story points measure relative complexity, effort and risk — not hours. The moment you start translating points to hours, you've lost the benefit. A 3-point story is three times as complex as a 1-point story, not three times as long.
How to keep them honest
Anchor every round of estimation against a story you already shipped. 'This is smaller than the profile settings we did last sprint, and bigger than the notifications toggle.' If you don't have anchor stories, estimation drifts within weeks.
Re-anchor every quarter. Teams get faster over time. The same scope that was a 5 last year might be a 2 now — refusing to update that distorts your velocity metrics.
Conclusion
The best teams treat estimation as a conversation, not a ceremony. The point isn't to be precise — it's to surface disagreements about scope early enough to do something about them.
