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.
Know it well enough for the exam? Questions on SAFe (Scaled Agile Framework) are scenario-based, not definitional.
Practice it freeExplanation
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, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting 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.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Part of
Agile & Hybrid
Practice SAFe (Scaled Agile Framework)
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.