The Cargo Cult of Agile: We Do The Rituals, We Get No Results

The Cargo Cult of Agile: We Do The Rituals, We Get No Results

We perform the ceremonies, but the planes of productivity refuse to land.

Nothing says agility quite like twelve adults sitting in ergonomic chairs for forty-two minutes to discuss why a button isn’t blue yet. We are in the middle of a daily stand-up, except no one has stood up in years. The air in the conference room is thick with the smell of over-roasted coffee and the collective realization that we are all lying to each other. Mark, a project manager who wears his ‘Agile Coach’ certification like a medieval sigil, is currently interrogating a junior developer about a ticket that has been in ‘In Progress’ for precisely seventy-two hours. He isn’t looking for a solution; he is looking for a reason to update a digital board that no one outside this room will ever read. It’s a performance. It’s theater. It’s the ritual of the cargo cult, where we build wooden headsets and light fires on the runway, praying for the planes of productivity to land, while completely forgetting how to fly.

I’ve spent the better part of the last decade watching this unfold in companies ranging from two-person startups to conglomerates with thirty-two thousand employees. My name is Aiden N., and when I’m not navigating the labyrinth of corporate ‘speed,’ I work as a hospice volunteer coordinator. In hospice, time isn’t a metric to be gamed; it’s a finite, precious resource that is slipping through our fingers at a rate of sixty-two seconds per minute. There is no ‘pivot’ in a deathbed conversation. There is only the truth of what was done and what was left unfinished. When I walk back into the office on Monday morning, the contrast is violent. We treat a Jira ticket like a matter of life and death, yet we treat the actual humans behind the keyboards like interchangeable parts in a machine that hasn’t produced a real result since 2012.

– The real clock vs. the sprint clock.

We have adopted the terminology of the future to mask the management structures of 1912. We talk about ‘sprints,’ but we are actually forced into marathons where the finish line is moved every twelve kilometers. We hold ‘retrospectives’ where we politely complain about the lack of communication, and then we go back to our desks and wait for the next top-down mandate to arrive from someone who doesn’t know the difference between a backend database and a backhand compliment. It’s a fundamental misunderstanding of what it means to be flexible. We think that by changing the names of our meetings, we have changed the nature of our work. But a waterfall by any other name still flows downward, and it still drowns the people at the bottom who are just trying to build something that works.

FLOW DOWNWARD

[the ritual is a shield for the terrified]

I found myself rereading the same sentence five times in the latest internal memo-something about ‘synergizing our verticality through iterative scrum cycles’-until the words just looked like black ants marching across a white desert. I realized then that the reason we cling to these rituals is that they provide a sense of safety. If we follow the Scrum Guide to the letter, if we have our burn-down charts and our Fibonacci story points, then we can’t be blamed when the product fails. We can say, ‘Look, we did everything right. The process was followed.’ It is the ultimate insurance policy for middle management. They would rather fail by the book than succeed by trusting their employees to make a decision without a sign-off from twelve different stakeholders. This obsession with the external label of ‘Agile’ is exactly why so many companies are currently stagnating.

📦

The Packaging Bias

Obsessing over the exterior label (Agile certification) while ignoring internal rot.

It reminds me of the way people approach shopping when they see a product that has been returned. They see the ‘open-box’ sticker and immediately assume the contents are broken, missing a gear, or inherently flawed. They can’t see past the label to the value inside. This is a massive mistake, because it’s often the core quality that matters most, not whether the tape on the box is original. It’s the same cognitive bias that makes people ignore a

Half Price Store

deal simply because the packaging is taped shut-they can’t see the pristine quality inside because they’re obsessed with the exterior label. In the corporate world, we do the opposite: we put a shiny ‘Agile’ box around a broken, rigid culture and wonder why the product still doesn’t work.

