The Ritual of Stagnation
The cursor hovers over the ‘In Progress’ column, twitching with a nervous energy that mirrors the 16 faces staring back through the low-resolution grid of the video call. We are currently 26 minutes into a session that was explicitly scheduled for 15. The Scrum Master, a man whose primary qualification seems to be an unwavering belief in the sanctity of the sticky note, is asking Marcus why his ‘story points’ haven’t moved since Tuesday. Marcus is a senior engineer with 26 years of experience, but in this moment, he looks like a schoolboy being interrogated about a missing eraser. He mumbles something about a dependency in the legacy database, but his words are swallowed by the sound of someone else’s unmuted heavy breathing. This is the ritual. This is the performance. We aren’t building software anymore; we are tending to a digital garden of bureaucratic weeds.
I find myself rereading the same sentence in the Jira ticket five times, a symptom of the cognitive rot that sets in when process becomes the product. The sentence says, ‘As a user, I want to be able to click a button so that I feel empowered.’ It’s nonsense. It’s the kind of fluff that exists only to satisfy the requirement of having a ticket to move. We have built a system that prizes the movement of the ticket over the quality of the code, a factory floor where the assembly line is made of meetings and the output is a feeling of ‘velocity’ that never actually reaches the customer. It’s a collective delusion, a high-cost theater production where the actors are paid in $106,000 salaries to pretend that a burndown chart is a map of reality.
The Measurement Fallacy
Dakota S.-J., an AI training data curator I worked with during the 46-day sprint from hell, once told me that the hardest part of her job wasn’t the data itself, but the way the managers tried to box human nuance into binary tags. It’s the same disease. We are obsessed with measuring the unmeasurable. We think that if we can put a number on a creative act, we can control it.
The Rigid Armor of Agile
We’ve turned Agile-a philosophy born from a desire for lightness and human interaction-into a rigid, clanking armor that prevents us from moving at all. It’s a cage made of daily stands, weekly refinements, and bi-weekly retrospectives where we talk about how we can be more efficient, never realizing that the meetings themselves are the inefficiency.
“
I once spent 46 hours in a single month just preparing for meetings about how to save time. The irony wasn’t lost on me, but I did it anyway because the alternative was being labeled ‘not a team player.’
That’s the trap. If you criticize the ritual, you’re a heretic. You’re told you just haven’t ’embraced the mindset’ yet. But the mindset was supposed to be about responding to change over following a plan. Now, the plan is the framework, and the framework is non-negotiable. If a developer has a breakthrough at 2:06 AM and wants to pivot the architecture because it’s the right thing to do, they are stopped by the weight of the committed sprint backlog. ‘We’ll put that in the next refinement,’ the Scrum Master says, effectively killing the spark before it can become a flame.
The Fear of Uncertainty
We fear uncertainty so much that we’d rather be precisely wrong than vaguely right. We want the comfort of the blue bar moving across the screen, even if that bar represents work that shouldn’t be done in the first place. This fetishization of process reveals a deep-seated distrust of professional autonomy. If we trusted our developers, we wouldn’t need to check in on them every 24 hours. If we trusted our vision, we wouldn’t need 106 pages of documentation to justify a button change. We are treating creative problem-solvers like cogs in a 19th-century textile mill, forgetting that software is grown, not manufactured. It’s an organic, messy, often frustrating process that requires space, silence, and the freedom to fail without it being recorded as a ‘deviation’ in a sprint report.
Process is the ghost of a dead intuition.
Consider the way a master of their craft operates. They don’t have a checklist for every second of their day. They have a goal and a deep well of experience to draw from. If you look at the work of Famous Wildlife Photographers, you don’t see them trying to ‘sprint’ toward a lion. They don’t have a 16-minute stand-up with the savanna. They wait. They adapt. They move when the moment is right, guided by an intuition that can’t be put into a Jira ticket. If they were forced to follow a modern corporate Agile framework, they’d spend the golden hour filling out status reports instead of capturing the light. They understand that the environment dictates the action, not the schedule. In the wild, as in the best software labs, rigidity is a death sentence. You have to be fluid. You have to be willing to scrap the plan when the weather changes.
Velocity Achieved
Outcome
Optimizing for Average
Dakota S.-J. recently quit her role as a curator. She told me she couldn’t stand the way the AI was being trained to be as boring and predictable as the managers who oversaw it. She saw the same pattern I see: the elimination of the outlier, the smoothing over of the creative ‘noise’ that actually contains the signal. When we force everyone into the same 16-day cycle, we lose the long-term thinkers and the quick-twitch innovators. We get a sea of ‘average’ that is safe for the middle manager but lethal for the company’s future. We are optimizing for the middle of the bell curve, and in doing so, we are making ourselves obsolete.
The Cost of Sameness
We lose the outliers-the quick-twitch innovators and the long-term thinkers-when we enforce uniform pacing. The rigidity that creates ‘alignment’ simultaneously eradicates true competitive advantage.
I’m not saying we should have no structure. Chaos is its own kind of prison. But the structure should be a trellis, not a cage. It should support the growth, not dictate its every turn. We need to stop pretending that 16 people in a Zoom call is a productive way to solve a complex architectural problem. We need to stop valuing the ‘done’ column more than the ‘value created’ column. And we desperately need to stop treating the Scrum Master as a high priest whose word is law. They are supposed to be facilitators, not wardens.
The Uncomfortable Silence of ‘Why’
There is a certain silence that happens in a meeting when someone asks a real question-a question that isn’t about status or points, but about ‘why’ we are doing this. It’s an uncomfortable silence. Usually, it lasts about 6 seconds before someone redirects back to the board. We are afraid of the ‘why’ because the ‘why’ might reveal that the process is hollow. If we admit that the sprint goal is arbitrary, then the whole house of cards falls down. So we keep moving the tickets. We keep attending the stands. We keep our cameras on and our souls off.
“
I’ve started doing this thing where I just don’t go to meetings that don’t have an agenda. It’s a small rebellion, and it has caused 6 awkward conversations with my lead, but it’s the only way to stay sane. The work-the real, meaningful, difficult work-happens in the gaps.
I’m trying to reclaim those 46-minute blocks of deep work that the calendar tries to steal. It’s hard. The system is designed to fill every gap with ‘collaboration,’ which is usually just a fancy word for ‘group-think.’ But the work-the real, meaningful, difficult work-happens in the gaps. It happens when the Jira board is closed and the Slack notifications are paused. It happens when we stop performing and start building.
The true metric of autonomy.
The Path to Fluidity
Maybe we need to fail a few sprints on purpose. Maybe we need to let the velocity drop to 6 and see if the world actually ends. I suspect it wouldn’t. I suspect we’d find that the product actually improves when we spend less time talking about it and more time living with it. We need to find that balance again, the one where the process serves the human, not the other way around. We need to be more like the photographer in the grass, patient and observant, ready to strike when the moment is right, rather than when the clock strikes 10:06 AM for the daily stand-up.
I look back at the screen. The Scrum Master is still talking. Marcus has his eyes glazed over, probably dreaming of a world without sub-tasks. I decide to close the tab. For the next 36 minutes, I’m going to actually write code. No tickets, no points, no ‘as a user.’ Just logic and intention. It feels like a crime, which is exactly how you know you’re finally doing something right. If the process makes you feel like a criminal for doing your job, the process is the problem. It’s time we stopped asking for permission to be professionals. The cage is only as strong as our willingness to stay inside it.
Stop Asking Permission
We might move faster than any sprint could ever dictate if we traded the 26-minute status update for a 6-minute conversation about a real problem. The wild environment dictates action, not the clock.
What would happen if we just stopped? Not stopped working, but stopped the performance of work. If we traded the 26-minute status update for a 6-minute conversation over coffee about a real problem. If we valued the intuition of the senior dev over the metric of the project manager. We might find that we move faster than any sprint could ever dictate. We might find that the work actually matters again. Until then, I’ll be here, occasionally moving a ticket to keep the wardens happy, but my mind will be somewhere else-out in the wild, where the only metric that matters is the survival of the idea.