Agile Frameworks - SAFe
About The Author & The Article
Jonathan Bishop, Group Chairman, Bishop Phillips Consulting. [1]
Copyright 2020-2026 - Moral Rights Retained.
This article may be copied and reprinted in whole or in part, provided that the original author and Bishop Phillips Consulting is credited and this copyright notice is included and visible, and that a reference to this web site (http://RiskWiki.bishopphillips.com/) is included.
This article is provided to the community as a service by Bishop Phillips Consulting www.bishopphillips.com.
Introduction
SAFe (Scaled Agile Framework) is a way to align strategy, funding, architecture, and multiple Agile teams using a predictable cadence and multi‑team coordination mechanisms so the entire enterprise delivers value continuously and coherently.
It’s Agile for organisations with:
- multiple teams
- shared platforms
- shared architecture
- regulatory constraints
- long‑term funding
- enterprise‑level governance
Scrum is for teams, while SAFe is for systems.
The Four Levels of SAFe (the real structure)
SAFe has four layers which are effectively 'zoom levels' in a value‑delivery system.
1. Team Level (Scrum/Kanban Teams)
This is the level we know from Scrum.
Each team uses:
- Scrum or Kanban
- PBIs
- Sprint Goals
- Definition of Done (DoD)
- Retrospectives
Nothing changes from Scrum at this level. SAFe doesn’t replace Scrum: it connects Scrum teams.
2. Program Level (Agile Release Train — ART)
This level is the 'heart' of SAFe.
An **ART** is:
- 5–12 Agile teams
- working on one product or value stream
- synchronised on the same cadence
- delivering together every 8–12 weeks
An ART as a Scrum of Scrums with structure.
Key concepts:
- PI (Program Increment) = 5 Sprints
- PI Planning = all teams plan together
- System Demo = integrated demo across teams
- RTE (Release Train Engineer) = the Scrum Master for the whole train
- Product Management = the Scrum Product Owner at scale
- System Architect = architecture at scale
This solves the “multiple teams, one product” problem.
3. Large Solution Level (for big systems)
Used when multiple ARTs must coordinate to build a single large system.
Examples:
- Defence systems
- Banking platforms
- National infrastructure
- Enterprise‑wide platforms
Roles:
- Solution Train Engineer
- Solution Architect
- Solution Management
If you don’t have massive systems, you can ignore this layer.
4. Portfolio Level (Strategy + Funding)
This is where SAFe becomes Enterprise Agile.
Portfolio level handles:
- Lean budgeting
- Value streams
- Epic approval
- Investment horizons
- Enterprise architecture
- Governance
Key artifacts:
- Portfolio Kanban
- Strategic Themes
- Epic Owners
- Guardrails
This is where SAFe connects strategy to execution.
The Core SAFe Idea: Value Streams
SAFe organises the enterprise around value streams, not departments.
A value stream is: The sequence of activities that delivers value to a customer.
Each value stream has:
- funding
- teams
- architecture
- governance
- metrics
This is the opposite of traditional org charts.
---
=The SAFe Cadence=SAFe runs on a predictable rhythm:
- Daily: Team standups
- Every 2 weeks: Sprints
- Every 10 weeks: PI (Program Increment)
- Every PI:
- PI Planning
- System Demo
- Inspect & Adapt
This creates alignment across the entire enterprise.
The SAFe Roles (simplified)
SAFe has three major layers of roles:
- Team Level — where work is done
- Program Level (ART) — where multiple teams align
- Portfolio Level — where strategy and funding live
There is also a Large Solution Level for massive systems.
These three levels have the following roles:
1. Team Level
This is the Scrum level which are explained in detail in Agile Frameworks - Scrum:
- Product Owner
- Scrum Master
- Developers
2. Program Level
This is where SAFe becomes SAFe. The ART is 5–12 teams working together on one product/value stream:
- Product Manager
- Release Train Engineer (RTE)
- System Architect
Plus two external roles:
- Business Owners
- System Team
| Role | Description |
|---|---|
| Product Manager | Owns the Program Backlog.
Focus: What should the ART build next?
PO = team-level value. PM = program-level value. |
| Release Train Engineer (RTE) | The Scrum Master for the entire ART.
Focus: How do all teams work together?
This is one of the most critical roles in SAFe. |
| System Architect / Solution Architect | Owns the architecture runway.
Focus: What technical direction ensures long-term viability?
|
| Business Owners | The key stakeholders for the ART.
Focus: Is the ART delivering business value?
|
| System Team | A specialised team that supports integration and testing.
Focus: Enable continuous integration and system demos. |
3. Portfolio Level
This is where SAFe becomes Enterprise Agile:
- Epic Owners
- Enterprise Architect
- Lean Portfolio Manager
| Role | Description |
|---|---|
| Epic Owners | Own portfolio epics (big initiatives).
Focus: Drive large-scale change.
Coordinate across ARTs |
| Enterprise Architect | Owns enterprise-wide architecture.
Focus: Ensure technical coherence across value streams.
|
| Lean Portfolio Manager | A group, not a person.
Focus: Where should we invest?
|
These roles ensure alignment from strategy → execution.
Why SAFe Exists
SAFe solves problems that Scrum alone cannot:
- Multiple teams working on one product
- Shared architecture
- Shared platforms
- Regulatory compliance
- Long‑term funding
- Enterprise governance
- Cross‑team dependencies
- Coordinated releases
Scrum is too small for enterprise wide application so SAFe provides a scaffolding around Scrum but in the process it looses some of its agility. SAFe’s Secret: It’s Not Really About Agile. SAFe is actually about:
- alignment
- flow
- governance
- architecture
- funding
- strategy execution
Agile is the delivery mechanism while SAFe is the operating model at enterprise scale.
SAFe + Agentic AI (our future direction)
This is where things get exciting.
SAFe provides:
- structure
- cadence
- governance
- alignment
Agentic AI provides:
- automation
- analysis
- orchestration
- continuous sensing
- autonomous execution
Together, they create: Enterprise Agile 2.0: A hybrid human–AI operating model.
Agents can plug into:
- Portfolio Kanban (epic analysis)
- PI Planning (capacity simulation)
- Backlog refinement (PBI generation)
- Architecture runway (design evaluation)
- Flow metrics (bottleneck detection)
- Compliance (continuous monitoring)
This is the future we are moving towards.
Next Steps: Choose Your Path
- SAFe + Agentic AI (the future model) - How agents plug into every SAFe layer.
- SAFe Roles Explained - PO vs PM vs RTE vs Epic Owner.
- SAFe Portfolio Kanban - How strategy flows into execution.
- SAFe PI Planning - How multi‑team planning actually works.
- SAFe vs Scrum vs Kanban - When to use which.
- How to implement SAFe in a real organisation - Practical, not theoretical.
