# Scaling Agile with SAFe

> What changes when many agile teams build one product. How a scrum of scrums links a few teams, and how SAFe groups 50 to 125 people to plan as one.

**Course:** [Agile, Scrum and Kanban](https://learn.benibix.com/learn/business-agile)  
**Time:** 12 min

**After this lesson you can:**

- Run a scrum of scrums
- Say how SAFe groups teams
- Name the cost of scaling

## How many agile teams work on one product

One Scrum Team is 10 people or fewer, so a big product needs several teams. They then have to share work, avoid getting in each other's way and agree on one plan. A scrum of scrums is a simple fix for a few teams. The Scaled Agile Framework, or SAFe, is a full system for 50 people or many more.

A scrum of scrums is a meeting where each team sends one person, often one of its Developers. They share what their team finished, what comes next and what might block another team. Most of all, they look for work where one team waits on another. It is not in the Scrum Guide, but many groups use it.

SAFe goes much further. Teams join into teams of teams, called release trains, of about 50 to 125 people. A train plans as one, at a two-day event every 8 to 12 weeks. Every team in the train works to the same rhythm.

Above the trains, SAFe adds levels for very large systems. At the top is the whole firm, where leaders pick and fund the work. SAFe sets out shared roles, events and habits for each level. That makes it popular with big firms that want one way of working.

The cost is weight. SAFe brings many new roles, meetings and words, and some say it drifts from the light spirit of the Manifesto. A firm with 3 teams does not need it. A firm with 30 teams on one product may need something like it.

Scaling works best when teams are cut around parts of the product, not around skills. A team that owns the checkout from screen to data can ship on its own. A team of only testers has to wait on everyone, at every scale.

The common mistake is scaling before one team works well. Ten teams that cannot ship a working piece each sprint become one large team that cannot either. Get one team right first, then copy it.

![Four levels stacked from bottom to top. At the bottom, agile teams. Above them, a release train of 50 to 125 people that plans every 8 to 12 weeks. Above that, large solution, several trains on one big system. At the top, portfolio, which picks and funds the work.](https://learn.benibix.com/diagrams/agile-safe-levels.svg)

### Example: Jack's three teams meet twice a week

Jack's company in Berlin has 3 Scrum Teams on one shop app. Twice in one month, one team breaks the checkout another team just finished.

They start a 15-minute scrum of scrums twice a week, with one person from each team. Clashes are now found in days, not at the Sprint Review, and they do not need anything heavier.

**Words in this lesson:** [Scrum of Scrums](https://learn.benibix.com/term/business/scrum-of-scrums), [Scaled Agile Framework (SAFe)](https://learn.benibix.com/term/business/scaled-agile-framework)

**Question:** Three Scrum Teams keep blocking each other on one product. What is the lightest first step?

**Answer:** Hold a scrum of scrums with one person from each team. A scrum of scrums is a short, regular meeting that finds where teams wait on each other. A full framework brings much more weight than three teams usually need.

---

Source: https://learn.benibix.com/learn/business-agile/scaling-agile-with-safe
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
