SAFe (Scaled Agile Framework)
The Scaled Agile Framework (SAFe), created by Dean Leffingwell in 2011, is the most-adopted methodology for applying agile practices at enterprise scale (typically 100+ engineers). SAFe organises work in three levels — Team, Program (typically 5-12 teams forming an Agile Release Train), and Portfolio — with synchronised Program Increment (PI) cadences of 8-12 weeks across all teams.
SAFe is the most divisive framework in scaled agile. Critics (including most of the original Agile Manifesto signatories) argue it's a heavyweight process layer that violates agile's people-over-process principle. Defenders argue that genuinely large organisations need explicit coordination mechanisms and SAFe provides them. The honest assessment: SAFe works in regulated industries and very large organisations where PI Planning's predictability is more valuable than its overhead; it fails in product-led organisations where the ceremony slows down learning. Modern alternatives at scale: LeSS (Large-Scale Scrum) is leaner; Spotify model is loosely-coupled; Team Topologies provides structural patterns without dictating ceremony.