The 9-Month Roadmap in a 9-Day Sprint
The Ritual of Pre-Determined Outcomes
“So, this 49-point list is non-negotiable?” The Product Owner didn’t meet my eyes; he was scrolling through his boss’s email, reading the demands aloud. This wasn’t planning; it was dictation. We were sitting in the brightly colored war room-a space designed, ironically, to facilitate collaboration. We call it “Sprint Planning,” but the sprint goal was predetermined by a VP who hadn’t spoken to a user in 9 months. We were just estimating tasks dictated from 9 floors up, assigning story points to features that smelled faintly of desperation and quarterly earnings calls. The estimation process itself-the ritual we performed every 9 days-was a lie. We knew the backlog priority had been swapped 3 times since Monday, but we kept shuffling the cards anyway, generating metrics for a dashboard nobody truly trusted. We performed the ceremony perfectly, yet we all knew the decisions were made before we walked in the door.
The paradox isn’t just irritating; it’s culturally corrosive. We adopted the costumes of agility. We have daily stand-ups that clock in at 9 minutes precisely. We use Jira and Confluence. We throw around terms like ‘MVP’ and ‘iterative delivery’ as if they were talismans capable of warding off the corporate demons of slowness.
The Annual Budget Cage
But then, the annual budget review hits. Suddenly, that fluid, adaptive backlog we preached about vanishes, replaced by a rigid, 18-month commitment document signed in triplicate. This document dictates scope, budget, and time, effectively paralyzing any genuine ability to respond to change. How can I possibly deliver a detailed, fixed-scope, fixed-price product 18 months out, when the entire philosophy I’m supposed to be following is built on learning and pivoting every 9 days?
Demands Certainty
Requires Trust
It forces us into a spectacular act of corporate theater. We spend half our time generating fake precision to satisfy the planning department, providing charts that project velocity 239 days into the future, and the other half trying to explain why the fake plan needs to change. The frustration isn’t with the tools; it’s with the fundamental deception. We are performing the rituals of trust without ever granting the trust itself.
Polishing the Glass While Ignoring the Ecosystem
I remember talking to Cameron S.-J. He’s an aquarium maintenance diver-a surprisingly relevant profession, trust me. Cameron doesn’t just skim the algae off the glass; he goes into the massive, public tanks, down where the filter systems run and the structural supports meet the floor. He told me the biggest mistake people make is cleaning the glass 9 times a day while ignoring the substrate and the pumps. Surface maintenance creates the illusion of a healthy system. You see the clean, happy fish, but the entire ecosystem is slowly collapsing beneath the aesthetic layer.
The Velocity Lie
V: High
Velocity
Auth: Req.
Authority
P: 979
Data Points
We are generating 979 data points of velocity for a team that has zero authority to reject a feature dictated from above.
That’s our adoption of Agile. We are polishing the glass (stand-ups, story points, velocity charts) while refusing to clean the substrate (the budget process, the power structure, the annual review cycle). We are celebrating the speed of the horse while refusing to accept that the horse is running on a broken leg.
The Unwillingness to Cede Control
It’s like demanding a marathon runner pivot mid-race to a 100m sprint, but judging their success based on the original marathon trajectory. This system isn’t designed to allow adaptation; it’s designed to punish deviations from the original commitment, regardless of market shifts or new information. The rigidity serves institutional comfort, not market success.
My core internal contradiction was this: I preached that the team must self-organize and push back against fixed scopes, yet I still held the final sign-off on the 18-month roadmap, because my bonus was tied to its stability. I criticized the leadership for lacking trust, while simultaneously using my positional authority to enforce the rules established by that same distrusting structure. It was an impossible position, and for 239 days, I blamed the methodology. My mistake wasn’t in adopting Agile; it was in believing I could implement a philosophy of rebellion without confronting the political structure that demanded conformity.
What happens when the budget is fixed? The cost is fixed. The schedule is fixed. The only variable left is scope. And when scope inevitably needs to be cut to hit those artificial deadlines, it’s not the big, shiny, visible features that go; it’s the quiet, necessary things: technical debt repayment, system refactoring, security hardening, thoughtful testing. We sacrifice long-term health for short-term visibility and the appearance of compliance.
This is not Agility; this is just high-frequency Waterfall.
We pretend the business value will magically remain the same, even though we are delivering a hollowed-out version of the original vision. This hollow core is the cost of protecting the annual budget cycle.
From Projects to Persistent Value Streams
To truly adopt agility, you have to accept that planning is a continuous activity, not an annual event. You must shift resource allocation from pre-defined projects to persistent teams focused on persistent value streams. If your company still spends 3 months debating capital expenditure for 2029 projects, you are not agile, no matter how many Jira tickets you close today. The budget isn’t just a number; it is a mechanism of power projection, defining who gets to make decisions and when.
The final metric isn’t velocity or story points. It’s the answer to this question: When a team discovers a genuinely better way to solve a user problem-a way that violates the 18-month roadmap signed 9 months ago-how quickly can they pivot, and whose permission do they need to ask? If the answer involves a committee meeting scheduled 49 days out, then the agile transformation hasn’t started. It has simply provided better, more frequent reporting on the rate of failure.
This deep integration of technical expertise and organizational strategy is critical, especially when navigating complex digital shifts. It’s what separates vendors who just install software from organizations like Eurisko who help redesign the operating model from the ground up, recognizing that true change is about structure and trust, not just tools.
-
Tagged Finance