SAFe (Scaled Agile Framework)
The Scaled Agile Framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices across multiple teams, programs, and portfolios.
Explanation
SAFe addresses the challenge of applying agile at scale by providing structured guidance for coordination across multiple agile teams. It organizes work at four levels: Team (individual Scrum/Kanban teams), Program (Agile Release Trains of 50-125 people), Large Solution (multiple ARTs), and Portfolio (strategic alignment and funding).
At the program level, SAFe introduces the Agile Release Train (ART), which is a long-lived team of agile teams that plans, commits, and executes together in Program Increments (PIs). PI Planning is a major event where all ART teams come together to plan the next PI, typically 8-12 weeks of work. This creates alignment and manages dependencies across teams.
SAFe incorporates practices from Scrum, Kanban, XP, lean, and DevOps into a comprehensive framework. Key concepts include WSJF for prioritization, PI objectives for commitment, enablers for architecture and infrastructure, and the innovation and planning (IP) iteration for exploration and planning. PMI exams may reference SAFe as an example of scaling agile.
Key Points
- •Four levels: Team, Program, Large Solution, and Portfolio
- •Agile Release Trains coordinate multiple teams
- •PI Planning aligns teams and manages dependencies across 8-12 week increments
- •Incorporates Scrum, Kanban, XP, lean, and DevOps practices
Exam Tip
SAFe is the most commonly referenced scaling framework on PMI exams. Know the ART concept, PI Planning, and the four levels.
Frequently Asked Questions
Related Topics
Agile Release Train
An Agile Release Train (ART) is a long-lived team of agile teams in SAFe that plans, commits, and executes together in Program Increments, aligned to a common mission and value stream.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model used in SAFe that calculates priority by dividing the Cost of Delay by the job size, ensuring the highest-value, smallest items are done first.
Hybrid Approach
A Hybrid Approach combines elements of predictive (waterfall) and adaptive (agile) methods within a single project, tailoring practices to fit the project's specific needs and constraints.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.