Scrum guide · Scaling and learning
Scrum of Scrums: How to Coordinate Multiple Scrum Teams
A Scrum of Scrums is a meeting, and a structure, in which representatives of several Scrum Teams coordinate their work. It is the simplest way to scale Scrum when a few teams build one product together.
Key takeaways
- A Scrum of Scrums coordinates several Scrum Teams through representatives.
- It focuses on dependencies, integration and shared impediments.
- It is the basic building block of Scrum@Scale.
How it works
- Each team sends a representative, often a Developer with the right technical knowledge, sometimes the Scrum Master.
- Representatives meet regularly, from daily to a few times a week, often for about 15 minutes, with time afterwards for problem-solving.
- The focus is integration, dependencies and impediments that affect more than one team.
- Representatives share the outcome with their own teams.
Sample agenda
- What has my team done since we last met that affects other teams?
- What will my team do next that affects other teams?
- What impediments is my team facing that others could help with?
- Are we about to put something in another team's way?
- Problem-solving on the issues raised (after the core time-box).
Tips
- Keep a shared board of cross-team dependencies and impediments.
- Send the person best placed to discuss current dependencies, which may change over time.
- Align Sprint cadences so teams plan and review together.
- Hold a joint Sprint Review for the integrated product.
Pitfalls
- Turning it into a status report for managers.
- Representatives who can't make decisions or don't report back.
- Too many teams in one meeting; split into layers if needed.
How it relates to scaling frameworks
The Scrum of Scrums is a core building block of Scrum@Scale. Similar coordination appears in LeSS and in SAFe's ART Sync; see Agile Release Train.
Frequently asked questions
How many teams can a Scrum of Scrums coordinate?
Typically up to about five to ten teams. Beyond that, organisations add another layer, sometimes called a Scrum of Scrums of Scrums.
Is the Scrum of Scrums part of the Scrum Guide?
No. It is a widely used scaling practice, not part of the official Scrum framework.
What is a Scrum of Scrums?
A coordination meeting in which representatives from several Scrum Teams discuss dependencies, integration and shared impediments.
Who attends a Scrum of Scrums?
One representative per team, often a Developer with relevant technical knowledge or the Scrum Master. The best person can change depending on current dependencies.
How often does a Scrum of Scrums meet?
Anywhere from daily to a few times a week, depending on how many dependencies exist. Many keep the core discussion to about 15 minutes.
Who created the Scrum of Scrums?
The practice is generally credited to Jeff Sutherland and Ken Schwaber, who used it to coordinate multiple teams in the 1990s.
What is the difference between a Daily Scrum and a Scrum of Scrums?
The Daily Scrum is for one team's Developers to plan their day towards the Sprint Goal. A Scrum of Scrums coordinates work between teams.
What is a Scrum of Scrums Master?
In Scrum@Scale, the person who facilitates the Scrum of Scrums and helps remove impediments across teams. See Scrum@Scale.
How does the Scrum of Scrums relate to SAFe?
SAFe uses similar coordination events, such as the ART Sync, to align teams on an Agile Release Train. See SAFe.
What makes a Scrum of Scrums effective?
Representatives who can make decisions, a shared board of dependencies and impediments, aligned Sprint cadences and a focus on problems rather than status.
Is the Scrum of Scrums a status meeting?
It should not be. Its purpose is to surface and resolve cross-team issues, not to report progress to managers.