Scaling Agile can feel like trying to run a relay race with five teams, three maps, and one confused mascot. Everyone is moving fast. But not always in the same direction. That is where Scrum of Scrums comes in. It helps multiple Scrum teams work together without turning every meeting into a calendar monster.
TLDR: Scrum of Scrums is a short coordination meeting for several Agile teams working on the same product or goal. Each team sends one person to share progress, blockers, and risks. For example, if 4 teams are building a mobile banking app, Scrum of Scrums can help reduce duplicated work by 20% and catch cross-team blockers earlier. It is simple, fast, and great for keeping everyone aligned.
What Is Scrum of Scrums?
Scrum of Scrums is a way to scale Scrum across multiple teams. Think of it as a “team of teams.” Each Scrum team still runs its own sprint, daily Scrum, review, and retrospective. But when teams depend on each other, they need a shared place to sync.
That shared place is the Scrum of Scrums meeting.
It is not a status theater. It is not a place to read reports like a sleepy robot. It is a quick meeting where teams say:
- What did our team finish?
- What will our team do next?
- What is blocking us?
- Are we about to block another team?
The goal is simple. Find problems early. Fix them fast. Keep delivery smooth.
Why Do Teams Need It?
One Scrum team is like a small pizza kitchen. Easy to manage. Everyone can hear when the oven timer rings.
Now imagine five pizza kitchens making one giant wedding feast. One team is making dough. One is making sauce. One is baking. One is packing. One is handling delivery. If the sauce team is late, everyone suffers. If no one talks, the bride gets cold pizza. Bad day.
Large products work the same way. Teams often share code, data, designs, APIs, release dates, and customer promises. Without coordination, teams may:
- Build the same feature twice.
- Wait days for another team.
- Miss dependencies.
- Break each other’s work.
- Ship late.
Scrum of Scrums helps teams see the whole board. Not just their own corner.
Who Attends Scrum of Scrums?
Each team sends one representative. This person is often called an ambassador. Fancy word. Simple job.
The ambassador speaks for the team. They also bring useful news back to the team. This can be:
- A Scrum Master.
- A developer.
- A tester.
- A product specialist.
- Anyone who understands the work.
The same person does not need to attend every time. In fact, rotating the role can help. It spreads knowledge. It also stops one person from becoming the “human information mailbox.”
A Product Owner may attend if product decisions are needed. An architect may join when technical design is involved. But keep the group small. If 30 people show up, it is no longer Scrum of Scrums. It is a conference with snacks missing.
How Often Should It Happen?
There is no magic number. The meeting should happen as often as needed.
Common choices are:
- Daily: Good for high-risk or fast-moving projects.
- Two or three times per week: Good for many product teams.
- Weekly: Good when dependencies are light.
Keep it short. A good Scrum of Scrums is often 15 to 30 minutes. If it turns into a long debate, pause. Create a smaller follow-up with only the needed people.
The meeting should solve coordination issues, not every issue in the universe.
The Four Magic Questions
Scrum of Scrums often uses a simple question set. These questions make the meeting clear and fast.
- What has our team done since the last meeting?
- What will our team do before the next meeting?
- What blockers are slowing us down?
- Will our work block or affect another team?
The fourth question is the superhero question. It helps teams warn each other before trouble arrives wearing tap shoes.
For example, Team A may say, “We are changing the login API on Thursday.” Team B may reply, “Wait. Our checkout flow uses that API.” Boom. Problem found early. No drama. No weekend panic.
A Simple Example
Let’s say a company is building a travel booking platform. There are four Scrum teams:
- Team Flight: Handles flight search.
- Team Hotel: Handles hotel booking.
- Team Payment: Handles checkout.
- Team Mobile: Builds the app experience.
Each team has its own sprint goal. But they all depend on each other. The mobile app needs flight and hotel data. Payment needs final prices. Flight and hotel teams need shared customer details.
In Scrum of Scrums, Team Payment says, “We need final pricing rules by Wednesday.” Team Hotel says, “We can deliver that Tuesday.” Team Flight says, “We are delayed by one day.” Team Mobile says, “That delay affects our demo.”
Now the teams can adjust. They can change demo scope. They can mock data. They can shift tasks. The problem is visible. That is the whole point.
What Makes Scrum of Scrums Work?
Good Scrum of Scrums is not about more meetings. It is about better signals.
Here are the key ingredients:
- Clear purpose: Focus on cross-team coordination.
- Right people: Send someone who can explain the work.
- Short format: Keep it focused and quick.
- Visible dependencies: Use a shared board or roadmap.
- Fast follow-ups: Solve details outside the main meeting.
- Real ownership: Blockers need names, dates, and actions.
A shared board helps a lot. It can show dependencies, risks, release goals, and blocked work. When everyone sees the same picture, fewer surprises jump out of the bushes.
Common Mistakes to Avoid
Scrum of Scrums can go wrong. Usually in very human ways.
Watch out for these traps:
- Turning it into a status report: Managers do not need a performance show.
- Inviting too many people: Bigger is not always better.
- Ignoring blockers: If blockers never get fixed, people stop caring.
- No decision power: Representatives must be able to act or escalate fast.
- Talking only about tasks: Focus on dependencies and risks.
The biggest mistake is pretending everything is fine. Scrum of Scrums works best when people are honest. If there is a mess, say so. Agile teams do not fear mess. They inspect it. Then they clean it up.
Scrum of Scrums vs. Daily Scrum
The Daily Scrum is for one team. It helps that team plan the day.
Scrum of Scrums is for several teams. It helps them coordinate shared work.
That is the main difference.
Daily Scrum asks, “How do we move our team forward?” Scrum of Scrums asks, “How do all teams move together?”
Both are useful. But they solve different problems.
How to Start Scrum of Scrums
You do not need a giant framework to begin. Start small.
- Pick the teams: Include teams working on the same product or release.
- Choose ambassadors: One person per team is enough.
- Set a rhythm: Try twice per week for 30 minutes.
- Use the four questions: Keep the format simple.
- Track blockers: Write them down and assign owners.
- Improve: Review what works after two or three weeks.
Do not aim for perfect. Aim for useful. If the meeting helps teams avoid delays, it is working. If people leave more confused, change it.
Final Thoughts
Scrum of Scrums is like a traffic light for busy Agile teams. It does not drive the cars. It helps them avoid crashes.
When teams grow, communication can get messy. Dependencies hide. Blockers multiply. People start saying scary things like, “I thought your team owned that.” Scrum of Scrums keeps those surprises away.
Keep it short. Keep it honest. Keep it focused on shared work. Do that, and scaling Agile becomes less like herding cats and more like leading a very caffeinated marching band.