LeSS Huge: Scaling Scrum Beyond Eight Teams
LeSS Huge is a framework for applying Scrum when over eight teams work on one product, organizing them into "Requirement Areas." It’s for massive projects, like autonomous driving systems, where dozens of teams must coordinate.
The mental model
LeSS Huge is not just 'more Scrum.' It's a framework for descaling organizational complexity. When you have more than eight teams working on a single product, a single backlog and single Product Owner become a bottleneck. LeSS Huge addresses this by creating multiple smaller 'LeSS' implementations within a larger whole, each focused on a major area of customer requirements. The goal is to maintain the core LeSS principles—simplifying structure, amplifying learning, and technical excellence—at a massive scale.
How it works
LeSS Huge is designed for organizations with more than eight Scrum teams. The key structural addition is the 'Requirement Area.' The product is divided into major customer-centric areas, and teams are grouped into these areas. Each Requirement Area has an 'Area Product Owner' who manages a specific Area Product Backlog, which is a filtered view of the overall Product Backlog managed by the one, overall Product Owner. All teams still work in a synchronized cadence, participating in one overall Sprint Review and Retrospective, but much of the planning and refinement happens within their Requirement Area.
When to use it
Use LeSS Huge only when you have more than eight teams working on a single, end-to-end customer product. It is intended for massive development efforts where the scale of coordination makes the basic LeSS framework (for 2-8 teams) impractical. Examples from the field include developing autonomous driving platforms, modernizing core banking systems, or building complex logistics and port management software.
When not to use it
Do not use LeSS Huge if you have eight or fewer teams; the simpler LeSS framework is sufficient. Avoid it if your organization is not prepared for a radical redesign. It requires breaking down functional silos, empowering teams, and changing the role of management from director to coach. It will also fail without strong technical excellence; practices like continuous integration and test automation are non-negotiable for managing the dependencies between dozens of teams.
One canonical example
A large automotive company is building a unified autonomous driving platform with 30 teams. A single backlog is chaos. They adopt LeSS Huge and create four Requirement Areas: 'Sensor Fusion,' 'Path Planning,' 'Driver Monitoring,' and 'In-Car Experience.' Each area has an Area Product Owner and 7-8 teams. This structure allows teams to focus on a cohesive part of the customer problem while still integrating their work into a single, shippable product increment every Sprint.
Interview question
In LeSS Huge, what is the fundamental reason for organizing teams into 'Requirement Areas'?
- a.To decentralize product ownership and backlog management for specific customer-centric parts of a single product, addressing scale beyond eight teams.Correct
- b.To establish independent development streams that can operate on different Sprint cadences and release cycles.
- c.To allow each individual Scrum team to manage its own distinct product backlog and Product Owner.
- d.To enable the development of multiple, unrelated products concurrently within the same large organization.
Why? this is the answer
LeSS Huge introduces Requirement Areas to manage the complexity of a single product's backlog when more than eight teams are involved, by decentralizing ownership for customer-centric parts. Option C is incorrect because Requirement Areas, not individual teams, get Area Product Owners, and their backlogs are filtered views of the overall product backlog, not distinct ones.
Just read this? Test yourself on what you have been reading.
Read the original → less.works
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles