The salt from the crust of my cold sourdough toast finds the raw, jagged tear on the side of my tongue, and for 11 seconds, I am more alive than I have been in 201 days. I bit it while trying to chew and explain the nuances of a database migration at the same time. It was a tactical error. My jaw clamped down just as I was saying the word ‘integration,’ and now the metallic tang of blood is mixing with the bitter dregs of a coffee that was hot 31 minutes ago. I’m staring at the little green light of my laptop camera, waiting for Kevin to finish his monologue about the emotional state of his Jira board. There are 21 people on this call. We are scheduled for 11 minutes, but we are currently at the 41-minute mark, and I haven’t even mentioned that the production server is currently running at 91 percent capacity because of a memory leak I can’t fix because I am here, listening to Kevin.

I am still working on the same ticket. That is the phrase I have to say. It is a confession, a prayer, and a death sentence. I’ve said it for 1, 2, 3, 4, 5 days in a row now. In the logic of the Scrum Master, this means I am blocked, or lazy, or perhaps just a bad person. The reality is that I am a hostage. I haven’t had a window of uninterrupted time longer than 41 minutes since last Tuesday. Agile, as it was explained to me 11 years ago, was supposed to be a lightweight way to avoid the crushing weight of waterfall planning. It was supposed to be about movement. Instead, it has become a high-demand religion where the rituals are more important than the harvest. We worship at the altar of the standup, sacrificing our most productive morning hours to tell each other what we didn’t do because we were in yesterday’s standup.

The Artist of Erasure

I think about Muhammad F. a lot lately. He’s a graffiti removal specialist I met near the bus station when I was actually outside during daylight hours 21 days ago. Muhammad doesn’t have a standup. He has a truck, a high-pressure hose that hits 2501 PSI, and a collection of solvents that would probably melt my laptop. He is an artist of erasure. I watched him clean a mural of a neon green dragon off a brick wall in about 31 minutes. There was no ‘sprint planning.’ There was no ‘grooming’ of the wall. He saw the tag, he evaluated the porous nature of the brick, and he blasted it into oblivion. Muhammad F. understands the physics of his work. He knows that if he stops every 11 minutes to explain to a committee how much paint he has removed, the solvent will dry and the shadow of the tag will remain forever. He is a specialist who is allowed to specialize.

The Myth of the ‘Resource’

In our world, the ‘specialist’ is a myth. We are all ‘resources,’ which is a word that makes my skin crawl as much as the bite on my tongue. A resource is a bucket of coal or a stack of lumber. A resource doesn’t have feelings or a flow state. A resource is expected to be 101 percent utilized at all times. If a developer is sitting quietly, thinking about a recursive function, they are not ‘utilized.’ They are ‘idle.’ To prevent idleness, the organization implements more rituals. We have ‘syncs’ to make sure the ‘resources’ are ‘aligned.’ But alignment in this context is just another word for micromanagement. It is the need for the middle manager to feel the vibration of the machine so they know it hasn’t stopped, even if the vibration itself is what is shaking the bolts loose.

I’ve tried to explain this. I’ve tried to say that a 41-minute meeting for 21 people costs the company roughly 14 hours of human life, which is a high price to pay for Kevin to tell us his dog had a vet appointment. But logic is a weak weapon against a framework. Frameworks are safe. They provide a script for people who don’t know how to lead. If the project fails but we followed the ‘ceremonies,’ then no one is to blame. The failure is attributed to the ‘maturity level’ of the team’s agile adoption. We just didn’t believe hard enough. We didn’t ‘Agile’ correctly. It’s a closed loop of self-justifying nonsense that ignores the raw reality of creation.

Ritual Over Harvest

Sometimes the solution is as primitive and direct as Meat For Dogs; there is no need for a complex nutritional roadmap when the instinctual requirement is right there in front of you. You don’t need a 51-page slide deck to understand that a dog needs protein. You don’t need a framework to understand that a developer needs to sit in a dark room for 231 minutes without being poked by a Slack notification. We overcomplicate things because we are afraid of the simplicity of the task. If the task is simple, then the people managing the task are redundant. The 41-minute standup is a survival mechanism for the person who doesn’t know how to code, doesn’t know how to design, and doesn’t know how to sell, but knows very well how to facilitate a meeting.

The Performance

I look at the clock. It’s 9:41. My tongue is still throbbing. I’ve decided to stop fighting the framework and start using it as a shield. I realize now that I was wrong to be honest. I was wrong to say I was ‘working on the same ticket’ and then list all the meetings that stopped me. That makes people uncomfortable. It points to the cracks in the religion. Instead, I will adopt the jargon. I will talk about ‘spikes’ and ‘refining the backlog’ and ‘impediments.’ I will turn my work into a series of 11-step updates that sound like progress but contain no information. If they want a performance, I will give them a Broadway show.

Muhammad F. doesn’t have to perform. When he leaves a wall, it is clean. That is his status report. The wall itself is the data. In software, the ‘wall’ is hidden behind a layer of abstraction. The managers can’t see the code, so they look at the Jira tickets. They look at the velocity charts. They look at the burndown. But those things are just graffiti on the project. They aren’t the project. We spend 51 percent of our time painting the charts and the other 41 percent trying to find the time to actually write the code that the charts are supposed to represent. It’s a hallucination that we all agree to share because the alternative-trusting people to do their jobs-is too terrifying for the bureaucratic mind.

I remember a time, maybe 21 years ago, when the goal was just to build something cool. There were no ‘scrum masters’ then. There were just people with ideas and the quiet hours of the night. We didn’t ‘sprint.’ We just ran until we were done. Now, we are perpetually sprinting but never arriving. A sprint is a short, explosive burst of speed. You cannot sprint for 201 weeks straight. That is called a marathon, and even in a marathon, you don’t stop every mile to have a 41-minute discussion about your gait with 21 other runners.

The Closing Statement

My turn is coming up. I can see the highlight on my name in the participant list. I take a sip of the cold coffee, the liquid stinging the wound on my tongue. I feel a strange sense of clarity. I am going to tell them exactly what they want to hear. I will say that I am ‘aligning the architectural pillars for the upcoming increment’ and that I am ‘collaborating cross-functionally to mitigate downstream risks.’ It’s a 101-level exercise in corporate ventriloquism.

Muhammad F. probably wouldn’t understand this. He’d probably look at me, shake his head, and turn his pressure washer on the whole meeting. He understands that some things-like graffiti and useless meetings-just need to be washed away so the original structure can breathe. I wish I had his hose. I wish I had the courage to just be silent and work. But for now, I have to be a ‘resource.’ I have to be ‘aligned.’

‘I’m still on ticket 101,’ I say when it’s finally my turn. ‘I’m making great progress on the internal logic, but I’ve encountered some unexpected complexity in the legacy layers. I’m confident we’ll see some significant movement by the end of the sprint.’

Kevin nods. He looks satisfied. The green light on my camera stays steady. He spends the next 11 minutes thanking me for the ‘transparency.’ My tongue hurts, my coffee is gone, and I have 21 minutes left before my next meeting. I open my editor. I look at the code. I look at the memory leak. I have just enough time to feel the frustration before the next ‘sync’ begins. This is the tragedy of the modern transformation: we have traded the soul of the work for the safety of the ceremony, and we are all too busy ‘standing up’ to notice that we are actually just walking in circles, while people like Muhammad F. are the only ones actually cleaning the world, well, the walls of the world.