The SAFe Framework
Scaled Agile Framework · v6.0What is SAFe?
The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at enterprise scale — helping large organizations align strategy with execution and deliver value continuously.
SAFe was developed by Dean Leffingwell and Drew Jemilo, first released in 2011. It combines principles from Agile software development, Lean product development, and systems thinking into a comprehensive framework for scaling across teams, programs, and portfolios.
SAFe is built around the Agile Release Train (ART) — a long-lived team of Agile teams (typically 50–125 people) that incrementally develops and delivers solutions in a value stream. ARTs operate on a fixed cadence called the Program Increment (PI), usually 8–12 weeks, creating a predictable rhythm of planning, execution, and inspection.
The framework defines four configurations to accommodate different scales: Essential SAFe (the minimal starting point), Large Solution SAFe, Portfolio SAFe, and Full SAFe. Most organizations begin with Essential SAFe and expand as needed.
SAFe Principles
SAFe is grounded in ten immutable principles derived from Agile, Lean product development, and systems thinking. These principles inform every practice and decision within the framework.
#1 — Take an Economic View
Deliver early and often, apply economic prioritization with Weighted Shortest Job First (WSJF), and understand the economic trade-offs of scope, schedule, and quality.
#2 — Apply Systems Thinking
Understand that the solution is a system, the enterprise building it is a system, and optimizing a component doesn’t optimize the whole. Think about interactions, not just parts.
#3 — Assume Variability; Preserve Options
Maintain multiple design and implementation options early in the process. Narrow choices over time as data emerges. Avoid premature commitment.
#4 — Build Incrementally with Fast Learning Cycles
Develop solutions in small increments. Integrate frequently. Use short feedback loops to learn what works before committing to large batches.
#5 — Base Milestones on Objective Evaluation
Use frequent, objective demonstrations of working systems — not documents, reviews, or phase gates — to assess fitness for purpose.
#6 — Make Value Flow Without Interruptions
Understand, visualize, and optimize the flow of value. Limit work in progress. Reduce batch sizes. Manage queue lengths. Eliminate delays and handoffs.
#7 — Apply Cadence; Synchronize with Cross-Domain Planning
Use cadence to make events predictable and reduce uncertainty. Synchronize across teams and domains during PI Planning to align on shared objectives.
#8 — Unlock Intrinsic Motivation
Provide autonomy, mastery, and purpose. Remove impediments. Trust people to make decisions. Leadership’s role is to create the environment, not control the work.
#9 — Decentralize Decision-Making
Centralize only strategic, infrequent, and high-impact decisions. Push all other decisions to the teams closest to the work for speed and engagement.
#10 — Organize Around Value
Structure the organization around the flow of value, not around functional departments. Identify value streams, build ARTs around them, and fund them as persistent entities.
Core Values
SAFe is built on four core values that guide behavior at every level: Alignment, Transparency, Built-in Quality, and Program Execution.
Team Level
The Team Level is where value is created. Agile Teams of roughly 5–11 cross-functional members use Scrum, Kanban, or a hybrid to deliver working increments every iteration (typically 2 weeks).
Agile Teams
Each team is cross-functional and self-managing, containing all the skills needed to define, build, test, and deliver an increment. Teams include Developers, testers, designers, and other specialists as needed.
Product Owner
The PO is the single voice of the customer for the team. They own the Team Backlog, define and prioritize user stories, accept work, and serve as the bridge between the team and Product Management at the ART level.
Scrum Master / Team Coach
A servant leader who facilitates team events, removes impediments, coaches the team in Agile practices, and fosters continuous improvement. In SAFe 6.0, this role can be called either Scrum Master or Team Coach.
Team Events
Iteration Planning, Daily Stand-up, Iteration Review, Iteration Retrospective, and Backlog Refinement. These mirror Scrum events but operate within the larger ART cadence and contribute to ART-level integration.
ART Level
The Agile Release Train (ART) is the primary value delivery construct in SAFe. It brings together 5–12 Agile Teams (50–125 people) around a shared value stream, operating on a fixed PI cadence.
Release Train Engineer (RTE)
The servant leader and chief coach of the ART. Facilitates PI Planning, ART Sync, Inspect & Adapt, and System Demos. Manages cross-team dependencies, removes systemic impediments, and optimizes flow across the train.
Product Management
Owns the ART Backlog and has content authority over features. Defines the product vision and roadmap, prioritizes features using WSJF, and works with Product Owners to decompose features into stories.
System Architect
Defines the overall architecture of the solution. Identifies non-functional requirements, designs subsystem interfaces, and ensures architectural runway supports current and near-term feature delivery.
Business Owners
Key stakeholders with business and technical responsibility for fitness-for-use, governance, and ROI. They actively participate in PI Planning, evaluate PI objectives, and provide feedback at System Demos.
ART Events
PI Planning (the signature event), System Demo (every iteration), ART Sync / Coach Sync / PO Sync (weekly coordination), and Inspect & Adapt (at the end of each PI).
Portfolio Level
The Portfolio Level aligns strategy with execution, organizes around value streams, and applies Lean governance through Lean Portfolio Management (LPM). It connects enterprise strategy to ART-level delivery.
Lean Portfolio Management
LPM applies Lean and systems thinking to strategy, investment funding, and governance. It replaces traditional project-based funding with persistent value stream funding, uses portfolio Kanban to manage the flow of epics, and applies guardrails rather than detailed oversight.
Value Streams
The primary organizing construct. Each value stream delivers end-to-end value to a customer or internal user. Development value streams build solutions; operational value streams deliver them. ARTs are organized around value streams.
Strategic Themes & OKRs
Strategic themes connect portfolio decisions to enterprise strategy. Objectives and Key Results (OKRs) create measurable outcomes at portfolio, ART, and team levels, ensuring alignment from strategy through execution.
Epic Owners & Enterprise Architect
Epic Owners shepherd individual epics through the portfolio Kanban system. The Enterprise Architect guides technical strategy across value streams, ensuring architectural coherence and managing cross-cutting concerns.
The Program Increment
The Program Increment (PI) is the fundamental planning and execution cadence for the ART — typically 8–12 weeks comprising 4 development iterations plus 1 Innovation & Planning (IP) iteration.
The PI provides a fixed cadence for planning, executing, inspecting, and adapting at scale. It begins with PI Planning (a 2-day event aligning all teams), proceeds through iterative development with ongoing synchronization, and concludes with Inspect & Adapt.
PI Planning
The signature event of SAFe. All ART members (50–125+ people) gather for a 2-day working session to align on a shared vision, identify dependencies, commit to PI Objectives, and build the ART Planning Board. It produces alignment that cannot be achieved through documents or status meetings.
PI Execution
Teams execute in iterations, integrating and demoing continuously. ART Sync, Coach Sync, and PO Sync events keep teams coordinated. The RTE monitors flow, manages risks via ROAM boards, and facilitates impediment resolution.
Innovation & Planning (IP) Iteration
A dedicated iteration for innovation, continuing education, PI Planning preparation, infrastructure work, and hackathons. It provides a buffer for meeting PI objectives and prevents over-commitment.
Inspect & Adapt
A three-part event at the end of each PI: a System Demo of the integrated solution, quantitative and qualitative review of PI performance, and a problem-solving workshop that produces improvement items for the next PI.
Flow & Quality
SAFe 6.0 places heavy emphasis on accelerating the flow of value and building quality in at every level. Eight flow properties and eight flow accelerators define how SAFe teams measure and improve delivery.
Flow Properties
Speed, predictability, quality, efficiency, value, visibility, sustainability, and partner health. These eight properties describe what healthy flow looks like and provide a measurement framework for continuous improvement.
Flow Accelerators
Limit WIP, reduce batch size, manage queue lengths, visualize work, reduce handoffs, eliminate waste, get faster feedback, and work in smaller increments. These operational practices directly improve the flow properties.
Built-in Quality
Starts with basic Agile quality practices: shift learning left, pairing and peer review, collective ownership, T-shaped skills, artifact standards and definition of done, and workflow automation. These create the foundation for continuous delivery.
Continuous Delivery Pipeline
Describes the workflows, activities, and automation needed to release value continuously: Continuous Exploration (what to build), Continuous Integration (build and test), and Continuous Deployment (release on demand).