The Cult of Agile: Why Smart People Believe Stupid Things
The Sunk Cost Fallacy at Scale
Companies have invested so heavily in Agile that admitting failure becomes psychologically impossible:
The Investment Trap:
- Millions in consultant fees
- Thousands of hours in training
- Entire departments of Scrum Masters
- Careers built on Agile expertise
- Reputations staked on transformation
The Cognitive Dissonance:
When faced with failure, organizations don’t question Agile—they blame themselves for not being “Agile enough.” This creates an endless cycle of doubling down on a failing approach.
The Cargo Cult Problem
Richard Turpin identified a critical pattern: organizations copy the rituals without understanding the principles. They see Spotify’s success and copy their “squad model.” They hear about ING’s transformation and mimic their structure.
The Reality:
- Spotify doesn’t even use the “Spotify model” anymore
- ING’s success had nothing to do with Agile
- Copying structure without context guarantees failure
- 95% of transformations just cargo cult what others did
The Waterfall Leadership Paradox
Professor John Kotter states he’s never seen a successful long-term Agile transformation with Waterfall leadership. Yet 95% of Agile transformations have exactly that.
The Fatal Contradiction:
- Leadership thinks in quarters and years
- Agile teams think in sprints and days
- Leadership wants predictability
- Agile promises adaptability
- Leadership demands fixed scope/time/budget
- Agile requires flexible everything
The Hidden Mathematics of Agile Failure
The Complexity Multiplication Effect
Agile doesn’t reduce complexity—it redistributes and amplifies it:
Traditional Project:
- One plan to maintain
- One timeline to track
- One budget to manage
- Clear success criteria
Agile Project:
- 26 sprint plans per year
- Constantly shifting timelines
- Budget consumed in unpredictable chunks
- Success criteria that “emerge”
The Overhead Explosion:
Every two-week sprint requires:
- Planning (complexity: n)
- Execution (complexity: n)
- Review (complexity: n)
- Retrospective (complexity: n)
- Adjustment (complexity: n²)
Total complexity: 5n × 26 sprints = 130n annual complexity units vs. n for traditional approach.
The Communication Catastrophe
Agile’s emphasis on “individuals and interactions” creates an exponential communication burden:
Team Communication Load:
- 5-person team: 10 communication channels
- 10-person team: 45 channels
- 20-person team: 190 channels
- Formula: n(n-1)/2
Daily Standup Dysfunction:
- 10 people × 3 minutes each = 30 minutes
- 30 minutes × 5 days × 50 weeks = 125 hours/year
- 125 hours × 10 people = 1,250 person-hours
- Cost at $100/hour: $125,000 annually just to say what you did yesterday
The Technical Debt Timebomb
Agile’s sprint focus creates systematic technical debt:
The Accumulation Pattern:
- Sprint 1: Ship quick solution (debt: x)
- Sprint 2: Ship another quick solution (debt: 2x)
- Sprint 3: First solution breaks (fix + new debt: 4x)
- Sprint n: Exponential debt accumulation
The Horizon Post Office Scandal proved this catastrophic:
- Rapid Application Development (early Agile)
- No robust requirements engineering
- Technical debt compounded for years
- Result: 700+ wrongful prosecutions
Why Impact Engineering Succeeds Where Agile Fails
Dr. Ali’s research identified five practices that reduce failure by 6.5x:
1. Robust Requirements Engineering
- 97% more likely to succeed with clear requirements
- 54% more likely when requirements match real problems
- Agile actively discourages this
2. Psychological Safety
- Projects with psychological safety 87% more likely to succeed
- Agile’s “fail fast” creates fear, not safety
- Blame for “not being Agile enough” destroys trust
3. Preventing Developer Burnout
- 83% of developers report burnout
- Agile’s endless sprints create hamster wheel effect
- Sustainable pace impossible with constant ceremonies
4. Problem-Solution Fit
- Start with real problems, not user stories
- Validate solutions against actual needs
- Measure impact, not velocity
5. Engineering Discipline
- Technical excellence over process adherence
- Code quality over feature quantity
- Long-term sustainability over short-term delivery
The Binary Choice: Agile Theater or Actual Agility
You face a simple decision:
Continue Agile Theater:
- Keep running sprints to nowhere
- Measure velocity while value plummets
- Conduct ceremonies that produce nothing
- Watch 96% of transformations fail
- Join the 67% that end in bankruptcy or acquisition
Build Actual Agility:
- Define clear requirements upfront
- Create psychological safety for real discussion
- Prevent burnout with sustainable practices
- Solve real problems with engineering discipline
- Join the 10% that actually succeed
The Uncomfortable Truth About Your Transformation
Your Agile transformation is probably already dead. The consultants know it. Your developers know it. Deep down, you know it. But the sunk costs, the political capital, the careers built on Scrum certifications—they all demand you pretend otherwise.
The math is undeniable:
- 96% failure rate for adaptability
- 268% higher project failure rate
- 67% end in terminal failure
- 30% deliver no business value
You’re not failing because you’re “not Agile enough.” You’re failing because Agile, as practiced, is a recipe for failure. It’s a methodology that actively prevents the very things that make projects succeed: clear requirements, sustainable pace, engineering excellence, and long-term thinking.
The Path Forward: From Agile to Agility
Real agility doesn’t come from ceremonies and sprints. It comes from:
1. Requirements Reality
- Spend time understanding the problem
- Document what you’re building and why
- Validate with real users before coding
- Change when needed, but know what you’re changing from
2. Sustainable Excellence
- Build at a pace you can maintain for years
- Invest in architecture and infrastructure
- Pay down technical debt continuously
- Measure value delivered, not points completed
3. Psychological Safety
- Admit when things aren’t working
- Question processes that don’t add value
- Support developers who raise concerns
- Value truth over methodology
4. Engineering First
- Let engineers engineer
- Minimize meetings, maximize making
- Trust technical judgment
- Build for the long term
Your Agile Apocalypse Moment
Right now, your organization is either recognizing Agile’s failure or doubling down on delusion. The evidence is overwhelming. The mathematics are undeniable. The graveyard is full of companies that achieved perfect Scrum implementation on their way to bankruptcy.
The question isn’t whether Agile is failing—it’s whether you’ll admit it before it’s too late.
Because every day you continue the sprint to nowhere, every ceremony that produces nothing, every story point that measures meaningless velocity—you’re not just wasting time and money. You’re building your own corporate coffin, one sprint at a time.
The clock is ticking. Your competitors who abandoned Agile theater for actual engineering excellence are pulling ahead. Your developers are burning out. Your projects are failing at record rates.
What will it be: Another retrospective about why the last sprint failed? Or the courage to admit that the emperor has no clothes, the methodology has no merit, and it’s time to try something that actually works?
The 96% are waiting for you to join them in failure. The 4% are waiting for you to wake up.
Choose wisely. Choose quickly. Choose based on evidence, not ideology.
Because in the end, working software beats perfect Scrum. Every. Single. Time.
Todd Hagopian has transformed businesses at Berkshire Hathaway, Illinois Tool Works, Whirlpool Corporation, and JBT Marel, selling over $3 billion of products to Walmart, Costco, Lowes, Home Depot, Kroger, Pepsi, Coca Cola and many more. As Founder of the Stagnation Intelligence Agency and former Leadership Council member at the National Small Business Association, he is the authority on Stagnation Syndrome and corporate transformation. Hagopian doubled his own manufacturing business acquisition value in just 3 years before selling, while generating $2B in shareholder value across his corporate roles. He has written more than 1,000 pages (coming soon to toddhagopian.com) of books, white papers, implementation guides, and masterclasses on Corporate Stagnation Transformation, earning recognition from Manufacturing Insights Magazine and Literary Titan. Featured on Fox Business, Forbes.com, AON, Washington Post, NPR and many other outlets, his transformative strategies reach over 100,000 social media followers and generate 15,000,000+ annual impressions. As an award-winning speaker, he delivered the results of a Deloitte study at the international auto show, and other conferences. Hagopian also holds an MBA from Michigan State University with a dual-major in Marketing and Finance.