SAFe is not Scrum with more Scrum on top
SAFe is an enterprise operating model that contains team-level methods — SAFe Scrum and SAFe Kanban — rather than being a scaled-up Scrum. Its unit of delivery is the Agile Release Train, and most of what it adds sits above the team, in cadence, funding, architecture and portfolio governance.
Why it is like this
The problems SAFe claims to solve — funding, dependency, architectural runway, portfolio prioritisation — are not team problems, so scaling a team framework would not reach them. Whether the answer is right is contested; that it is answering a different question is not.
Not to be confused with
A bigger Scrum, or a Scrum variant. SAFe's team method is adjacent to Scrum but its own thing, and several of its role names mean something different from the Scrum Guide's — which is where almost all the confusion between the two comes from.
In practice
"We do Scrum, so we basically do SAFe" and "SAFe is just Scrum with extra meetings" are the same mistake from opposite directions.
Source: SAFe Glossary (Scaled Agile, Inc.) — Agile Release Train (ART). Read on .
SAFe® and Scaled Agile Framework® are registered trade marks of Scaled Agile, Inc. ytyk.org is not affiliated with, endorsed by or licensed by Scaled Agile, Inc. These cards are independent commentary written in our own words; no SAFe text, graphic or Big Picture is reproduced here.
Connects to
- Scrum — Scrum's whole scope is the one unit SAFe treats as its smallest piece
Odd one out Check yourself
Three of these are things SAFe adds above the team level. Which one is a team-level concern it inherits?
Show the answer
A cross-functional group of ten or fewer people delivering value
That is the Agile Team, and SAFe's definition of it is near-identical to Scrum's. Everything SAFe genuinely adds sits above it.