Scaled Agile, Inc. is the company founded by dean-leffingwell that created and commercializes the Scaled Agile Framework (SAFe). SAFe 1.0 was released in 2011 with the safe-launch-2011, and the framework has since become the most widely adopted enterprise Agile scaling approach — and the most controversial. SAFe 6.0 was released in March 2023.
The Scaled Agile Framework (SAFe)
SAFe is a prescriptive framework for applying Agile, Lean, and DevOps practices at enterprise scale. Where scrum is minimal and extreme-programming is technically rigorous, SAFe is comprehensive and hierarchical: it defines roles, events, artifacts, and structures at the team level, the program level (the "Agile Release Train"), and the portfolio level.
The framework's comprehensiveness is simultaneously its main appeal and the source of its most fundamental criticism. For large organizations that want a complete playbook for scaling Agile — something they can implement organization-wide with a defined structure and certification path — SAFe provides exactly that. For critics, the same comprehensiveness looks like the reintroduction of waterfall planning under Agile terminology.
The Certification Economy
Scaled Agile, Inc. generates revenue through the SAFe certification program (Leading SAFe, SAFe for Teams, SAFe Scrum Master, SAFe Product Owner/Manager, and others) and through its extensive training partner network. The SAFe Agilist (SA) certification is the entry point for organizational leaders adopting the framework. This certification structure made SAFe part of the agile-industrial-complex that emerged during the enterprise-scaling-era.
The Controversy
SAFe is the most polarizing artifact of the enterprise-scaling-era. Its critics — including many of the original agile-manifesto signatories and framework creators — argue that:
1. SAFe reintroduces quarterly planning cycles (Program Increment Planning) that function as a scaled version of waterfall releases, violating the responding-to-change principle. 2. Its hierarchical structure with multiple levels of management roles contradicts the spirit of self-organizing-teams and individuals-and-interactions. 3. It prioritizes organizational comfort (familiarity with predictive planning) over genuine Agile transformation. 4. It serves as cover for organizations to claim Agile adoption without changing the underlying management behaviors that Agile was designed to address.
The "waterfall in Agile clothing" characterization became a shorthand for this critique during the post-agile-era. Critics like ron-jeffries and others associated the enterprise scaling era with dark-agile — the corruption of Agile principles through organizational convenience.
Defenders and Adoption
SAFe's defenders argue that the choice is not between SAFe and "pure" Agile but between SAFe and nothing — that large organizations need structure, that the framework provides a workable path for enterprises that could not otherwise adopt Agile practices, and that Program Increment Planning, whatever its resemblance to quarterly release planning, at least creates cross-team coordination and visibility.
SAFe's adoption figures are substantial. Multiple surveys of the Agile ecosystem have shown SAFe as the dominant scaling framework by enterprise adoption, with less-large-scale-scrum and Nexus (from ken-schwaber and scrum-org) occupying smaller shares of the scaling framework market.
Versions
SAFe has gone through major revisions — SAFe 4.0 added a Lean-Agile Mindset layer; SAFe 5.0 (2020) incorporated business agility and organizational agility concepts; SAFe 6.0 (March 2023) updated the framework further. Each major version has attempted to address criticisms while maintaining the framework's comprehensive, prescriptive character.