Back to glossary

Scaled Agile Framework (SAFe)

Written by Joel Schneider · Last updated November 18, 2026

What is the Scaled Agile Framework (SAFe)?

The Scaled Agile Framework (SAFe) is a knowledge base of organizational and workflow patterns that helps large enterprises apply Lean, Agile, and DevOps practices across hundreds or thousands of practitioners. Created by Dean Leffingwell in 2011, SAFe coordinates work through Agile Release Trains, value streams, and four configuration levels that match an organization's scale.

TL;DR
  • Scope and origin: SAFe was created by Dean Leffingwell in 2011 and is maintained by Scaled Agile, Inc., the same body that certifies practitioners and publishes the reference guide.
  • Adoption signal: Scaled Agile reports that more than 20,000 organizations use SAFe and that more than two million people have been trained in it (Scaled Agile). Scaled Agile reports that 70% of Fortune 100 companies have certified SAFe professionals on site (Scaled Agile, 2024).
  • Four configurations, not one: Essential, Large Solution, Portfolio, and Full SAFe scale the framework from a single Agile Release Train up to multi-portfolio enterprises.
  • Not universally loved: Critics inside the Lean and Kanban communities argue SAFe reintroduces hierarchy and ceremony that pure Scrum, the Spotify model, or LeSS deliberately avoid.

Definition: The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns intended to guide enterprises in scaling lean and agile practices. SAFe integrates principles and techniques from Agile, Lean, and systems thinking to provide a structured framework for deploying agile practices at an enterprise scale.

Core competencies SAFe organizes around

SAFe 6.0 named seven core competencies on its Big Picture (Scaled Agile, SAFe 6.0 Big Picture), drawn from Agile methodologies, systems thinking, and Lean product development. Each names a capability that has to function for the framework as a whole to deliver value.

  1. Lean-Agile Leadership: Leaders drive and sustain organizational change by coaching and aligning teams around outcomes rather than outputs.
  2. Team and Technical Agility: High-performing agile teams own the engineering practices, testing, and craftsmanship needed to deliver value continuously.
  3. Agile Product Delivery: Customer-centric design, develop-on-cadence release-on-demand pipelines, and feedback-driven improvement.
  4. Lean Portfolio Management: Funding value streams instead of projects, governing through strategic themes, and managing the portfolio Kanban.
  5. Continuous Learning Culture: Relentless improvement, learning organization habits, and innovation rituals that compound over time.
  6. Enterprise Solution Delivery: Applying Lean-Agile practices to building and evolving very large systems, including cyber-physical ones.
  7. Organizational Agility: Extending Lean-Agile ways of working beyond technology into business functions and strategy.

Scaled Agile's current framework site regroups this guidance into five disciplines: Lean Portfolio Management, Team and Technical Agility, Product Development Flow, Large Solution Integration and Delivery, and Leadership and Culture (Scaled Agile).

How SAFe rollouts actually sequence

A SAFe rollout follows the 13-step Implementation Roadmap published by Scaled Agile (Scaled Agile), condensed here into the six decisions that determine whether the program survives its first year.

  1. Reach the tipping point. Name the burning platform or proactive opportunity that justifies the change. Without it, the rollout stalls at the first leadership turnover.
  2. Train Lean-Agile change agents. Certify SAFe Practice Consultants (SPCs) who will coach Agile Release Trains and run PI Planning.
  3. Create a Lean-Agile Center of Excellence. Establish the small central team that owns standards, training, and continuous improvement across trains.
  4. Identify value streams and ARTs. Map how value flows to the customer, then organize 50-125 practitioners into each Agile Release Train around that flow.
  5. Extend to the portfolio. Introduce Lean Portfolio Management, strategic themes, and the portfolio Kanban so funding follows value streams rather than projects.
  6. Sustain and improve. Run Inspect and Adapt workshops after each Planning Interval (PI; earlier SAFe versions called it a Program Increment, see Scaled Agile) and treat the framework itself as the object of continuous improvement.

The four SAFe configurations compared

SAFe offers four configurations so the framework matches the actual scale of an enterprise. The differences are not cosmetic: each configuration adds specific roles, ceremonies, and artifacts.

Configuration

Scope

Trains

Adds these elements

Best fit

Essential SAFe

One Agile Release Train

1 ART (50-125 people)

PI Planning, System Demo, Inspect and Adapt

Single program or product line

Large Solution SAFe

Multiple ARTs delivering one solution

2-10+ ARTs

Solution Train, Solution Architect, Solution Demo

Aerospace, defense, complex hardware

Portfolio SAFe

One portfolio of value streams

Multiple ARTs across the portfolio

Lean Portfolio Management, strategic themes, portfolio Kanban

Mid-to-large enterprises

Full SAFe

Multi-portfolio enterprise

All of the above

Every role, artifact, and competency in the framework

Global enterprises with multiple portfolios

What problems SAFe is built to solve

Most enterprises that adopt SAFe do so because team-level agile practices stopped scaling. The framework is designed to fix four specific failure modes that appear once an organization moves past ten teams.

  • Misalignment between teams: PI Planning synchronizes 50-125 people around shared PI objectives, so teams stop building features that conflict at integration.
  • Slow release cadence: The develop-on-cadence release-on-demand pattern decouples integration from release, so working software exists every two weeks even if the business chooses not to ship it.
  • Funding tied to projects, not value: Lean Portfolio Management funds long-lived value streams instead of one-off projects, removing the annual budgeting cycle from the critical path.
  • No connection between strategy and work: Strategic themes cascade enterprise strategic business goals down through the portfolio Kanban into ART backlogs.
