The Performance of Completion

Sarah is leaning so far into her monitor that I can see the reflection of 13 unread Slack messages in her glasses, her cursor hovering over a Jira ticket like a hawk over a field mouse. She doesn’t look up when the door to the museum’s Annex 3 creaks open. She just clicks. There. The ticket is moved from ‘In Progress’ to ‘Done.’ Except, of course, it isn’t done. It’s just been pushed into the next phase of a very long, very rigid plan that we’ve collectively agreed to call ‘Agile.’ We’re in the middle of a sprint planning session, which is really just a polite way of saying we’re deciding which lies to tell ourselves for the next 13 days.

The Agile Shield

I’m Hugo D.R., the museum education coordinator, but lately, I feel more like a stage manager for a play that nobody wants to watch. My job is to ensure the educational content matches the digital interface, but the interface is a moving target that somehow always hits the same wall. I’m currently riding the high-or maybe the low-of winning an argument I knew I was wrong about. Last week, I insisted that the server couldn’t handle 233 concurrent connections for the virtual tour. I threw out numbers like ‘latency overhead’ and ‘concurrency bottlenecks.’ I was lying through my teeth; the server could handle three times that. But I wanted more time to finish the curriculum guides, and I won.

“They apologized. I felt powerful, then immediately felt like a fraud. Now, I’m watching the team scramble to ‘optimize’ a system that was fine, all because I used the ‘Agile’ shield to block a request I didn’t like. It’s a dirty habit, using the process to hide the truth.”

This is the fundamental rot at the heart of modern development. We’ve taken the visible rituals-the standing up, the sticky notes, the 13-minute retrospectives-and we’ve pasted them over a culture that still demands the illusion of total control. It’s a cargo cult.

Velocity Without Direction

We build wooden Jira boards and hold daily stand-ups, hoping the ‘Agile’ spirits will grant us productivity, while the managers in the boardroom are still counting down the days on a Gantt chart they printed 3 weeks ago. There is no trust here. There is only the performance of flexibility.

If we were actually agile, we would be able to say, ‘Hey, this 83-page requirement document is actually quite bad, and we should change it based on what we learned yesterday.’ But you can’t say that. If you say that, you’re ‘not a team player.’ You’re ‘disrupting the velocity.’ Velocity. What a beautiful, terrifying word. It implies we’re going somewhere fast, but it says nothing about the direction.

Slaves to the Increment

I think about the way we curate exhibits. It’s the same pathology. We spend 153 days planning the placement of a single Mesopotamian urn. We have meetings about the font size on the placards. Then, 3 days before the opening, someone decides the lighting is all wrong. Instead of adjusting, we just stick to the plan because the ‘sprint’ is over. We’ve become slaves to the increments. We’ve forgotten that the goal isn’t to finish the sprint; the goal is to build something that doesn’t suck.

In the rare moments when I look past our internal mess, I see entities like Fourplex that actually understand how to bridge the gap between high-level ambition and the messy reality of code without resorting to these theatrical performances. They seem to understand that the software isn’t the point; the problem-solving is.

Painting the Portrait in Shakes

Every Friday, we have a ‘Demo.’ This is the part of the play where we show off what we’ve ‘built.’ Usually, it’s just a series of 13 screenshots of a UI that doesn’t actually connect to a database yet. We all clap. We say ‘great job on the velocity.’ Then we go back to our desks and try to figure out how to bridge the 83-mile gap between the demo and the reality of the code. It’s exhausting. It’s like trying to paint a portrait while someone is constantly shaking the ladder and asking you for a status update every 3 minutes.

I sometimes wonder if anyone actually believes in the process, or if we’re all just participating in a collective delusion because it’s easier than admitting we’re lost.

Managing Emptiness in Intervals

The museum is quiet tonight. I stayed late to look at the new exhibit layout. There are 13 pedestals waiting for artifacts. They look like the empty boxes on our Jira board. We’ve planned the ‘sprint’ for the installation, but we haven’t even secured the insurance for the pottery yet. It’s the perfect metaphor for our software. We have the pedestals, we have the labels, we have the ‘Agile’ ceremonies, but we don’t have the actual thing. We’re just managing the emptiness in two-week intervals.

We talk about ‘pivot’ and ‘iteration,’ but we’re actually just marching. It’s a forced march through a swamp, and we’re all pretending the mud is a refreshing spa treatment. I’ve started counting the number of times Sarah uses the word ‘alignment’ in a single meeting. Yesterday it was 33. On Tuesday, it was 43. It’s a linguistic tic, a way to fill the silence when no one knows what they’re doing. We’re aligned, alright. We’re all aligned in our commitment to the ritual over the result.

There’s a specific kind of tiredness that comes from pretending to be ‘Agile’ while being crushed by the weight of a 123-page project plan. You’re not just tired from the work; you’re tired from the acting. You’re tired of the ‘Story Points’ which are just hours in a funny costume. We’ve turned a philosophy of liberation into a tool of surveillance.

The Final Performance

I’m looking at the 13th ticket again. It’s titled ‘Refactor Education API.’ I’m the one who wrote it. I’m the one who will probably be the reason it gets ‘carried over’ to the next sprint. I’ll come up with a reason. I’ll say there was a ‘dependency’ that we didn’t account for. I’ll win the argument. Everyone will nod, Marcus will sigh his 43rd sigh of the day, and we’ll all go back to our desks to prepare for the next performance.

Is this what we wanted? Is this the peak of software development? Or are we just 13 people in a room, waiting for someone to be brave enough to admit that the emperor is not only naked but is also 13 weeks behind schedule?