LeSS
LeSS starts from a premise that sets it apart from other scaling frameworks: organizational complexity is not the solution to the problem of scaling; it is part of the problem. More structure, more roles, and more events generate more coordination but not necessarily more value. LeSS seeks to preserve the properties of team-level Scrum (self-management, product focus, and continuous improvement) when scaling.
Two versions of the framework
LeSS (Basic)
For up to eight Scrum Teams working on the same product. The structure is recognizably Scrum:
- A single Product Owner with vision and authority over the whole product.
- A single Product Backlog shared by all teams.
- A single Definition of Done that applies to the integrated increment of all teams.
- Sprints synchronized across all teams.
- A single integrated increment at the end of each sprint.
Additional events are minimal: a Sprint Planning with representatives from all teams to coordinate dependencies (before each team's individual planning) and an overall retrospective at the end of each sprint.
LeSS Huge
For more than eight teams. It introduces the concept of the Requirement Area: groupings of parts of the product by area of user value. Each area has an Area Product Owner who works under the Product Owner of the whole product.
Core principles
LeSS doesn't add structure; it simplifies. Its most relevant principles are:
- More with LeSS: more value with less: fewer roles, fewer artifacts, fewer special processes. Simplicity is a deliberate goal.
- Technical Scrum in the teams: each team does full Scrum. If Scrum does not work in the teams, scaling adds nothing.
- Whole-product focus: teams work on the whole product, not on components or technical layers. The goal is for any team to be able to work on any part of the backlog.
- Experimentation and continuous improvement: LeSS is a framework, not a prescribed process. Teams experiment and adapt.
LeSS vs. Other Scaling Frameworks
| LeSS | Nexus | SAFe | |
|---|---|---|---|
| Target teams | 2-8 (LeSS) / 8+ (LeSS Huge) | 3-9 | 50-125+ people |
| Philosophy | Minimal additional structure | Technical integration | Comprehensive |
| New roles | None (in basic LeSS) | Nexus Integration Team | Many |
| PO | One for the whole product | One for the whole product | Product Manager + POs |
Common mistake
Adopting LeSS without teams that are mature in technical Scrum. LeSS assumes that individual teams practice Scrum fluently. If the teams have not mastered their own level (self-management, the Definition of Done, delivering integrated increments), adding LeSS coordination amplifies the problems instead of solving them. Larman's maxim is explicit: first make sure each team works well; then scale.
References
- Larman, Craig; Vodde, Bas. (2016). Large-Scale Scrum: More with LeSS. Addison-Wesley.
- LeSS.works — Official website.
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.