Scaled Agile Framework (SAFe)
SAFe scales agile beyond a single team by organising teams into Agile Release Trains that plan together in a shared cadence, so multiple teams can ship one integrated product instead of sprinting in isolation.
Four tiers stack up, team-level work at the base and portfolio strategy sitting at the top.
Reach for this when…
- Agile works fine inside a team but falls apart coordinating several teams on one product.
- Leadership wants enterprise-level planning and budgeting without losing agile speed.
- Several agile teams keep integrating badly because none of them plan on the same cadence.
How to run it
- Organise teams into an Agile Release Train around a shared value stream.
- Run Program Increment (PI) Planning to align on a common 8-12 week increment.
- Sequence portfolio work using Weighted Shortest Job First, not whoever shouts loudest.
- Sync progress across teams with a regular System Demo.
- Inspect and adapt at the end of each Program Increment before planning the next.
A worked example
Situation. Bence Nagy led engineering at Duna Pay, a payments SaaS company in Budapest, Hungary, where six agile teams built one platform, each sprinting independently and integrating badly at every release.
Applied. He organised the six teams into a single Agile Release Train, ran PI Planning to align everyone on a shared ten-week increment, and had the portfolio backlog prioritised by Weighted Shortest Job First instead of by whichever product owner was loudest that week.
Result. The train's first synchronised release shipped with far fewer integration surprises, and for the first time portfolio leaders could see what all six teams were actually working on at once.
The catch
SAFe adds real coordination overhead - PI Planning alone takes teams offline for one or two days every increment - and organisations that adopt the ceremonies without the underlying decentralised decision-making just get slower, more expensive agile. It's built for genuinely large, coordinated product efforts; forcing it onto two or three teams is using a crane to hang a picture.
If your teams could coordinate with a fifteen-minute conversation, you don't need a Release Train.
Origin: Dean Leffingwell / Scaled Agile, Inc.