I Wasted a Decade Pretending Story Points Made Sense
For over a decade, I lived a lie. I convinced myself that Agile story points were legitimate. That the contradictions made sense. That "it's flexible, you can do it how you want" was profound rather than absurd.
I'm done.
The Rationalisations We Tell Ourselves
"They map to complexity, not time"
Yet every Sprint Planning meeting revolves around fitting tasks into a Sprint, which is literally a unit of time. And doesn't complexity... relate to time? A complex task takes longer. That's what "complex" means in this context.
The disconnect is stunning. We're using story points as effort estimates during sprint planning, then claiming they measure complexity independently of time. This isn't nuance, it's contradiction.
"They're rough guides, not accurate"
How did we end up with a unit of measure that's "not supposed to be accurate"? Imagine a builder saying "yeah, metres aren't meant to be precise." You'd find another builder.
Yet in software, we've normalised imprecision as a feature. Ron Jeffries, who co-created story points, now openly regrets it: "I may have invented story points, and if I did, I'm sorry now." Even the inventor thinks it's broken.
"It depends on who's doing the work"
This is like saying the length of a centimetre depends on your tape measure. A measurement system that changes based on the measurer isn't a measurement system, it's vibes.
"They're relative complexity"
Relative to what? Another story you estimated inaccurately? It's turtles all the way down.
"We use Fibonacci/shirt sizes/animals/fruit"
Why can't I give a task 4 points? Because the Fibonacci sequence says so? This isn't making estimation easier, it's adding arbitrary constraints that force false precision.
My personal favourite: "A story point is like a chicken." Yes, a human actually said this. Find a simple story, call it a chicken, that's 1 point. A harder story is 2 chickens. This is a real explanation people use with straight faces.
The Cult Dynamics
Agile exhibits classic cult characteristics. There's the scripture (the manifesto), the high priests (Scrum consultants), and the mantras we repeat until they sound true.
When pressed to define story points, I've seen:
- "They have no unit of value"
- "They're a non-standard unit of value" (what?)
- "They're team-specific, so they don't map to anything"
- "They don't map to time, but they map to sprints, which are time"
- "They're only for epics, stories use hours"
- "Planning poker helps us reach consensus" (translation: wears people down until they agree)
Every contradiction gets handwaved with "it's Agile, it's flexible." This isn't flexibility, it's incoherence dressed up as methodology.
The Reality
By 2026, the cracks are impossible to ignore. Teams report that estimates become promises, not learning tools. Plans become contracts with management, not guides for collaboration. The artificial precision creates false confidence.
Brightball's analysis found story points "completely unreliable, confusing." Multiple studies show they don't improve predictability. Yet we persist because admitting failure means confronting an uncomfortable truth: some things are genuinely hard to estimate.
My New Framework
I'm launching a new system. Planning meetings every 13 days, unless there's a full moon. Play Snakes and Ladders to determine relative complexity. Throw out that number. Do the work anyway. Every 15 minutes, someone stands up and shouts "Bingo."
Sound ridiculous? It makes exactly as much sense as our current rituals, so it'll probably take off.
I apologise to the workers of 2040 who'll inherit whatever we cook up next.
What Actually Works
Here's the uncomfortable truth: estimation is hard. Complexity and time are intertwined. Team dynamics change. Requirements shift. No amount of chickens or Fibonacci numbers changes this.
Some teams are ditching estimates entirely. Others use actual hours, acknowledging the time/complexity relationship. The key isn't finding the perfect system, it's admitting when one doesn't work.
After a decade of rationalisations, I'm done pretending. Story points don't make sense. They've never made sense. And that's okay, we can find better ways to plan work.
Just maybe not chickens.