In my hospice work, I’ve learned that the most important things happen in the gaps between the formal moments. It’s the hand-hold when the morphine isn’t enough; it’s the quiet joke told to a grieving spouse. In software, ‘Agile’ was supposed to be about those gaps-about the ‘individuals and interactions over processes and tools.’ But we’ve flipped the script. We’ve automated the interactions so we can focus on the tools. We’ve turned the ‘stand-up’ into a status report because we’re too afraid to actually talk to each other. I once worked at a place that had 112 different Slack channels for a single project, yet no one knew who was responsible for the final deployment. We were drowning in communication but starving for connection.

The Illusion of Velocity

Let’s talk about the numbers, because management loves numbers, as long as they end in two. We had a velocity of eighty-two points last sprint. Does that mean we delivered value? No. It means we closed eighty-two points’ worth of tickets. We could have been moving pebbles from one side of a digital field to the other, and the chart would look beautiful. In fact, if we actually stopped to fix the systemic issues that make our code a mess, our velocity would drop to twelve for a week, and the ‘Agile Coaches’ would have a collective heart attack. They are incentivized to maintain the appearance of speed, not the reality of progress. It is a system designed to reward busyness while punishing thought. I’ve seen developers spend forty-two hours a week in meetings only to be asked why they didn’t finish their tasks during the remaining two hours of the day.

Velocity Points Closed

82

Last Sprint

VS

Tangible Value Delivered

14

Estimated Value Units

[speed is the byproduct of trust not the goal of a ritual]

There is a deep, underlying fear that if we let go of the rituals, we will lose control. And that is the truth: you will. Real agility requires a loss of control. It requires a manager to say, ‘I don’t know when this will be done, but I trust the team to do it as fast as possible.’ But in a world of quarterly earnings and $222-an-hour consultants, ‘I don’t know’ is a death sentence. So we lie. We create fake deadlines that end on the twenty-second of the month. We create ‘sprint goals’ that are just lists of features we’ve already promised to the sales team. We perform the dance. We wear the grass skirts. We wait for the planes.

The Engineer and the Comfort Metric

I remember a specific volunteer I coordinated back in 2022. He was a retired engineer who tried to ‘Agile’ the hospice intake process. He wanted to track the ‘cycle time’ of a patient’s comfort. It was the most absurd thing I had ever seen. He was trying to measure the unmeasurable because he didn’t know how to just be present in the room with a person who was suffering. That is exactly what we are doing in our offices. We are trying to measure ‘productivity’ because we don’t know how to build a culture where people actually want to work. We are trying to substitute a Jira board for a sense of purpose.

– Measuring presence with metrics is the ultimate failure of context.

The Way Forward: Burning the Rulebook

If we want to actually be agile, we have to start by burning the rulebook. We have to stop calling things ‘ceremonies’-a word that implies a religious devotion to a fixed form-and start calling them conversations. We have to admit that we are terrified of the uncertainty of the market and the complexity of our systems. We have to stop punishing people for finding a better way that doesn’t fit into the two-week sprint cycle. True innovation doesn’t happen on a schedule that ends in two. It happens when someone has the space to fail, the time to think, and the trust of their peers.

The Unassigned Mess

I often think about that coffee stain on the table. It’s still there, forty-two minutes into the meeting. No one has wiped it up because that isn’t anyone’s ‘task.’ It isn’t in the backlog. It hasn’t been assigned a story point. We are so focused on the ritual of the meeting that we can’t even see the mess right in front of us. We are waiting for the cargo to arrive, while the ship is sinking right outside the window. We need to stop looking at the labels, stop worshipping the process, and start looking at the reality of the work. Only then will we find the results we’ve been pretending to achieve for all these years. It’s time to stop the stand-up and actually start moving.

We need to stop looking at the labels, stop worshipping the process, and start looking at the reality of the work. Only then will we find the results we’ve been pretending to achieve for all these years. It’s time to stop the stand-up and actually start moving.

Reflections on Process, Trust, and the Illusion of Speed.