Story points vs. hours: The debate that never dies
I know this has been discussed a million times, but I'm seeing a new trend at my org. Leadership is pushing us back to hourly estimates because "story points aren't predictable enough."
Here's my argument for keeping story points:
1. They measure complexity, not time — which is what actually matters for capacity planning
2. They reduce sandbagging (people pad hourly estimates)
3. Velocity stabilizes over time and becomes MORE predictable than hours
4. They force conversations about scope and complexity
What's your go-to response when leadership pushes back on story points?
4 Comments
My go-to: show them the last 6 sprints of velocity data and compare it to the accuracy of hourly estimates from before. Data wins arguments.
Honestly? I've moved to t-shirt sizing for rough estimation and only use points when the team finds them useful. The goal is shared understanding, not precise numbers.
New to this — can someone explain how story points actually help with sprint capacity planning? I keep hearing conflicting advice.
@tom_facilitate Sure! In short: you track how many points your team completes per sprint (velocity). After 3-5 sprints, it stabilizes. Then you know roughly how many points you can commit to. It's not about the absolute number, it's about the trend.