“How exactly did you miss the dependency on the legacy API, Jeremy?” The question doesn’t hang in the air; it drops like a lead weight into a bowl of cold soup. Rick, the Scrum Master-who, let’s be honest, hasn’t written a line of code since 2009-is leaning against the whiteboard. He isn’t looking at the blockers. He is looking at Jeremy’s neck, watching for the telltale pulse of anxiety. Jeremy is blocked. He said it clearly 9 seconds ago. But instead of the room shifting to clear the path, the room has shifted into a courtroom. The daily stand-up, that 15-minute ritual of supposed peer-to-peer alignment, has been weaponized into a public trial.

We call this ‘Agile,’ a word that implies grace, speed, and the ability to pivot like a gazelle. In reality, it feels more like a slow-motion car crash in a room filled with expensive monitors and 49-dollar office chairs that claim to be ergonomic but are actually just plastic molds of despair.

The Hollowed Core of Efficiency

We didn’t start here. I remember when we thought the Manifesto was a liberation document. We were going to talk to each other. We were going to build things that worked. But somewhere between the first Post-it note and the 1509th Jira ticket, the spirit of the thing was hollowed out and stuffed with the taxidermy of middle management. Companies didn’t adopt Agile because they wanted to empower teams; they adopted the vocabulary because it provided a more granular way to track exactly how much blood they could squeeze from a stone in a 29-day cycle. It is a cargo-cult of efficiency where the rituals are performed with religious fervor, but the gods of productivity have long since left the building.

In our office, the ‘Done’ column is a lie we tell ourselves so we can sleep at night. We have 39 different statuses in Jira, ranging from ‘In Discovery’ to ‘Refining the Refinement.’ It’s a labyrinth designed to hide the fact that nobody actually knows what the customer wants, including the customer. Rick loves the charts. He prints out the burn-down charts and pins them to the wall like they’re holy relics. If the line doesn’t go down at the right angle, he starts asking about ‘commitment.’

Measuring the Unmeasurable

I think about how different this is from actual structural integrity. In the world of physical construction, you can’t just ‘pivot’ the foundation of a building after the concrete is poured. You have to get the fundamental system right from the start. This is why I find the approach of WELLCAMP so interesting.

This is why I find the approach of container house factoryso interesting. They deal in modularity, but it’s a modularity based on the reality of physics and materials, not just the whims of a project manager who read a book on Scrum. In their world, the modules are designed to work together because they have to; the efficiency is baked into the physical design, not forced through a series of endless, soul-crushing meetings. They aren’t pretending to be ‘agile’ by changing the names of their problems; they are solving the problems through better structural thinking.

Velocity Over Craftsmanship

I once made a massive mistake because of this ‘commitment’ culture. It was back in the summer of 2009. I was so focused on hitting the sprint goal-which was an arbitrary deadline for a feature no one used-that I ran a script to clean up the production database without double-checking the ‘where’ clause. I deleted 199 gigabytes of user data in the time it took to blink. Why? Because I was rushing to meet a velocity target. I was being ‘Agile’ by moving fast, but I was actually being a disaster because I was being watched. When you are under constant surveillance, you stop thinking about the work and start thinking about the appearance of the work. You stop being a craftsman and start being a performer.

This is the core of the frustration. The daily stand-up is supposed to be for the developers. It’s supposed to be a moment where we say, ‘Hey, I’m stuck, can you help?’ Instead, it’s a status report for the manager. It’s a way for Rick to fill his spreadsheet so he can look busy in the next meeting with the directors. It’s 15 minutes of grilling, where every ‘blocker’ is treated as a personal failure of foresight.

Flattening the Symphony

Ava C. once told me about a volunteer who tried to bring a stopwatch into a hospice room to ensure they were ‘maximizing their impact.’ She had to fire him, of course. You can’t maximize impact with a stopwatch. You can only maximize anxiety. That’s what our version of Agile has done. It has taken the natural rhythm of creative work-the ebbs and flows, the moments of deep focus followed by periods of reflection-and tried to flatten it into a constant, frantic hum. It’s like trying to play a symphony at 2x speed and wondering why the music sounds like noise.

We’ve lost the plot. The Agile Manifesto has four values and twelve principles, and none of them mention Jira, story points, or standing in a circle while a guy in a fleece vest interrogates you. We’ve traded ‘individuals and interactions’ for ‘processes and tools,’ which is exactly what the founders told us not to do. We’ve created a system of micro-management that is more pervasive than the old waterfall model because it happens every single day.

Replacing Tracking with Trust

I look at the clock. It’s 9:29 AM. We are 14 minutes over. Rick is still talking about ‘granularity.’ I decide, right then, that I am done with the performance. When it’s my turn, I’m just going to say, ‘I’m working on the thing, and it’ll be done when it’s done.’ Rick will hate it. He’ll probably put a red flag on my ticket. He might even schedule a ‘one-on-one’ to discuss my ‘engagement.’