Large-Scale Scrum (LeSS): Scale Scrum with minimal overhead

What is LeSS?

LeSS (Large-Scale Scrum) is a minimalist framework for scaling Scrum to multiple teams (2–8 teams), without the overhead seen in some other scaling frameworks. At its core, it's 'just Scrum', but bigger. For organizations with hundreds of developers, there is LeSS Huge, which adds some extra structure, but still adheres to the philosophy of simplicity.

‍

Core Philosophy

LeSS emphasizes starting with one team and gradually adding more teams, instead of immediately creating an entire management layer and separate roles. The idea: “Scrum, just bigger.” You continue to work in short sprints, with a single Product Backlog and one Product Owner, but with extra attention to coordination and integration between the feature teams.

‍

Key Features in LeSS

Single Product Backlog & a single Product Owner

Even with multiple teams, everyone works from the same Product Backlog and reports to a single Product Owner. This maintains a single product vision and prevents each team from charting its own course. The teams are feature teams—they can independently deliver end-to-end features, instead of component teams that only handle the front-end or back-end.

‍

LeSS Events

LeSS retains the familiar Scrum events but adds a few additional practices for multiple teams:

1. Sprint Planning part 1: All teams meet with the PO to decide who takes on which backlog items.
2. Sprint Planning part 2: Each team plans the details for the upcoming sprint.
3. Daily Scrum: Still separate per team, but with many dependencies, you can optionally do a Scrum of Scrums.
4. Sprint Review: One integrated review, where all teams demonstrate the product increment as a single whole.
5. Retrospective + Meta-Retro: Each team holds its own retrospective, plus a 'meta-retro' with representatives from each team (and optionally the PO/SMs) to resolve cross-team issues.

‍

LeSS Huge

If one Product Owner can no longer oversee everything, LeSS Huge introduces 'Requirements Areas', each with an Area Product Owner. You split the product into sub-areas, but continue to minimize hierarchy and management layers. This is useful, for example, when working with 10+ teams.

‍

When do you choose LeSS?

LeSS is suitable if:

• You have 2–8 Scrum teams working together on a single product.
• You appreciate that as few additional management layers and roles as possible are added.
• Your teams are capable of forming feature teams (end-to-end responsibility).
• Your product vision is clear enough to work with a single Product Backlog and Product Owner.

If you are larger (e.g., 10+ teams)? Then LeSS Huge might be an option, or another framework like SAFe. In any case, LeSS is a counterpart to SAFe for those who prefer minimal overhead.

‍

Keeping it simple: LeSS in practice

• Start small: LeSS recommends starting with pure Scrum with one team first. Only when that is going well do you gradually add more teams.
• Feature teams: Each team must be able to deliver a fully functional feature, from design to deployment.
• Additional coordination: Consider regular 'multi-team' events, but only if truly necessary. The emphasis remains on self-organization.

‍

Pitfalls and considerations

• One Product Owner, multiple teams: This demands a lot from the PO. Ensure they have enough time and receive support if needed.
• Integration and testing: A Done Increment per sprint means that all work from all teams is integrated and tested together. This requires robust DevOps practices.
• Focus on mindset: LeSS is not just a set of rules, but a philosophy for applying Scrum at scale.

‍

Conclusion

LeSS (Large-Scale Scrum) is a scalable Scrum framework that preserves the simplicity of Scrum, even when deploying multiple teams. With a single Product Backlog and one Product Owner, feature teams, and minimal overhead, you can maintain agility. Do you want to avoid complex structures and management layers, yet have multiple Scrum teams building a product together? Then LeSS might be exactly what you're looking for.