tezvyn:

Scrum@Scale: Agile for Teams of Teams

AI-drafted, machine-checkedSource: scrumatscale.comintermediate
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.

Read the original → scrumatscale.com

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.