SAFe (Scaled Agile Framework) is an enterprise-scale methodology that extends Lean and Agile principles across large organizations, enabling multiple teams to deliver value through coordinated Agile Release Trains (ARTs) and program increments. SAFe addresses the challenge of scaling agility — moving from a handful of Scrum teams to hundreds or thousands of people working on complex, mission-critical solutions. The framework's power lies in its structured cadence (typically 8–12 week program increments), economic prioritization (using WSJF), and built-in quality practices that prevent technical debt from accumulating. Understanding SAFe means recognizing that success at scale requires more than team-level practices: it demands alignment, transparency, and synchronization across portfolios, solutions, and programs.
What This Cheat Sheet Covers
This topic spans 17 focused tables and 125 indexed concepts, 115 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: SAFe Core Values and Principles
The four core values — alignment, transparency, respect for people, and relentless improvement — guide behavior across every SAFe portfolio. They create a cultural foundation that enables distributed teams to make decisions independently while staying coordinated. These values are operationalized through ten Lean-Agile principles that inform everything from economic trade-offs to architectural decisions.
| Value/Principle | Example | Description | |
|---|---|---|---|
PI Planning aligns 50-125 people to a shared mission every 8-12 weeks | • Synchronizes strategy and execution across all levels • every team understands how their work contributes to business outcomes | ||
Program Board displays all dependencies and risks visibly during PI Planning | • Makes work visible to everyone • backlogs, progress, and impediments are openly shared — no hidden agendas | ||
Teams self-organize sprint plans; RTEs facilitate rather than command | • Empowers teams to make technical decisions • leaders coach and enable rather than micromanage | ||
Inspect and Adapt workshop identifies process bottlenecks every PI | • Constantly reflects and optimizes • uses problem-solving workshops to address systemic issues | ||
WSJF = (Business Value + Time Criticality + Risk/Opportunity) ÷ Job Size | • Quantifies trade-offs using Cost of Delay • prioritizes work that delivers economic value fastest | ||
Optimizing one team's velocity while ignoring integration harms the ART | • Views the organization as an interconnected system • local optimizations that harm the whole are avoided | ||
Solution Intent keeps requirements variable early, fixed late | • Delays irreversible decisions • maintains multiple design alternatives until facts reduce uncertainty | ||
System Demo every 2 weeks; full Solution Demo every PI | • Delivers working increments frequently • validates assumptions early rather than waiting until the end | ||
Epics pass Lean Business Case review at Portfolio Kanban gates | Funds initiatives based on objective evidence and demos, not subjective opinions or phase-gate completion | ||
Flow metrics track time from idea to production deployment | • Identifies and eliminates delays in value delivery • focuses on flow efficiency over resource utilization | ||
PI boundaries synchronize multiple ARTs; all teams plan together | • Uses fixed rhythms (iterations, PIs) to reduce coordination overhead • synchronization events align dependencies | ||
Teams commit to PI Objectives they define; management assigns value | • Leverages autonomy, mastery, and purpose • people work harder when they control how they meet goals | ||
Teams choose their iteration plans; architects set guardrails, not designs | • Pushes decisions to those closest to the information • leadership retains authority only for strategic, infrequent, or long-lasting choices | ||
ARTs are funded as long-lived teams, not temporary projects | • Forms persistent value streams instead of project-based structures • funding flows to outcomes, not task completion |