The Gospel of the Story Point: How Agile Became a Religion
When the bureaucracy of process suffocates the very responsiveness it promised.
The fluorescent lights in the ‘War Room’ hummed at a frequency that felt like a migraine in waiting, a steady, buzzing 44 hertz of corporate clinicality. Jeff was leaning across the laminate table, his face flushed a dull shade of red, insisting that the login refactor was a 14, while I sat there with my head in my hands, knowing damn well we hadn’t even defined what ‘done’ looked like for the 4th time this week. We were 124 minutes into a ‘sprint planning’ session that was supposed to last 54. The air smelled like stale coffee and the desperate, electric scent of people trying to quantify the unquantifiable.
I just lost 44 open browser tabs of research because my finger slipped on the ‘Close All’ shortcut right before this meeting started, and honestly, the void feels more honest than this Jira board. There is a specific kind of grief that comes with losing a dozen half-read whitepapers and four competing stack-overflow threads, but it’s a clean grief. It’s the universe telling you that the slate is wiped. In this room, however, there is no such mercy. We are buried under the weight of ‘Story Points,’ a currency backed by nothing but the collective anxiety of a middle-management layer that needs to see a velocity chart go up by 4 percent every two weeks or they’ll lose their sense of self.
The Cult of Process
We have entered the age of the Agile Cult. What was once a manifesto written by 14 guys in a ski resort-a document that emphasized individuals and interactions over processes and tools-has been cannibalized by the very bureaucracy it sought to dismantle. We now have High Priors, known as Scrum Masters, who spend their days policing the length of a stand-up. If you speak for 16 minutes instead of 14, you have committed a minor heresy. We have rituals that must be performed with liturgical precision: the refinement, the planning, the retro, the demo. We are so busy practicing the religion of being fast that we have forgotten how to actually move.
The Groundskeeper’s Agility
I think about Sarah T.J. sometimes. She’s been the groundskeeper at the local cemetery for 14 years, and she is perhaps the most agile person I know, though she would never use that word. Sarah doesn’t have a backlog. She has 444 acres of silence and the changing seasons. When a storm rolls through and knocks down an oak branch across a 104-year-old headstone, she doesn’t wait for a sprint cycle to move it. She doesn’t estimate the ‘effort’ required in Fibonacci numbers. She picks up the chainsaw and she cuts. Sarah understands something that the ‘Agile Coaches’ with their $4,444 certifications seem to have missed: responsiveness is a physical act, not a documentable ceremony.
Humans have a deep, primal need for certainty. We are terrified of the dark, and software development-or any complex creative endeavor-is essentially walking into a dark room and trying to find a light switch that might not exist. To soothe this terror, we adopt rigid frameworks. We convince ourselves that if we just follow the ‘Safe’ framework or the ‘Scrum’ guide to the letter, we are protected from the chaos of reality. We turn the process into a shield. If the project fails but we followed the ceremonies, it wasn’t our fault; it was a ‘process impediment.’ We have traded the soul of the work for the safety of the ritual.
The Un-Agile Response
I remember a time, about 14 months ago, when a server went down in the middle of a release. The ‘Agile’ response would have been to wait for the morning stand-up to ‘surface the blocker.’ Instead, three of us stayed up until 4:44 AM, drinking lukewarm soda and actually talking to each other. No tickets. No points. Just raw, unmediated problem-solving. That was the only time in the last 24 weeks that I felt we were actually being agile. We were responding to change over following a plan. Yet, the next morning, we were scolded because our ‘burndown chart’ looked jagged.
Abstraction vs. Reality
This dogmatic obsession with the rules of Agility often prevents the very thing it claims to promote. We see this everywhere in the corporate world, but rarely in the service industries that actually have to live in people’s homes.
Discussing velocity off-chart after 44 hours of delay.
VS
Adapting to subfloor slant and humidity immediately.
When you look at a company like Hardwood Refinishing, you see a different kind of agility. They don’t walk into a house with a 24-page immutable ‘sprint plan’ for your living room floor. They adapt to the slant of the subfloor, the humidity of the Tennessee air, and the specific, shifting needs of the family living there. They are agile because they have to be; if they weren’t, the floor would buckle. In our world, the ‘floor’ is a digital abstraction, so we let it buckle and then spend 44 hours in a retrospective discussing why the ‘velocity’ was off.
“
The ritual has replaced the result.
”
The Isolation of Metrics
We are currently arguing over whether a task is a 4 or an 8. The customer, meanwhile, is sitting in a 104-degree office in Phoenix, unable to pull a report that they need to keep their business alive. They don’t care about our points. They don’t care about our ‘Daily Scrum.’ They care about the fact that their reality is broken and we are playing a board game with sticky notes. The irony is that the more we lean into the ‘Agile’ rules, the less we listen to the human on the other side of the screen. We have automated our empathy into a Jira workflow.
Sarah T.J. once told me that the hardest part of her job isn’t the digging. It’s the 14 minutes after the service is over, when she has to stand back and wait for the family to leave before she can finish her work. She has to be present, but silent. She has to adapt her pace to their grief. That is true agility-the ability to modulate your existence based on the environment you find yourself in. It requires a level of emotional intelligence that cannot be found in a 4-day seminar in a Hilton conference room.
We’ve created a system where we are rewarded for the ‘output’ of stories rather than the ‘outcome’ of success. I have seen teams celebrate finishing 44 tickets in a sprint, even though the feature they built was so confusing that support calls increased by 24 percent. But the chart went up! The velocity was high! The High Priests were pleased! We are sacrificing the product at the altar of the process.
A Decade of Isolation
14 Years Ago
Notebooks, Lists of People
24 Weeks Ago
Discovery Sessions Scheduled
I recently found an old notebook from 14 years ago, back when I first started coding… Now, if I want to talk to a user, I have to submit a request to the Product Owner, who then clears it with the UX Researcher, who then schedules a ‘discovery session’ 14 days from now. We have ‘Agiled’ ourselves into a state of total isolation.
The Necessary Reckoning
We need to stop. We need to admit that the ‘rules’ are just a security blanket. We need to realize that you can have 104 Scrum certifications and still be a terrible teammate. Agility is not something you ‘do’; it is something you are when everything goes wrong. It is what happens when the browser tabs close and you have to remember what you were doing from memory and instinct. It is the ability to look at a 4-point ticket and realize it’s actually a 0-point conversation that should have happened 24 days ago.
The final truth: Unscripted Motion
As the meeting dragged into its 154th minute, I looked out the window. I saw a bird land on a power line, adjust its grip, and take off again as the wind shifted. It didn’t consult a framework. It didn’t wait for a consensus. It felt the change in the air and it moved.
Maybe one day we will be that brave again. Maybe one day we will stop counting points and start solving problems, even if it means breaking every single ‘Agile’ rule in the book. Until then, I’ll be here, arguing with Jeff about whether a 4 is really just a 14 in disguise, while the world keeps spinning at 1,004 miles per hour, completely indifferent to our velocity.
WE ARE SACRIFICING THE PRODUCT AT THE ALTAR OF THE PROCESS.
Comments are closed