Agile is the most disciplined and quality-driven set of development practices the industry has invented to date.
― Dean Leffingwell, creator of SAFe and co-founder of Scaled Agile, Inc.

That defense of Agile discipline sits at the heart of why SAFe exists: SAFe's bet is that disciplined Agile, applied with explicit roles and cadences, scales better than the alternative of letting each team invent its own process.

Four ways SAFe rollouts stall: PI Planning, ceremony, the LACE and budget

The framework covers a wide surface area of roles, artifacts, and ceremonies, which is also its main implementation risk. Four patterns appear repeatedly in failed rollouts.

  • PI Planning becomes a status meeting. Two days of synchronized planning only works if teams arrive with prepared features and clear acceptance criteria. Without that prep, the event becomes a 100-person scheduling exercise.
  • Ceremony without behavior change. Organizations adopt the roles and meetings but keep waterfall handoffs, milestone-based funding, and command-and-control management. The output looks like SAFe; the operating model is unchanged.
  • The Lean-Agile Center of Excellence becomes a bottleneck. A 4-person LACE team cannot review every ART's decisions. When it tries to, the trains stop deciding and start escalating.
  • Initial investment underestimated. Certifying SPCs, retraining hundreds of practitioners, and running the first 2-3 PIs at reduced throughput is a real cost. Rollouts that skip the budget commitment usually stall by month nine.

When SAFe is the wrong choice

Scaled Agile, which sells SAFe training and certification, calls Core SAFe "the world's most adopted Operating Model" (Scaled Agile), but SAFe is not the right answer for every context. SAFe is used by roughly 35% of organizations practicing scaled agile (State of Agile Report, 2024). The framework is a poor fit for at least three situations.

  • Small organizations. Under 50 engineers, the overhead of Agile Release Trains, PI Planning, and the SAFe role library exceeds the coordination benefit. Plain Scrum or Kanban is faster.
  • High-autonomy product organizations. Companies that compete on engineering velocity (consumer SaaS, AI labs, fintech challengers) usually find that the Spotify model or pure team-of-teams structures preserve more autonomy than SAFe's prescribed roles allow.
  • Frequent strategy pivots. SAFe assumes a portfolio Kanban with strategic themes that hold for several PIs. Organizations that re-plan every quarter on the back of new market data should anchor on quarterly OKRs with lighter-weight coordination, not on annual portfolio Kanbans.

This is the contrarian read SAFe critics have raised since the framework launched: at scale, the prescribed ceremonies can reintroduce the hierarchy and handoffs that team-level Agile was supposed to remove.

The framework is strongest in regulated, multi-team, multi-year delivery contexts. It is weakest where speed of strategic pivot is the competitive advantage.

Using SAFe inside an OKR cycle

Many enterprises run SAFe and OKRs in parallel. The cleanest pattern is to treat SAFe as the execution layer and OKRs as the strategic-intent layer above it.

  • Annual strategic themes become 3-5 enterprise-level OKRs.
  • Portfolio Kanban epics become Key Results on those OKRs, with explicit value-stream owners.
  • PI objectives at the ART level inherit from portfolio OKRs, giving each train a measurable contribution to enterprise outcomes.

This pairing keeps SAFe's coordination strength while addressing the most common critique: that strategic themes alone do not give teams a falsifiable definition of success.

Who created SAFe and when?
SAFe was created by Dean Leffingwell and first published in 2011 through the company that became Scaled Agile, Inc. Leffingwell remains the chief methodologist. Scaled Agile still maintains it: its framework site now presents Core SAFe, organized into five disciplines, and an AI-Native SAFe operating model that builds on it, and still offers the SAFe 6.0 Big Picture configurations.
How is SAFe different from Scrum?
Scrum is a single-team framework with three roles and four events; SAFe is an enterprise framework that coordinates many Scrum teams through Agile Release Trains, PI Planning, and a portfolio layer. Teams inside SAFe usually still run Scrum at the team level.
What are the four SAFe configurations?
The four configurations are Essential SAFe (one Agile Release Train), Large Solution SAFe (multiple ARTs delivering one solution), Portfolio SAFe (one portfolio of value streams), and Full SAFe (multi-portfolio enterprise with every element of the framework).
What is an Agile Release Train?
An Agile Release Train (ART) is a long-lived team of 50-125 practitioners organized around a value stream. It plans together every 8-12 weeks at PI Planning, releases on a shared cadence, and is the basic unit of execution in every SAFe configuration.
Is SAFe still relevant in 2026?
SAFe is still widely used: Scaled Agile reports that more than 20,000 organizations use it and more than two million people have been trained in it. SAFe remains the most-adopted scaling framework, with 70% of Fortune 100 companies running certified SAFe professionals on site (Scaled Agile, 2024). Adoption inside high-autonomy tech companies has declined, but in regulated, multi-team enterprises SAFe is still the default scaling choice. Its strongest fit is regulated, multi-team, multi-year delivery; high-autonomy product organizations often prefer lighter structures that preserve team autonomy.
How long does a SAFe implementation take?
A meaningful SAFe rollout typically takes 9-18 months to reach a self-sustaining state: 3 months to train SPCs and stand up the Lean-Agile Center of Excellence, 3-6 months to launch the first Agile Release Train, and another 6-9 months to extend to portfolio level. Sustaining improvement continues indefinitely.
Related articles
Try Mooncamp for free