Skip to content
PMPCAPM

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.

Share:

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

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

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 in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Part of

Agile & Hybrid

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.