Velocity Is Theater
How story points create the illusion of control while masking uncertainty
“Since you rated this story a 5, does this mean we can complete it in one sprint?”
“This story is a 2-pointer, so you could be able to knock that out in one working day.”
“Whoa, a 13? We need to table this and put into the next planning discussion so we can break it into multiple sprints.”
“The implementation for this seems complex…I’m thinking we should size this story as a Large.”
There is a theme with this concept of thinking: Chronic guessing.
Even if your team has been sizing together for a while, that doesn’t mean the process is any less convoluted.
It just means you’ve gotten better at guessing in a group.
The Comfort of Story Points
Let’s be honest: story points feel scientific.
They give us:
A sense of control
A mechanism to forecast
A way to signal complexity
A structured planning ritual
Popularized through frameworks like Scrum and heavily discussed in resources such as Agile Estimating and Planning, story points were meant to measure relative effort, not time.
But somewhere along the way, relative effort quietly morphed into time translation.
A 2 becomes “a day.”
A 5 becomes “half a sprint.”
A 13 becomes “we’re in trouble.”
And suddenly, the abstraction collapses.
The Illusion of Precision
When a team debates whether something is a 5 or an 8, what are they really debating?
Unknown dependencies
Integration risk
Team familiarity
Architectural ambiguity
Historical trauma from “similar” work
But instead of articulating those risks explicitly, we compress them into a number.
Then we treat the number as if it contains truth.
It doesn’t.
It contains sentiment.
And sentiment shifts depending on:
Who is in the room
Who is most vocal
Who has been burned before
Who is under delivery pressure
This is not estimation. You’ve just socially calibrated your team to align on this activity.
The Real Cost of Chronic Guessing
Chronic guessing leads to three predictable patterns:
Defensive Sizing: Engineers pad estimates to create safety.
Political Sizing: Leads or stakeholders push for smaller numbers to protect roadmap optics.
Emotional Sizing: A past incident inflates the perceived risk of unrelated work.
None of this improves delivery. But it does ensure you’re just redistributing anxiety.
Velocity Theater
Over time, teams start performing for the velocity metric.
Velocity becomes a proxy for productivity, predictability and team health.
But velocity is simply the sum of guesses completed.
Optimizing for it doesn’t increase flow, just conformity.
You can hit your velocity target and still
Ship late
Miss critical dependencies
Burn out your team
Accumulate architectural debt
Velocity is a lagging indicator of a flawed premise: that we can predict complex knowledge work with Fibonacci numbers (or other various sizing methods).
What Actually Improves Delivery
High-performing teams shift from estimation obsession to flow optimization.
Instead of asking:
“Is this a 5 or an 8?”
They ask:
What makes this unclear?
What would make this smaller?
What dependency is hiding here?
What decision are we avoiding?
They slice vertically.
They reduce batch size.
They tighten feedback loops.
This thinking aligns more closely with lean principles often associated with The Lean Startup and the systems thinking popularized in The Phoenix Project.
The focus shifts from predicting effort to accelerating learning.
The Shift That Changes Everything
Here’s the uncomfortable truth: You don’t need better estimation techniques.
You need fewer unknowns.
You don’t need more precise pointing sessions. You need:
Clearer product decisions
Tighter acceptance criteria
Earlier integration testing
Reduced cross-team coupling
Ruthless scope slicing
When uncertainty decreases, delivery accelerates.
Not because your guesses got sharper. But because there’s less to guess about.
A Better Planning Conversation
Instead of:
“This feels like a 13.”
Try:
“What makes this feel risky?”
“What part can we deliver in 3 days?”
“What dependency can we validate this week?”
“What’s the smallest outcome that proves value?”
That conversation produces movement, while point debates produce comfort.
The Hidden Truth
Story points aren’t evil. They’re just over-trusted.
They were meant to create shared understanding, but they don’t create certainty.
When you detach identity and performance from estimation accuracy, something powerful happens…
Planning becomes calmer.
Engineers stop negotiating numbers.
Product focuses on outcomes.
Delivery improves organically.
Because the team stops trying to be right about the future…
…and starts building feedback into the present.
If you’ve ever felt that planning sessions were more exhausting than building the thing itself, you’re not alone.
The question isn’t whether to estimate.
The question is: “Are your estimates revealing truth…Or just masking uncertainty with math?”