Loading content
Large-Scale Scrum (LeSS) is a structured approach to implement Scrum across multiple teams within large organizations. It promotes collaboration and maximizes value through agile practices on both social and technical levels.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Large-Scale Scrum (LeSS) is a framework for aligning multiple Scrum teams around one product. It scales through shared product ownership, integrated work, and as few additional roles and layers as possible.
Bas Vodde and Craig Larman developed LeSS from experience with large product development and documented it publicly from 2008 onward. They present it as applying Scrum and Lean principles at the scale of multiple teams.
Picture several teams working on one product map: one product backlog, one Product Owner, and one shared Sprint Goal connect their work. Cross-team planning and a common Definition of Done produce an integrated increment; organizational dependencies become visible and can be reduced.
Teams share product ownership and align decisions around the same customer value.
All teams' results are integrated, tested, and treated as one product.
Teams coordinate directly where possible instead of adding hierarchies and handoffs.
LeSS helps organizations consider how several Scrum teams can work on one product. It requires real product boundaries and technical integration; adding teams without simplifying structure increases coordination.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.