Large-Scale Scrum
Large-Scale Scrum applies Scrum to multiple teams working on one product while deliberately minimizing added roles, artifacts, and coordination layers.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/large-scale-scrum/
01What 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.[1][2][3]
- One Product Owner
- Accountability for value and one ordered backlog
- Feature teams
- Long-lived cross-functional teams delivering customer value
- Common Sprint
- Shared cadence with coordinated planning and review
- Continuous integration
- All teams combine work throughout the Sprint
- One Definition of Done
- Common quality boundary for the whole product
- One increment
- Potentially releasable integrated product outcome
LeSS seeks less organizational complexity around Scrum; component silos and local optimization undermine whole-product learning.
02Why 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.
03When 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.
04How it works
- Define one product broadly enough to represent customer value, then maintain one ordered Product Backlog and one Product Owner.
- Organize long-lived, cross-functional feature teams that can deliver customer-facing work across components.
- Run a common Sprint with coordinated planning, team-level Daily Scrums, an integrated review, and an overall retrospective.
- Integrate continuously toward one Definition of Done and one potentially releasable product increment.
- Use retrospectives and experiments to remove organizational policies, specialist queues, and structures that prevent whole-product learning.
05A 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.
06Where 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.
07Sources
- Principles OverviewThe LeSS Company · Official framework principlesPrinciples Overview
- Large-Scale Scrum BrochureThe LeSS Company · Official framework overviewLarge-Scale Scrum Brochure
- The Large-Scale Scrum FrameworkAtlassian · Professional overviewThe Large-Scale Scrum Framework