# Scaled Agile Framework

SAFe coordinates strategy, portfolio decisions, and multi-team product delivery through a structured Lean-Agile operating model.

- Type: framework
- Domain: Delivery & agility
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/scaled-agile-framework/>)

## What it means

The Scaled Agile Framework \(SAFe\) is a configurable body of principles, roles, events, and practices for applying Lean, Agile, systems thinking, and DevOps across a large enterprise. Its core delivery construct is the Agile Release Train: a long-lived team of teams aligned to a value stream and a shared mission.

## Why it matters

Local team agility does not automatically resolve portfolio queues, cross-team dependencies, funding constraints, architecture work, or regulatory coordination. SAFe gives large organizations common planning cadences and decision structures for connecting strategy to delivery while emphasizing built-in quality and flow.

## When to use it

Consider SAFe when many persistent teams build related products or large solutions, coordination costs are visible, and leaders are prepared to change budgeting, governance, and management behavior. Start with a specific value stream and problem rather than rolling out every role at once.

## How it works

1. Identify development value streams and organize the people needed to deliver value into durable Agile Release Trains.
2. Set product and solution direction, maintain prioritized backlogs, and use economic considerations to sequence work.
3. Align teams through a shared planning interval, common objectives, dependency conversations, and regular system demonstrations.
4. Build quality and continuous delivery into everyday work instead of relying on a final integration phase.
5. Inspect outcomes and flow, solve systemic impediments, and connect portfolio investment decisions to measurable strategic themes.

## A practical example

A bank modernizing mortgage servicing forms an Agile Release Train spanning customer experience, underwriting, platform, security, and operations. During interval planning, teams agree on objectives and expose a dependency on identity verification. Leaders fund the value stream, teams integrate continuously, and system demonstrations reveal workflow problems before a broad release.

## Where it breaks

SAFe can add vocabulary, meetings, specialized roles, and certification expense. A ceremonial implementation may preserve project funding, functional silos, and command-and-control decisions beneath Agile labels. Its breadth can overwhelm smaller organizations, and synchronized planning must not become a promise that discourages learning or local autonomy.

## Common mistakes

- Installing the full framework before identifying the coordination problem to solve.
- Treating planning objectives as fixed commitments despite new evidence.
- Changing team ceremonies while leaving portfolio funding and decision bottlenecks untouched.

## Sources

1. [About the Scaled Agile Framework](<https://framework.scaledagile.com/about/>) — Scaled Agile, Inc. · Official framework overview
2. [SAFe Lean-Agile Principles](<https://framework.scaledagile.com/safe-lean-agile-principles/>) — Scaled Agile, Inc. · Official framework guidance
3. [Essential SAFe](<https://framework.scaledagile.com/essential-safe/>) — Scaled Agile, Inc. · Official framework configuration

## Related topics

- [Large-Scale Scrum](<https://wiki.soroush.uk/topic/large-scale-scrum/>)
- [Nexus Framework](<https://wiki.soroush.uk/topic/nexus-framework/>)
- [Disciplined Agile](<https://wiki.soroush.uk/topic/disciplined-agile/>)
