In 30 seconds
- SAFe coordinates many agile teams into Agile Release Trains.
- Trains plan together in PI Planning every 8 to 12 weeks.
- Comes in configurations from Essential to Full SAFe.
How SAFe is structured
- Teams work in Scrum or Kanban.
- Agile Release Train (ART): 5 to 12 teams, roughly 50 to 125 people, delivering together.
- Program Increment (PI): a planning cycle, typically 8 to 12 weeks, starting with PI Planning.
- Portfolio: funds value streams and manages large initiatives.
Configurations
Essential SAFe covers a single train. Large Solution adds coordination across trains. Portfolio SAFe adds lean portfolio management. Full SAFe combines everything.
Why it's popular, and criticized
Dean Leffingwell released SAFe in 2011. Large enterprises like its structure, defined roles and training paths. Critics say it adds layers and can turn agile into a heavy process if adopted mechanically. See SAFe vs LeSS.
Myth vs reality
Myth · SAFe is just Scrum for big companies.
Reality · It adds roles, events and portfolio practices on top.
Myth · You must adopt Full SAFe.
Reality · Most organizations start with Essential SAFe.
Myth · SAFe guarantees agility.
Reality · Without real culture change, it can become a renamed waterfall.
FAQ
Who maintains SAFe?
Scaled Agile, Inc., which publishes updated versions.
What is PI Planning?
A two-day event where all teams on a train plan the next increment together.
Does SAFe use story points?
Many SAFe teams do, normalized across the train.