Agile guide · Scaling Agile
What Is Large-Scale Scrum (LeSS)? Principles and Structure
Large-Scale Scrum (LeSS) applies Scrum to many teams working on one product while adding as little extra structure as possible. Its motto is "more with LeSS".
Key takeaways
- LeSS scales Scrum with one Product Owner, one backlog and one sprint for many teams.
- LeSS covers two to eight teams; LeSS Huge goes further.
- It deliberately adds as little structure as possible.
Origins
LeSS was developed by Craig Larman and Bas Vodde from the mid-2000s, based on experience scaling Scrum in large product development organisations.
Core structure
- One product, defined broadly from the customer's point of view.
- One Product Owner and one Product Backlog for all teams.
- One Definition of Done shared by all teams.
- One shared Sprint: all teams start and end together and deliver one integrated increment.
- Feature teams: cross-functional teams that deliver complete customer features, rather than component teams.
LeSS and LeSS Huge
| Framework | Size | Extra structure |
|---|---|---|
| LeSS | Two to eight teams | Minimal: shared events added to Scrum |
| LeSS Huge | More than eight teams | Requirement areas, each with an Area Product Owner |
LeSS events
- Sprint Planning One: representatives of all teams and the Product Owner decide which items each team will take.
- Sprint Planning Two: each team, or several teams together, plans how to do its work.
- Daily Scrum for each team, plus informal coordination between teams.
- Overall product backlog refinement with several teams.
- One Sprint Review for the whole product, often in a bazaar style.
- Team retrospectives followed by an Overall Retrospective focused on the whole system.
Principles
- Large-scale Scrum is still Scrum.
- Systems thinking and lean thinking.
- Whole-product focus and customer-centric organisation.
- Empirical process control and transparency.
- Continuous improvement towards perfection.
- More with less: avoid adding roles, artifacts and processes unless truly needed.
LeSS vs SAFe
| LeSS | SAFe | |
|---|---|---|
| Philosophy | Minimal additions to Scrum | Comprehensive framework |
| Organisational change | Encourages deep restructuring | Fits alongside existing structures |
| Roles | Few new roles | Several new roles and layers |
| Best for | Organisations willing to simplify | Large enterprises needing structure |
Frequently asked questions
Is LeSS a certification?
LeSS is a framework; The LeSS Company offers training and certification for practitioners.
Can LeSS work with non-software products?
Yes, although most published experience comes from software and systems products.
What is LeSS in Agile?
Large-Scale Scrum, a framework for applying Scrum to many teams working on one product with one Product Owner, one Product Backlog and one shared Sprint.
Who created LeSS?
Craig Larman and Bas Vodde, from the mid-2000s, based on experience scaling Scrum in large product development organisations.
How many teams can use LeSS?
Basic LeSS is designed for two to eight teams. LeSS Huge is for more than eight teams.
What is LeSS Huge?
The version of LeSS for more than eight teams, which divides the product into requirement areas, each with an Area Product Owner.
What are feature teams in LeSS?
Cross-functional teams that deliver complete customer features end to end, rather than component teams that each own one technical layer.
What is Sprint Planning One and Two in LeSS?
In Sprint Planning One, team representatives and the Product Owner decide which items each team takes. In Sprint Planning Two, each team plans how to do its work.
What is the difference between LeSS and SAFe?
LeSS adds minimal structure to Scrum and encourages deep organisational change; SAFe provides a comprehensive framework with additional roles, events and layers.
Does LeSS have a Scrum Master?
Yes. Each Scrum Master usually supports one to three teams and focuses on the whole system as well as the teams.
What is an Overall Retrospective in LeSS?
A retrospective held after the team retrospectives, in which Product Owner, Scrum Masters and team representatives improve the whole system.