Scrum of Scrums | Agile Scrum Master
Scrum of Scrums is a lightweight coordination pattern where each Scrum Team sends one representative, often called an ambassador, to a regular cross-team meeting focused on dependencies, risks, and impediments that affect more than one team. It mirrors the structure of a Daily Scrum but shifts the focus from individual team progress to what other teams need to know. Key elements: a rotating or role-based ambassador from each team, a small set of standard questions covering progress, plans, and obstacles, and a shared record for tracking cross-team issues through to resolution rather than letting them disappear after the meeting ends.
What Scrum of Scrums coordinates
Scrum of Scrums exists because adding more Scrum Teams to a product does not automatically add proportional delivery capacity. Each additional team introduces new dependencies, integration points, and decisions that need input from more than one team, and those cross-team concerns rarely get resolved inside any single team's own Daily Scrum. Scrum of Scrums creates a dedicated, lightweight forum for exactly that category of issue.
Scrum of Scrums is not part of the Scrum framework itself; it is a widely used technique that grew up alongside Scrum specifically to handle coordination once more than one team is working toward the same product. It is deliberately lighter and less prescriptive than a full scaling framework, which is part of why it remains common even inside organizations that use a heavier framework for other aspects of scaling.
How Scrum of Scrums is structured
Each Scrum Team selects one representative, commonly called an ambassador, to attend the Scrum of Scrums. The ambassador is often the Scrum Master, but any team member who can speak accurately to dependencies and represent the team's context is a reasonable choice. Attendance can rotate over time, and the makeup of the group can flex based on which topics are currently most relevant.
Meetings typically run daily, a few times a week, or weekly, depending on team size and how tightly the teams' work is coupled. Unlike a Daily Scrum, Scrum of Scrums is not fixed to a fifteen-minute timebox; it runs long enough to cover genuine cross-team coordination, though well-prepared groups often finish in fifteen to thirty minutes.
A common Scrum of Scrums question format
Scrum of Scrums commonly follows a small set of questions that mirror the Daily Scrum but shift the focus from individual progress to cross-team impact:
- What has the team completed since the last meeting - shares progress that other teams may depend on or need to react to.
- What problems has the team run into - surfaces impediments that may need help or attention from outside the team.
- What does the team plan to do before the next meeting - gives other teams visibility into upcoming work that could affect them.
- What might the team's upcoming work affect in other teams - flags potential interference or dependency before it becomes a blocker, rather than after.
Organizations adapt this format to fit their own context, and some maintain a shared backlog specifically for cross-team issues raised in the meeting, so items are tracked to resolution rather than only discussed once and forgotten.
Why Scrum of Scrums needs a decision-making purpose
Scrum of Scrums only creates value if it actually resolves what it surfaces. The purpose of the meeting is to identify and remove cross-team impediments, which sometimes means teams temporarily adjust responsibilities, lend capacity, or renegotiate a dependency on the spot rather than simply reporting the problem and moving on. A Scrum of Scrums that only reports status without empowering ambassadors to make or escalate decisions quickly turns into overhead instead of coordination.
How Scrum of Scrums relates to other scaling approaches
Scrum of Scrums has directly influenced larger, more prescriptive scaling frameworks. Scrum @ Scale (SoS) builds a fuller structure directly on top of this pattern, including a dedicated Scrum of Scrums Master role focused on facilitating cross-team coordination and resolving systemic impediments. Scaled Agile Framework (SAFe) and Large-Scale Scrum (LeSS) address similar coordination needs through their own mechanisms, but Scrum of Scrums remains useful on its own as a lightweight starting point for organizations that are not ready to adopt a full framework, or that only need cross-team coordination without the rest of a heavier framework's structure.
Common misuse and fake-agile patterns
Scrum of Scrums frequently drifts into a form that looks like coordination but does not actually resolve anything. Typical problems include:
- Status theater - ambassadors report what their team did without surfacing real dependencies or risks, so the meeting produces information without producing decisions.
- Ambassador without authority - representatives cannot make or escalate decisions on the spot, so every cross-team issue has to be taken back to another meeting before anything moves forward.
- No follow-through - impediments and dependencies are discussed but never tracked to resolution, so the same issues resurface meeting after meeting.
- Silent representatives - information raised in the meeting never makes it back to the ambassador's own team, so the rest of the team stays unaware of decisions that affect their work.
The fix in each case is the same: keep the meeting focused on decisions and follow-through rather than status reporting, and check whether cross-team impediments are actually getting resolved faster than they would without the meeting.
Scrum of Scrums is a coordination pattern where representatives from multiple Scrum Teams meet to surface cross-team dependencies and impediments