Corporate Agile: The Art of Self-Sabotage
Description
A three-panel comic strip using the 'Bicycle Fall' meme format to satirize corporate project management. In the first panel, a man confidently rides a bicycle, which is labeled 'Software development project'. In the second panel, the same man intentionally shoves a stick into the front wheel of his bike, causing it to stop suddenly. The stick is labeled with the text: 'Set arbitrary deadlines, budget a year ahead and take estimates as promises'. In the final panel, the man lies on the ground, injured from the crash, blaming an external force with the words 'damn agile'. The comic is a potent critique of how companies often self-sabotage their software projects with rigid, waterfall-style planning (fixed deadlines, budgets, and treating estimates as commitments) and then ironically blame the failure on the Agile methodology they claim to be following. It highlights a common frustration among experienced developers where the process is scapegoated for poor management decisions
Comments
7Comment deleted
This is what happens when management reads the Agile manifesto and concludes that 'responding to change' means changing the deadline to be sooner and 'customer collaboration' means promising them every feature they can think of
Enterprise Agility in one slide: freeze scope a year ahead, budget CapEx like it’s waterfall, call estimates “commitments,” and when the roadmap faceplants, schedule a “fix Agile” workshop
After 20 years in the industry, I've learned that 'Agile' is what management calls it when they want waterfall timelines with startup flexibility - essentially asking for a distributed system with ACID guarantees and eventual consistency at the same time
This perfectly captures the 'Agile' transformation at most enterprises: we'll keep all the rigid waterfall constraints - fixed scope, fixed budget, fixed timeline a year out - but now we'll have standups and call estimates 'commitments.' Then when physics inevitably asserts itself and the project crashes, we'll blame 'agile' instead of acknowledging we just did waterfall with extra meetings. The real tragedy? The bike was working fine in panel one before management got involved
If your “agile” fixes scope, date and budget in Q1 and treats story points as SLAs, that’s not Scrum - it’s Water-Scrum-Fall with estimates-as-commitments jammed in the spokes
Bike was agile; deadlines were the waterfall model pulling it off the cliff
Enterprise Agile: turn a forecast into a contract, nail scope to the calendar, hit the cone of uncertainty, then blame Agile in the postmortem