The 37-Minute Stand-Up

I am shifting my weight from the left foot to the right, feeling the thin, industrial carpet tiles compress under my heels. The fluorescent hum overhead is syncopated with the rhythmic, irritating tapping of a pen against a mahogany table-a table we aren’t even supposed to be sitting at because this is officially a ‘stand-up.’ We have been here for 37 minutes. Gary, our Scrum Master-who was a Senior Project Manager exactly 17 days ago-is hovering over a digital board that looks like a neon game of Tetris. He is asking Sarah why her ticket is still in ‘In Progress.’ Sarah is explaining, for the 7th time this week, that she is waiting on the API credentials from the security team. Gary nods, taps a stylus against his tablet, and then moves to the next person on the screen. He is not removing blockers; he is collecting data points for a report that 27 people will receive and 0 people will actually read.

At 2:07 am this morning, I was standing on a rickety kitchen chair trying to silence a smoke detector that had decided to chirp every 47 seconds. I replaced the battery, a $$7 ritual performed in the dark with blurry eyes, only to realize that the detector itself was 17 years old and essentially a plastic paperweight. The internals were fried, but the ritual of the battery change was the only thing I knew how to do in my sleep-deprived state. That is exactly what this meeting feels like. We are replacing batteries in a dead system, hoping the ritual of the status update will somehow keep the house from burning down, while the actual fire is the fact that we haven’t shipped a meaningful line of code in 7 weeks.

The Negotiator’s View

Maya N. is sitting in the corner, her presence a sharp contrast to the soft, corporate fatigue in the room. She isn’t a developer; she’s a union negotiator with 37 years of experience in the trenches of labor disputes and contract law. She was brought in as a consultant to look at ‘workflow efficiency’ from the human perspective, but mostly she just watches us with a look of profound, weary amusement. She has seen better bluffs in basement poker games. Maya doesn’t care about our ‘velocity’ or our ‘burndown charts.’ She understands that the contract isn’t the work, and the ceremony isn’t the result.

“

“Gary,” she says, her voice cutting through the technical jargon like a rusted blade through silk, “you’ve asked Sarah about those credentials 7 times. If the security team hasn’t given her the keys, what does her ‘status’ matter? You’re tracking the wind speed while the boat is stuck in the mud. You aren’t being agile; you’re just being loud.”

Gary flinches. He likes his rituals. Rituals provide the illusion of control and the comfort of predictability. If he follows the Scrum Guide, he can tell his superiors that he followed the process, regardless of whether the product actually works. It is the classic ‘Cargo Cult’ mentality. In 1947, after the Great War, certain island tribes in the Pacific saw planes landing with incredible cargo. When the soldiers left, the planes stopped. The tribes, wanting the cargo to return, built runways out of straw and carved headphones out of wood. They sat in control towers made of bamboo and waited. They had the form, but they lacked the underlying infrastructure of global logistics and combustion engines. Corporate Agile is our bamboo headset. We have the sticky notes, the stand-ups, and the funny names for meetings, but we lack the trust and autonomy that actually makes a team move fast.

Vocabulary as Control Mechanism

We have 47-page manuals on how to ‘be agile.’ We hire consultants at $777 an hour to tell us that we need to ‘pivot’ and ‘fail fast,’ while our actual release cycles are still measured in 7-month chunks. Management loves the vocabulary because it sounds innovative. They can say ‘sprint’ instead of ‘deadline’ and feel like they aren’t the ones causing the burnout. Maya N. sees through this instantly. To her, a ‘sprint’ is just a way to squeeze 47 hours of work into a 37-hour week without paying overtime. She views the Jira board as a digital picket line that the developers are too tired to realize they are standing on.

There is a specific kind of cognitive dissonance that occurs when you are told you are ‘self-organizing’ while being micro-managed every 27 hours. We spend 17% of our week in meetings about what we are going to do during the other 83% of the week, but that remaining time is eaten up by the 7 layers of approval required to change a button color. The process has become the product. We are so busy maintaining the bamboo runway that we’ve forgotten what the cargo was supposed to be.

The Absence of Trust

Maya leans forward, her glasses sliding down her nose. She mentions that in her 37 years of negotiating, the most successful agreements weren’t the ones with the most pages, but the ones where people actually trusted each other to do what they said they would do. In this room, there is no trust. There is only the board. If it isn’t on the board, it didn’t happen. If it is on the board but the API is broken, Gary just moves the sticky note to ‘Blocked’ and feels like he’s done his job for the day.

This reminds me of why I respect organizations that prioritize the mission over the mechanics. For instance, when a visitor engages with Zoo Guide, the underlying goal isn’t to marvel at the efficiency of the software development lifecycle that created the app. The goal is conservation education. The technology is a bridge to help a human being connect with the reality of an endangered species. If the bridge is beautifully ‘agile’ but leads nowhere, it’s a failure. In our office, we’ve spent $777,000 this year on ‘Agile Transformation’ while our actual goal-shipping a usable interface-is 17 months behind schedule. We are polishing the bridge while the river underneath has long since dried up.

The Illusion of Maturity

I think about the 7th floor, where the executives sit. They look at the 87% ‘Agile Maturity’ score the consultants gave us and they smile. They don’t see the 777 lines of redundant code Sarah had to write to bypass a security protocol that Gary didn’t have the authority to fix. They don’t see the exhaustion in the eyes of the junior devs who are on their 17th consecutive day of ‘sprinting.’ They only see the ceremonies. They see people standing up, so they assume we are moving.

“

“The problem,” Maya said during our 7-minute coffee break, “is that you’ve turned a philosophy of freedom into a technology of surveillance.”

She’s right. Agile was meant to give developers the power to respond to change. Instead, it has been used to track their every movement with 27-point story estimates that are essentially guesses disguised as mathematics. We are asked to estimate the unknown with a precision that would make a surgeon blush, and then we are punished when the unknown remains… well, unknown.

Standing Still in Motion

I’m looking at the clock. It is now 47 minutes into the stand-up. My lower back is beginning to ache, a dull reminder of the 2:07 am chair-climbing incident. We have reached the part of the meeting where we ‘sync’ on things that could have been an email sent 7 hours ago. Gary is happy. The board is updated. The ritual is complete. He dismisses us with a cheery reminder that we have 7 days left in the sprint and we are ‘behind our committed velocity.’

As we walk back to our desks, Maya N. catches my eye. She doesn’t say anything, but she shakes her head slowly. She knows that by 7 pm tonight, half the team will still be here, trying to make up for the time we spent standing in a circle talking about why we aren’t working. We are building a bamboo world, and we are all waiting for the cargo that will never come. The smoke detector in my hallway is still probably dead, and so is the spirit of this project. But hey, at least we followed the process. At least we stayed standing for the full 47 minutes. In the kingdom of the blind, the man with the 7-step plan is king, even if he’s leading everyone straight off a cliff.