Scrum@Scale: Agile for Teams of Teams
Scrum@Scale treats your organization as a network of Scrum teams, aiming for "minimum viable bureaucracy." It coordinates multiple teams working on one complex product.
The mental model
Scrum@Scale is a framework for applying Scrum principles to an entire organization, not just a single team. It envisions the company as a network of interconnected Scrum teams, creating a "scale-free" architecture. This means the basic patterns of interaction repeat at every level, from a small team to the entire enterprise. The goal is to coordinate many teams with the least amount of overhead—a "minimum viable bureaucracy."
How it works
The framework extends core Scrum by introducing scaled versions of roles, events, and artifacts. Multiple Scrum teams form a "Scrum of Scrums" to coordinate their work and resolve dependencies. This group has its own scaled daily scrum and its own backlog of cross-team issues. This structure can be repeated, with multiple Scrums of Scrums forming a "Scrum of Scrums of Scrums," allowing the framework to scale to hundreds of people while keeping each unit small and agile.
When to use it
Use Scrum@Scale when your product or system has grown too complex for a single team to handle. It's designed for situations requiring the coordinated effort of many teams—from five to five thousand—to develop, deliver, and sustain a single, integrated product. It applies to large enterprises and growing startups where inter-team coordination is becoming a bottleneck.
When not to use it
Do not use Scrum@Scale as a fix for dysfunctional teams. If your individual teams are not successfully practicing Scrum—if they have messy backlogs, unclear roles, or consistently miss sprint goals—scaling will only amplify these problems across the organization. It is also overkill for organizations with only a few teams that can coordinate informally; the "minimum viable bureaucracy" is still bureaucracy.
One canonical example
A large bank developing a new mobile banking app uses Scrum@Scale. One group of teams works on personal accounts, another on business lending, and a third on security infrastructure. Each group operates as a Scrum of Scrums. A higher-level Scrum of Scrums of Scrums, composed of representatives from each group, coordinates major feature releases, manages architectural dependencies, and ensures the entire app provides a unified user experience.
Interview question
Which scenario best describes an appropriate application of Scrum@Scale?
- a.A large enterprise coordinating many Scrum teams on a complex, integrated product.Correct
- b.A company aiming to establish a strict, hierarchical management structure for development.
- c.A small startup with a single product team seeking to formalize its agile process.
- d.An organization with multiple dysfunctional Scrum teams needing to fix their core issues.
Why? this is the answer
The correct answer (A) aligns with Scrum@Scale's purpose of coordinating numerous teams on a single, complex product, as stated in the "WHEN TO USE IT" section. Option D is incorrect because the card explicitly warns against using Scrum@Scale to fix dysfunctional teams, as it would only amplify existing problems.
Just read this? Test yourself on what you have been reading.
Read the original → scrumatscale.com
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles