Scrum of Scrums

What Scrum of Scrums Is For

Scrum of Scrums is a scaling coordination pattern, not a new delivery method. Its purpose is to give representatives from multiple teams a regular place to surface inter-team dependencies, blockers, sequencing issues, and delivery risks so work can stay aligned across a larger programme.

It is most useful when teams can execute independently most of the time, but still need a lightweight mechanism to coordinate handoffs, shared components, shared environments, or timing decisions that cut across team boundaries.

How Scrum of Scrums Works in Practice

In practice, Scrum of Scrums usually adds a coordination layer above team stand-ups. Each team keeps its own daily stand-up, while selected representatives meet separately to discuss what their team has completed, what is coming next, and what may affect other teams.

The meeting should stay focused on cross-team issues. If it becomes a status broadcast, it loses its value. The goal is not to review every task, but to expose dependencies early enough that teams can adjust plans before blockers become delivery delays.

What Problems Scrum of Scrums Helps Prevent

The main failure mode in multi-team delivery is not usually lack of effort, but lack of visibility across teams. Without a coordination forum, one team can unknowingly create a dependency bottleneck, duplicate another team’s work, or miss a timing conflict until late in the sprint or release cycle.

Scrum of Scrums reduces that risk by making cross-team friction visible sooner. It also helps prevent “local optimisation,” where each team looks healthy on its own while the wider programme stalls because shared decisions are not being surfaced in time.

When Scrum of Scrums Is the Right Fit

Scrum of Scrums is best suited to environments with multiple autonomous teams working toward a shared outcome, especially where shared architecture, security reviews, release coordination, or integration work can create dependencies. It is less useful when there are only a few teams, or when coordination can be handled through simpler channels.

For security organisations, it can be a practical way to improve cross-functional awareness, because delivery, operations, risk, and security work often intersect at the same dependency points. Used well, it supports faster escalation, clearer ownership, and better programme-level decision-making.

Practitioner Guidance

Why practitioners should care: Scrum of Scrums is only effective if it stays dependency-focused. If the attendees cannot make or escalate decisions, the forum degrades into reporting theatre and adds overhead without improving coordination.

Common misunderstanding: Many teams treat it as a bigger daily stand-up. In reality, it should concentrate on cross-team blockers, interface risks, and upcoming handoffs, while leaving team-internal updates to the individual team ceremonies.

Practitioner takeaway: Keep the meeting small, representative, and decision-oriented, then tie the discussion to a visible dependency or escalation path so unresolved issues do not disappear after the call.