By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that the Agile movement had two parts: frequent small releases, and empowering teams to solve problems rather than execute roadmaps. The first change spread easily, but the second threatened stakeholders and pushed back-office project management (the PMO) aside. As PMO-style thinking returned under the banner of "Agile at Scale," Cagan critiques SAFe as a top-down, output-focused model that rebrands Agile terms while preserving command and control. He contends it undermines true product teams and continuous innovation, while acknowledging a few narrow scenarios where it might fit. The piece matters because it frames the real difference as project-mindset versus product-mindset, a distinction large companies pursuing digital transformation often miss.
01Key takeaways
- Frequent small releases are only half of Agile; the bigger gain is empowering teams to solve problems and own outcomes.
- Be wary of frameworks that relabel Agile terms while reinstating roadmap-driven, top-down command and control.
- Judge a process by whether it keeps dedicated product teams with real decision-making authority over what to build.
- Digital transformation is really about moving from a project mindset to a product mindset, not adopting a methodology.
- Measure teams by outcomes delivered, not by the volume of output or features shipped.
02Key sections
- Two Halves of Agile
- Cagan separates Agile's frequent-release practice from its more important shift: letting teams own problems and outcomes rather than just implementing feature lists. The second change is what generated political resistance.
- The PMO Returns
- Program management offices were sidelined when companies went Agile, but they have regrouped and found a new home in scaled Agile frameworks that reassert top-down project control.
- Critique of SAFe
- Cagan argues SAFe repackages Agile vocabulary to hide its purpose, demotes the dedicated product team, prioritizes output over outcome, and blocks continuous innovation.
- Where It Might Fit
- He concedes a few contexts, such as heavy outsourcing, large re-platforming efforts, or weak product talent, where such a process may be tolerable.
- Project vs. Product Mindset
- The real issue, he says, is the mindset gap, and large companies pursuing digital transformation need to make that shift rather than adopt a marketed process.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.