SAFe Configurations Overview

Essential SAFe is the simplest configuration and the recommended starting point. It includes only the Team and Program (ART) levels.

What it includes:

• Agile Teams (5-11 people) using Scrum, Kanban, or ScrumBan
• Agile Release Train (ART): 50-125 people organized around a value stream
• PI Planning: Quarterly face-to-face planning event
• System Demo: Every iteration, show integrated work across all teams
• Inspect & Adapt: End-of-PI retrospective with quantitative and qualitative analysis

When to use Essential SAFe:

• You have 2-12 teams working on a shared product or value stream
• You need cross-team coordination but don't have multiple value streams
• You're new to SAFe and want to build competency before expanding

Why start here: Essential SAFe solves the most common scaling pain point—coordinating multiple agile teams building one product. It introduces the minimum viable framework: shared cadences (PI), shared planning (PI Planning), and shared integration (System Demo). Most organizations get significant value from just this level.

Large Solution SAFe adds a layer above Essential SAFe for products that require multiple ARTs working together.

When to use Large Solution:

• You have multiple ARTs (200+ people) building one product/solution
• There are significant inter-ART dependencies
• The system requires coordination with external suppliers
• Examples: autonomous vehicles, aircraft systems, large platforms

Key additions: Solution Train, Solution Management, Solution Architect, Pre/Post PI Planning, Solution Demo.

Portfolio SAFe adds strategic alignment and Lean governance above the program level.

When to use Portfolio:

• You have multiple value streams that need strategic coordination
• Investment decisions need to be decentralized to portfolio level
• You want to connect strategy to execution through Lean budgeting
• Organizations with 500+ people in development

Key additions: Lean Portfolio Management, Strategic Themes, Portfolio Kanban, Epic Owners, Value Stream Coordination.

Full SAFe combines all three layers: Team + Program + Large Solution + Portfolio. It's the most comprehensive configuration and applies to the largest enterprises.

When to use Full SAFe:

• You have multiple large solutions, each requiring multiple ARTs
• The enterprise needs portfolio-level governance across all solutions
• You're a Fortune 500-scale organization with thousands of developers
• Very few organizations actually need this level of complexity

Choosing the right configuration:

Start with a simple decision tree:

• 2-12 teams, one product? → Essential SAFe
• Multiple ARTs, one product? → Large Solution
• Multiple value streams, need strategic alignment? → Portfolio
• All of the above, enterprise scale? → Full SAFe

The most important principle: start small and grow. Don't adopt Full SAFe because you're a large organization. Adopt Essential SAFe, prove it works, and add layers only when you encounter specific problems that require them.

Many large organizations operate happily with multiple instances of Essential SAFe without ever needing the Portfolio or Large Solution layers. The framework is modular—use what you need.