# Large-Scale Scrum

Large-Scale Scrum applies Scrum to multiple teams working on one product while deliberately minimizing added roles, artifacts, and coordination layers.

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

## What it means

Large-Scale Scrum \(LeSS\) is a framework for several teams developing one product with one Product Owner, one Product Backlog, one Sprint, and one integrated increment. Rather than placing a new management structure above separate Scrum teams, LeSS redesigns the organization around a whole-product focus and shared responsibility.

## Why it matters

Scaling often multiplies backlogs, coordinators, component groups, and handoffs. LeSS instead treats those structures as possible causes of delay. Its “more with less” stance encourages broad feature teams, direct customer understanding, transparent integration, and organizational experiments that improve the entire product system.

## When to use it

Use LeSS when multiple teams genuinely contribute to one product and leadership is willing to simplify structures, reduce component ownership, and expose systemic constraints. The basic framework suits a smaller group of teams; LeSS Huge extends the ideas for many teams through requirement areas.

## How it works

1. Define one product broadly enough to represent customer value, then maintain one ordered Product Backlog and one Product Owner.
2. Organize long-lived, cross-functional feature teams that can deliver customer-facing work across components.
3. Run a common Sprint with coordinated planning, team-level Daily Scrums, an integrated review, and an overall retrospective.
4. Integrate continuously toward one Definition of Done and one potentially releasable product increment.
5. Use retrospectives and experiments to remove organizational policies, specialist queues, and structures that prevent whole-product learning.

## A practical example

Six teams maintain an online marketplace. Instead of separate mobile, search, payments, and seller backlogs, they establish one product backlog and gradually form feature teams. A checkout objective is split collaboratively; representatives coordinate shared concerns during the Sprint, and the review demonstrates one integrated customer journey rather than six component reports.

## Where it breaks

LeSS asks for consequential organizational change, not only new meetings. Feature-team formation can be difficult where architecture, skills, vendors, or compliance responsibilities are strongly siloed. One Product Owner may become a bottleneck if discovery is not distributed. The framework offers principles and rules, but teams must design many practical details through experimentation.

## Common mistakes

- Keeping component teams and separate backlogs while adopting LeSS event names.
- Adding coordinators instead of reducing dependencies and enabling direct team collaboration.
- Interpreting one Product Owner as one person doing all product discovery and clarification.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/large-scale-scrum/#visualization-large-scale-scrum>)

## Sources

1. [Principles Overview](<https://less.works/less/principles/overview>) — The LeSS Company · Official framework principles
2. [Large-Scale Scrum Brochure](<https://less.works/resources/LeSS-brochure.pdf>) — The LeSS Company · Official framework overview
3. [The Large-Scale Scrum Framework](<https://www.atlassian.com/agile/agile-at-scale/less>) — Atlassian · Professional overview

## 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/>)
