Is Agile methodology a revolutionary approach to software development, or has it become corrupted into expensive consulting theater that ignores organizational context and culture? Watch the show for the 5 big things you need to know about agile.

We Discuss:

• Where did Agile come from and what is its background?
• Does it matter where the concept of Agile started if it works?
• Is there data to support that Agile fails more often than it succeeds in large enterprises?
• What should individual practitioners do when they’re stuck on an Agile team that feels like bullshit?
• What do developers actually think about Agile frameworks in practice?

Key Highlights:

• Agile is often implemented poorly because it’s used as an excuse to avoid process rather than being properly understood (00:02:56)
• Agile originated from the 2001 Agile Manifesto created by software leaders like Kent Beck, Martin Fowler, and Jeff Sutherland, not from Toyota/Lean manufacturing as commonly believed (00:04:59)
• There’s a distinction between “Agile” (Capital A – the sold framework) and “agility” (lowercase a – being a nimble, responsive organization) (00:07:23)
• Successful tech companies like Google, Facebook, and Uber don’t explicitly do “Agile” or SAFe – they customize practices to fit their culture (00:10:28)
• Agile works poorly in highly regulated industries where waterfall may be more appropriate (00:14:46)
• The Department of Defense released a guide called “Detecting Agile BS” to help identify consultants who are full of it (00:15:38)
• Context matters enormously – organizations must understand their culture, capabilities, and readiness before adopting Agile (00:19:03)
• The core principles of Agile align with Deming’s 14 points and lean manufacturing – it’s systems thinking applied to software (00:25:45)
• Practitioners stuck in failed Agile implementations should lead from behind, educate management, and demonstrate what actually works (00:28:23)
• The root problem is that companies hiring Agile consultants aren’t having the necessary conversations about culture and capability (00:33:41)

5 Takeaways:

1. Agile itself isn’t bullshit, but the way it’s commonly sold by consulting firms—as a one-size-fits-all solution without considering organizational context—often is bullshit.
2. Successful implementation requires understanding your organization’s culture, people capabilities, existing processes, and appetite for change before attempting any Agile transformation.
3. Top technology companies like Google, Facebook, and Uber don’t rigidly follow frameworks like SAFe or Scrum; instead, they customize practices to fit their specific culture and needs.
4. The Agile Manifesto’s core principles align with established industrial engineering concepts like Deming’s 14 points and lean manufacturing—it’s fundamentally about systems thinking applied to software development.
5. When hiring consultants for Agile adoption, organizations should demand practitioners with real implementation experience rather than those who have merely read books and will leave behind expensive “shelfware.”

Check out the Audio-only version of this episode!
Episode 14 – Audio Only