I am staring at the tiny green pinhole of my webcam, and my nose still stings from the seventh sneeze in a row. It is a sharp, acidic sensation that makes my eyes water, which the twelve other faces on the Zoom grid likely interpret as emotional investment in our ‘Sprint Commitment.’ I am currently giving my third update of the morning. I said the same thing at 8:04 to the internal team. I repeated it at 9:14 to the cross-functional product group. Now, at 10:04, I am saying it to a group of stakeholders who, if I am being honest, look like they would rather be getting a root canal. No one is actually listening. They are rehearsing their own scripts, moving their lips silently like monks practicing a vesper before it is their turn to perform the ritual of ‘What I Did Yesterday.’
We have entered an era where the act of building software has been swallowed by the act of talking about building software. It is a peculiar kind of corporate gluttony. We consume hours in the name of efficiency, devouring the very focus required to actually produce the work we are discussing. The Agile Manifesto was written 24 years ago by a group of developers in a ski resort who wanted to escape the heavy, soul-crushing weight of waterfall bureaucracy. They wanted individuals and interactions over processes and tools. Yet, somehow, we have managed to build a brand new cathedral of process, complete with high priests, sacred artifacts, and a liturgy that must be followed with terrifying precision.
It is a management control system disguised as empowerment, a way to keep a 24-hour watch on the psychological output of professionals who are treated like children in a Montessori school.
The Banishing Weapon
I remember a specific moment during a retrospective 14 weeks ago. We were using a digital whiteboard to drag virtual sticky notes into columns labeled ‘Sad,’ ‘Mad,’ or ‘Glad.’ It felt like a therapy session for people who weren’t allowed to actually express their feelings. I made a mistake then. I decided to be honest. I told the group that I had spent 34 percent of my previous week in meetings about the work I wasn’t doing because I was in meetings. The room went silent.
If you point out that the emperor is naked and also happens to be holding a 54-page Jira backlog, you are silenced for the sake of the ‘flow.’
The Mystical Math of Estimation
We use Fibonacci numbers to estimate tasks. 1, 2, 3, 5, 8. We pretend these numbers have a mystical significance, as if we are tapping into the divine proportions of the universe to decide how long it takes to change a button color. Last Tuesday, we spent 24 minutes debating whether a bug was a 3 or a 5. The bug took 4 minutes to fix after the meeting ended.
The Reality of Estimation vs. Fixing (Hypothetical Data)
We are participating in a mass hallucination where we believe that if we can measure something, we can control it. But software is not a factory line. It is a creative endeavor that requires long, uninterrupted stretches of deep thought. You cannot ‘sprint’ indefinitely. In the real world, a sprint is a burst of energy that ends in exhaustion. In the corporate world, we are expected to sprint for 52 weeks a year, with only 14 days of vacation to recover from the perpetual motion of the hamster wheel.
The Craving for Permanence
This obsession with the abstract-the points, the burn-down charts, the velocity-creates a profound hunger for the tangible. I find myself sitting in my home office, looking at the flickering cursor, and wishing I were holding a hammer. There is a specific kind of exhaustion that comes from spending 84 hours a month in a digital void. It makes you crave things that are permanent.
This is why I spent my lunch break looking at Sola Spaces. There is something deeply honest about a sunroom. It is made of glass and steel. It serves a singular, beautiful purpose: to let the light in. You do not need a retrospective to decide if the glass is transparent enough. It just exists.
Trust vs. Surveillance
Reese L. recently analyzed a 144-point intersection where the city had installed ‘smart’ sensors to manage congestion. The sensors were designed to be ‘agile,’ adjusting in real-time to the flow of cars. The result was a disaster. The constant shifting of the lights confused the drivers, leading to a 34 percent increase in minor collisions. The solution? They turned the sensors off and went back to a simple, predictable timer.
Sometimes, the best way to manage a complex system is to stop trying to micromanage every micro-movement. We have forgotten how to trust people to do their jobs. We have replaced trust with ‘transparency,’ which is just a polite word for surveillance.
I recently realized that I have started lying in my stand-ups. Not about big things, but small ones. I will say I am ’94 percent finished’ with a task when I haven’t even started it, simply because I know I can finish it in two hours of focused work tonight after everyone else has gone to sleep. I lie to protect my time. I lie to keep the management from ‘helping’ me. If I tell the truth-that I spent the morning thinking about the architecture instead of typing-I am flagged as an impediment. Agile has created a culture where ‘doing’ is valued more than ‘thinking,’ and where appearing busy is more important than being effective.
The Data Illusion
Drowning in Data
Starving for Clarity
The Dignity of the Permanent
I think back to the seventh sneeze that started this morning. It was a physical reality, a biological necessity that interrupted the digital facade. It was more real than any story point I have assigned this year. We need to find our way back to that reality. We need to stop worshiping at the altar of the Jira board and start focusing on the craft again.
There is a certain dignity in building something that lasts. When you look at a well-crafted structure, like a sunroom, you see the result of thousand-year-old principles of physics and aesthetics. There are no ‘pivots’ in a load-bearing wall. There are no ‘minimum viable products’ when it comes to keeping the rain out. You do the work correctly the first time because the consequences of failure are physical and immediate.
Walking Away from the Green Light
I am tired of the ceremonies. I am tired of the 104-page slide decks explaining why our velocity dropped by 4 percent. I want to build things that matter. I want to spend my days solving problems, not explaining how I plan to solve them to a group of people who aren’t going to help. Maybe the answer isn’t a better project management tool. Maybe the answer is to look out the window, past the glare of the screen, and remember that the world is made of more than just pixels and points.
The next time the green light of the webcam blinks on, I might just leave it off. I might just go outside and sit in the sun, where the only ‘sprint’ is the wind moving through the trees, and the only ‘stakeholder’ that matters is the quiet realization that the work is finally done.
Find Your Sunlight Structure