SAFe
Also known as: Scaled Agile Framework
Leffingwell's enterprise-scale agile coordination framework.
The Scaled Agile Framework was developed by Dean Leffingwell beginning in 2011 as a comprehensive framework for applying agile and lean practices at enterprise scale, with substantial elaboration through subsequent versions (SAFe 4.0 in 2016, 5.0 in 2020, 6.0 in 2023). SAFe organizes work across four configurations of increasing scope: Essential SAFe (single Agile Release Train, typically 50-125 people), Large Solution SAFe (multiple ARTs coordinated through Solution Trains), Portfolio SAFe (adds Lean Portfolio Management), and Full SAFe (complete framework). The Agile Release Train (ART) is SAFe's central scaling unit — multiple agile teams coordinated through Program Increment (PI) Planning events held quarterly, with synchronized iterations and aligned objectives. SAFe also defines Lean Portfolio Management, Value Stream Management, and DevOps practices integrated into the framework. SAFe is the most widely adopted scaled agile framework in large enterprises and government, particularly in regulated industries, but is also the most controversial — critics including agile-manifesto signatories argue it commoditizes and bureaucratizes agile in ways that contradict the manifesto's spirit, while proponents argue it provides realistic structure for enterprise contexts that simpler frameworks ignore.
Core components
- Four configurations: Essential, Large Solution, Portfolio, Full SAFe
- Agile Release Train (ART) as central scaling unit (50-125 people)
- Program Increment (PI) Planning (quarterly synchronization event)
- Multiple roles: Release Train Engineer, Product Management, System Architect, Business Owners, Solution Train Engineer
- Lean Portfolio Management with epics and Lean Budgets
- Value Stream Management
- Built-in Quality practices
- Connection to DevOps and Continuous Delivery Pipeline
- Substantial role and event taxonomy
Primary use case
Enterprise-scale agile coordination, particularly in large organizations (10,000+ engineers); regulated industries (finance, healthcare, defense, government); organizations transitioning from waterfall to agile at scale; foundation for substantial commercial certification ecosystem; widely-adopted in Fortune 500 transformation programs.
Common criticisms
- Most commercially successful scaled agile framework, but also most criticized — described by some agile practitioners (Ken Schwaber, Ron Jeffries, others) as 'fake agile' that adds command-and-control structure beneath agile vocabulary
- substantial role and event taxonomy can produce ceremony-heavy implementations
- PI Planning's quarterly cadence is too long for some contexts
- commercial certification structure incentivizes adoption regardless of fit
- documentation-heavy artifacts (program kanbans, dependency maps, etc.) can substitute for genuine cross-team work
- risks recreating waterfall-style centralized planning at scale while claiming agile branding
- 'SAFe-shaped' implementations where ART boundaries don't match actual product or team boundaries
- competitive tension with simpler scaling frameworks (LeSS, Nexus).
Lineage
- Child of
- Scrum
- Siblings
- Scrum, LeSS, Spotify Model
- Derived from
- Scrum