All templates

Scrum of Scrums Template

Agile / Scrum 30 min 2-3 times per week One representative per Scrum team plus a facilitator (5-9 people)

The scrum of scrums template scales Scrum coordination across multiple teams working toward a shared outcome. Think of it as a standup for team representatives. The focus is not individual tasks but the seams between teams: dependencies, integration points, and blockers that no single team can clear alone.

When to use it

Use it when two or more Scrum teams build a connected product or program. Run it a few times a week rather than daily, since cross-team issues move slower than individual work. Keep it to about thirty minutes and focused on coordination.

Who attends

Send one representative per team, often the Scrum Master or a senior engineer who knows the dependencies. A facilitator keeps the meeting moving. Reps must be empowered to speak for their team and commit to actions.

How to run it

Open with a quick progress round so every team knows where the others stand. Then spend the bulk of the time on the seams: each rep names work that depends on another team and confirms handoffs and timing. Surface blockers that cross boundaries, then assign a clear owner and due date to every dependency and impediment before closing.

Facilitator tips

  • Focus on the seams between teams, not the work inside each team.
  • Empower the reps so they can commit on behalf of their team.
  • Track dependencies visibly so nothing falls between teams.
  • Escalate fast when a blocker needs leadership attention.

Common mistakes

  • Rehashing each team's internal standup instead of cross-team issues.
  • Sending reps who cannot commit, so decisions stall.
  • Surfacing dependencies but never assigning owners or dates.
  • Running it daily when the cadence does not justify it.

Coordinating many teams? Run it in OrgTP to track cross-team dependencies and blockers in one shared view.

Agenda

30 minutes total · 4 sections

  1. Team progress round 10 min
    Each team rep shares what their team finished and what they will deliver before the next sync.
  2. Surface dependencies 8 min
    Reps name work that depends on another team and confirm the handoffs and timing.
  3. Raise shared blockers 7 min
    Identify impediments that cross team boundaries and need coordination to resolve.
  4. Assign cross-team actions 5 min
    Agree who owns each dependency and blocker, with a due date, before adjourning.

Run this meeting live in OrgTP

Stop copying agendas into a doc every week. OrgTP runs your meetings live — scorecard, rocks, issues, and to-dos all in one place, with your AI agents in the room.