📌 Introduction

In small Agile teams, coordination is straightforward. But what happens when you have 10+ Scrum teams working on a single product? You need a structured way to scale collaboration, resolve cross-team blockers, and align deliveries.

Enter the Scrum of Scrums (SoS) - an essential practice for large-scale Agile environments.

If you're preparing for a Scrum Master interview or working in a scaled Agile setup like SAFe, this concept is critical. It's also one of the most frequently discussed topics in ourScrum Master Interview Bootcamp.

🧠 What is Scrum of Scrums?

The Scrum of Scrums is a scaled Agile coordination meeting that allows multiple Scrum teams working on the same product or system to synchronize their progress.

It’s not part of the official Scrum Guide but is widely used in frameworks like SAFe, LeSS, and Nexus.

“A Scrum of Scrums is a technique to scale Scrum up to large groups (over a dozen people), consisting of teams of teams.” - Agile Alliance

🎯 Purpose of Scrum of Scrums

• Align multiple Scrum teams

• Identify and resolve cross-team dependencies

• Share progress toward the common goal

• Maintain transparency across teams

• Enable smoother integration of deliverables

• Facilitate faster decision-making at scale

👥 Who Attends the Scrum of Scrums?

Each Scrum Team sends one representative, typically:

• A Scrum Master, or

• A Team Lead, or

• A rotating delegate with technical knowledge

The meeting is often facilitated by a Chief Scrum Master or Release Train Engineer (RTE) in SAFe.

🕒 How Often is it Held?

• Daily (for fast-paced programs), or

• 2–3 times per week, or

• Weekly, depending on the cadence of teams and program scale

The frequency should support the sprint schedule and integration checkpoints.

📋 Scrum of Scrums Agenda

A focused Scrum of Scrums meeting typically covers the following:

🔹 1. What has your team done since the last Scrum of Scrums?

Share progress updates related to sprint goals or milestones.

🔹 2. What will your team do before the next Scrum of Scrums?

Outline the planned work and deliverables.

🔹 3. Are there any impediments or blockers affecting your team?

This includes technical issues, dependency delays, or resource bottlenecks.

🔹 4. Is your team planning anything that might affect other teams?

Highlight integration points, shared modules, or architectural changes.

🧾 Example of a Scrum of Scrums in Action

Scenario: A fintech product involves 5 Scrum teams working on mobile apps, backend services, and APIs.

• Team A is building the API layer

• Team B (mobile app team) is blocked due to missing API documentation

• During the Scrum of Scrums, the API team agrees to deliver and document endpoints within 24 hours

➡ This removes the blocker without email chains or delays, keeping the entire sprint on track.

Such real-world cases are exactly what you’ll be prepped for in ourScrum Master Interview Bootcamp.

🏗️ Best Practices for Scrum of Scrums

• Keep meetings short (15–30 mins)

• Only discuss cross-team concerns - not internal team issues

• Use a shared board to track inter-team blockers

• Rotate representatives for inclusivity

• Document actions and follow-ups

• Avoid turning it into a status meeting

🧠 Scrum of Scrums vs Daily Scrum

🧰 Tools to Run Scrum of Scrums

• Jira Advanced Roadmaps

• Miro / Mural boards

• Confluence action trackers

• Slack/Teams channels for async updates

🧭 Final Thoughts

The Scrum of Scrums is like Agile’s “mission control” - coordinating multiple moving pieces and ensuring that the whole is greater than the sum of its parts.

If you're aiming for a leadership role in scaled Agile, understanding how to run or participate in a Scrum of Scrums will set you apart.

👉 Ready to go deeper into scaled Agile, SAFe, and cross-team collaboration?
Join our live coaching sessions through theScrum Master Interview Preparation Bootcamp to master real-world scenarios and ace your interviews.