The Spectator to Functionality

My thumb is pressing hard against the glass of the driver’s side window, leaving a greasy smudge right over the spot where my keys are mocking me from the passenger seat. It is 8:49 in the morning, and the rain is starting to turn from a light mist into a committed downpour. There is a specific kind of helplessness that comes from seeing exactly what you need, separated from it by a transparent but impenetrable barrier. It’s a physical manifestation of a feeling I’ve carried into every office building for the last 19 years. You see the goal. You see the tools. But you are locked out by a system of your own making.

I eventually had to call for help, but that feeling of being a spectator to my own functionality didn’t leave when the door finally clicked open. Instead, it followed me into the 9:19 AM status meeting, which we collectively pretend is a ‘Daily Standup’. We stood in a loose, jagged circle of 19 people, most of us shifting our weight from foot to foot as if the physical act of standing could somehow inject urgency into a process that has been dead for 49 months.

We’ve adopted the liturgy. We’ve memorized the prayers. We have the vestments of Jira and the sacred incense of post-it notes, but the spirit of the thing has long since departed. Agile was supposed to be about the individual, about the conversation, and about the terrifyingly beautiful freedom of changing your mind when you realize you’re wrong. Instead, it has become a new flavor of Taylorism, a way to measure the factory output of human thought without ever having to acknowledge the messy, non-linear nature of how things actually get built.

The Ritual for the Living

I spent some time talking to Yuki F.T. about this. Yuki is a cemetery groundskeeper at a small plot of land about 29 miles outside the city center. She has a very different relationship with the concept of ‘process’ than most of the Scrum Masters I know. Yuki F.T. spends her days maintaining the dignity of things that have finished their run. She told me that the most dangerous part of her job isn’t the heavy machinery or the grief; it’s the complacency of the routine. When you dig 199 graves, you might start to forget that every one of them is for someone who had a very specific, unique story.

That hit me like a brick. Our Agile ceremonies aren’t for the developers. They aren’t for the product. They are for the management layers that are terrified of the silence that occurs when you actually trust people to do their jobs. If we aren’t standing in a circle at 9:19 AM, how do they know we are working? If we don’t have a burndown chart that looks like a playground slide, how do they prove their own existence to the level above them?

The Corporate Contradiction

I remember a project back in 2019 where we decided to scrap the standups for a week. We were behind by 89 hours on a delivery, and the stress was visible in the way people were typing-angry, staccato bursts of code. We stopped the meetings. We stopped the Jira updates. We just talked to each other when we needed to. It was the most productive 159 hours of my career. But by Friday, the department head was pacing the halls because he didn’t have a green checkmark on his dashboard. He didn’t care that the code was beautiful or that the bugs were being squashed at a record pace; he cared that the process was being bypassed. He wanted the keys to the car, even if he didn’t know how to drive it.

This is the fundamental contradiction of corporate Agile. It attempts to systematize something that is inherently anti-system. True agility requires a level of autonomy that makes a traditional hierarchy feel nauseous. It requires the ability to say, ‘This sprint plan is stupid, let’s do something else,’ without needing 9 signatures and a 29-page justification document. Most companies say they want Agile, but what they actually want is the ability to micromanage at a faster cadence. They want the illusion of speed while maintaining the safety of total control. It’s like trying to win a drag race while keeping your foot firmly on the brake.

The Locked Door

I think back to the smudge on my car window. I could see the solution. I could see the way forward. But the system-the locked door-was the priority. In the corporate world, the ‘process’ is the door. We spend so much time talking about how to polish the handle and what color the door should be painted that we forget the door is supposed to lead somewhere. We’ve become obsessed with the metrics of the journey while completely losing sight of the destination.

When I look at the work being done at Hytale multiplayer server, I see the opposite of this stagnation. There is an understanding there that software isn’t built by adhering to a set of rigid ceremonies, but by fostering an environment where the work can breathe. It’s about the long-term health of the development process rather than the short-term dopamine hit of moving a card from ‘In Progress’ to ‘Done’. It’s an acknowledgment that 99% of what we call ‘management’ is actually just overhead that gets in the way of the 1% that is pure creation.

Reclaiming Craft Over Certification

I’ve made mistakes myself. I once insisted on a 49-minute retrospective for a project that had only lasted three days. I was so caught up in being a ‘good practitioner’ that I didn’t realize I was suffocating the team’s momentum. I was the one holding the keys and locking them inside the car. We spent 29 minutes of that meeting discussing the ‘vibe’ of the office instead of the fact that our deployment pipeline was held together by duct tape and prayers. I chose the ritual over the reality, and I lost the trust of 9 good engineers that day. I didn’t acknowledge the mistake for 19 months, but it stayed with me, a quiet ghost in the back of my mind.

Agile, at its core, was a protest. It was a group of 17 (or let’s say 19 for the sake of the rhythm of this thought) people in a ski resort who were tired of being treated like cog-turners. They wanted to reclaim the craft. But like any successful protest, it eventually got co-opted by the very establishment it was fighting against. It was sanitized, packaged, and sold back to us as a certification. You can now pay $979 to be told that you are a Master of something that was originally intended to be a state of mind. It’s the ultimate irony. We are buying the permission to be free, and in doing so, we are ensuring we never actually will be.

Where Real Agility Lives

The rest of it-the 9:19 AM standup, the grooming sessions that last for 119 minutes, the endless estimation of ‘story points’-that’s just the funeral service.

The Fading Markers

Yuki F.T. told me that eventually, the grass grows over everything. The markers fade, and the names become illegible. The rituals eventually stop because the people who remembered why they started are gone. I wonder if that’s what will happen to Agile. Maybe in 29 years, we’ll look back at Jira tickets the way we look at punch cards-as a curious relic of a time when we thought we could capture the lightning of human thought in a box made of status updates.

The History of Co-option

Conclusion: Keep Your Keys Ready

Until then, I’ll keep my keys in my pocket. I’ll keep looking for the gaps in the glass. I’ll keep reminding myself that the goal isn’t to stand in a circle; the goal is to build something that matters before the rain gets too heavy and we all have to go home. We need to stop acting like groundskeepers for a methodology that died a decade ago and start acting like the creators we were hired to be.