The Illusion of Completion
Sliding my thumb across the trackpad, I watch the ‘Complete Sprint’ button hover in a state of digital purgatory while 11 pairs of eyes drill into the back of my neck from across the conference table. The screen is projected onto the wall, a giant, glowing testament to our collective delusion. We are finishing Sprint 41. We have checked all the boxes. We have moved all the cards. Yet, as I look at the face of the Lead Architect, I see the same vacant stare I saw 11 months ago when we first white-boarded this entire disaster. It is the stare of someone who knows the ending of the movie but is forced to sit through the previews anyway.
In the room, the air smells faintly of burnt coffee and the unspoken realization that we aren’t actually building anything new. We are just executing a plan that was etched into a granite-slab roadmap back in January. The stakeholder in the corner, a man whose tie is always exactly 1 inch too short, clears his throat. ‘It looks good,’ he says, ‘but can we change the user flow for the checkout?’ Our Product Manager, a person who treats the Jira backlog like a holy relic, doesn’t even blink. ‘Sorry,’ she says with a smile that doesn’t reach her eyes, ‘the requirements for the checkout module were locked in 21 weeks ago. We can add your feedback to the backlog for Q1 of next year.’
The Hospice Principle: Responding to Now
I’m Maria B.-L., and when I’m not navigating these corporate rituals, I’m a hospice volunteer coordinator. It’s a strange mix, I know. But in hospice, you learn very quickly that plans are just polite suggestions we make to the universe. You can’t ‘sprint’ through grief, and you certainly can’t roadmap a graceful exit. You have to be present. You have to react to the person in front of you, right now, in this moment. If a patient suddenly wants to see the ocean, you don’t tell them to put it in the backlog for Q4. You find a way to get them to the water.
Confusing Output with Outcome
Velocity Increase
Actual Users
We were the most efficient builders of a ghost town in the history of the company. We’ve turned ‘Agile’ into a micromanagement tool.
In the software world, we’ve lost that immediacy. We’ve traded the ‘Agile Manifesto’s’ value of ‘responding to change over following a plan’ for a set of ceremonies that actually make change harder. By the time we get to a sprint review, we’ve invested so much into the ‘process’ that any deviation feels like a failure rather than a pivot. I remember once, I was walking down the street and I saw someone waving frantically. I waved back, a big, enthusiastic gesture, only to realize a split-second later they were waving at the person standing 1 foot behind me. That’s exactly how it feels when we demo a feature that the market has already moved past. We’re waving at a ghost, pretending we’re still relevant because we followed the Scrum Guide to the letter.
“
[The process has become the product.]
The Frankenstein Monster: Water-Scrum-Fall
This obsession with the ‘how’ instead of the ‘why’ is a symptom of a deeper cultural rot. It’s a fear of the unknown. Real agility is terrifying to a traditional corporate structure because it requires trusting the people on the ground. It requires admitting that we don’t know what the world will look like in 101 days. Command-and-control mindsets love Waterfall because it feels like a safety net. You have a document. You have a signature. You have someone to blame when the $100,001 project fails because ‘they didn’t follow the specs.’
When we try to graft Agile onto that mindset, we end up with this Frankenstein’s monster: ‘Water-Scrum-Fall.’ We do big-up-front design for 2 months, then we do 11 days of development in sprints, and then we spend 1 month in QA and deployment. It’s the worst of both worlds. You lose the predictability of Waterfall and the flexibility of Agile. You’re just stressed, all the time, forever.
The True Measure of Agility
Hospice Focus
Singular focus on the outcome (patient well-being).
Tech Focus
Confusing output (shipping features) with impact.
The Need
True agility means having the autonomy to adapt.
Burning the Roadmap
If you want to break out of the theater, you have to start by burning the roadmap. Or at least, acknowledging that the roadmap is a work of fiction. Stop planning for Q4 when you haven’t even seen how users react to Q1. Give your teams the autonomy to say ‘no’ to a feature if it doesn’t make sense anymore, even if it was promised in a PowerPoint deck 121 days ago. And for heaven’s sake, stop using standups as a roll call.
Actually, I have a confession. I still use a Kanban board to manage my volunteer schedules. I know, I know. I just spent 801 words complaining about the process, and here I am, dragging cards across a screen. But that’s the contradiction, isn’t it? The tool isn’t the problem. The spirit in which we use the tool is the problem. My board is a map of human needs, not a cage for human activity. It’s fluid. If a volunteer gets sick, the card moves. There is no ‘failed sprint’ because the goal isn’t to clear the board; the goal is to show up.
We need that ‘showing up’ energy in our development teams. We need to stop pretending that we can predict the future with 100% accuracy. The most successful projects I’ve ever seen weren’t the ones with the best documentation; they were the ones where the developers felt empowered to change direction when they hit a wall. They had the right infrastructure, the right support, and the right to be wrong.
Infrastructure Mirroring Gridlock:
When you finally realize that your rigid software cycles are killing your innovation, you start looking for platforms that don’t box you in. You need the underlying power to be as fluid as the ideas you’re supposedly chasing. Using
for hosting gives you that architectural breathing room, allowing you to scale and pivot without the typical infrastructure bottlenecks that often mirror our organizational gridlock. It’s about having the technical agility to match your (hopefully) newfound cultural agility.
Measuring What Matters
I’ve spent 41 hours this week thinking about why we cling to these rigid structures. I think it’s because it’s easier to measure a sprint than it is to measure impact. Impact is messy. Impact is qualitative. Impact requires you to actually talk to people and listen to their frustrations. It’s much easier to just look at a burn-down chart and see a line going down. It gives us a sense of accomplishment, even if we’re just running in place.
The Path to Genuine Change
Phase 1: Following the Plan (Jan)
Commitment to Specs
Phase 2: Hitting the Wall (Now)
Waving at a ghost feature.
Phase 3: Honest Conversation
Asking the right question.
In hospice, the impact is undeniable. You see it in the way a family breathes a little easier when a volunteer arrives. You see it in the silence of a room where someone is no longer alone. There are no charts for that. There are no story points for a hand held. Maybe we should start measuring our software development the same way. Not by how many features we shipped, but by how much easier we made someone’s life.
Stopping the Performance
Real change is uncomfortable. It requires us to admit that the person waving might not be waving at us. It requires us to be okay with the embarrassment of being wrong. It requires us to stop performing and start building. We have to stop the theater. We have to stop the 11-minute-status-reports-disguised-as-standups. We have to stop the roadmaps that stretch out until the end of time.
The silence that follows is deafening. It’s the sound of 11 people realizing that we’ve been so busy following the process that we forgot the purpose. The stakeholder with the short tie looks surprised. The Product Manager looks panicked. But the developers? They look relieved. For the first time in 31 days, we’re actually having a conversation. We’re not performing. We’re not checking boxes. We’re just human beings in a room, trying to figure out how to do something that matters.
It’s not ‘Agile’ as defined by some certified consultant. It’s not ‘Scrum’ as defined by a 201-page manual. It’s just… honest. And in a world of corporate theater, honesty is the most radical form of agility there is. We might not have a roadmap for what happens next, and we definitely don’t have the requirements locked in for next year, but for the first time in a long time, I think we’re actually moving in the right direction. And if we get it wrong? We’ll just wave at the mistake, laugh at the awkwardness, and try something else tomorrow. That’s the only sprint that really counts.