# Scrum@Scale

Scrum@Scale uses modular Scrum-based coordination cycles to align networks of teams while aiming for a minimum viable bureaucracy.

- Type: framework
- Domain: Delivery & agility
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/scrum-at-scale/>)

## What it means

Scrum@Scale is a framework created by Jeff Sutherland for coordinating multiple Scrum Teams and connecting delivery with executive decision-making. It separates the concerns of how work gets done and what work should be done into interacting cycles, then scales coordination through small representative groups rather than one fixed hierarchy.

## Why it matters

Organizations need to coordinate priorities, impediment removal, releases, and learning without turning every decision into a large meeting. Scrum@Scale provides a modular pattern for linking teams, Product Owners, and leadership while retaining short feedback loops and making organizational impediments visible.

## When to use it

Consider Scrum@Scale when several capable Scrum Teams need shared prioritization and impediment resolution, and the organization prefers an adaptable network over a highly specified enterprise model. It can start with a small group and expand, but requires real authority in both product and delivery coordination bodies.

## How it works

1. Establish effective Scrum Teams with clear products, usable increments, and functioning feedback loops before scaling coordination.
2. Connect Scrum Masters through a Scrum of Scrums that addresses cross-team delivery, dependencies, quality, and impediments.
3. Connect Product Owners through a MetaScrum that aligns product vision, backlog priorities, and stakeholder decisions.
4. Use an Executive Action Team and Executive MetaScrum to remove enterprise impediments and align strategic priorities.
5. Inspect metrics and outcomes, then add or alter coordination cells only where the system needs them.

## A practical example

A travel company has eight teams across booking, pricing, identity, and service operations. A Scrum of Scrums coordinates a shared release dependency, while the MetaScrum resolves competing priorities between loyalty and checkout work. An executive group removes a procurement delay that no team can solve, and the network adapts after each delivery cycle.

## Where it breaks

The framework depends on healthy Scrum at team level; scaling weak teams scales their problems. Representative forums can become reporting hierarchies, and overlapping accountabilities may confuse decision rights. “Minimum viable bureaucracy” still requires deliberate design, while product boundaries, technical architecture, and incentives may demand changes beyond the framework’s diagrams.

## Common mistakes

- Creating a Scrum of Scrums as a status meeting for managers.
- Scaling before teams can produce usable increments reliably.
- Giving coordination groups responsibility without authority to remove impediments or order work.

## Sources

1. [The Scrum@Scale Guide](<https://www.scrumatscale.com/scrum-at-scale-guide/>) — Scrum@Scale · Official framework guide
2. [The Scrum@Scale Guide PDF](<https://www.scrumatscale.com/wp-content/uploads/2020/12/official-scrum-at-scale-guide.pdf>) — Scrum@Scale · Official guide document

## Related topics

- [Scrum](<https://wiki.soroush.uk/topic/scrum/>)
- [Nexus Framework](<https://wiki.soroush.uk/topic/nexus-framework/>)
- [Scaled Agile Framework](<https://wiki.soroush.uk/topic/scaled-agile-framework/>)
