Large-Scale Scrum (LeSS) is a framework for scaling Scrum to larger product development efforts. It is built on the same values, principles, and rules as defined in the Scrum Guide, but applies them to multiple teams working on one product. LeSS emphasizes simplicity, transparency, and learning, aiming to scale Scrum without adding unnecessary complexity or management layers.
Key Characteristics
· Product-centric approach: One product, one Product Backlog, and one Product Owner for all teams.
· Empirical process control: Same pillars as Scrum – transparency, inspection, adaptation – but applied across several teams.
· Downscaling complexity: Instead of adding roles or artifacts, LeSS reduces organizational layers to empower teams.
· Focus on learning and experimentation: Organizations are encouraged to adapt LeSS to their context through iterative learning.
Configurations
· Basic LeSS: Designed for 2 to 8 teams (up to ~50 people).
· LeSS Huge: Designed for more than 8 teams (~50+ people). LeSS Huge introduces additional coordination practices but still avoids extra management roles.
Roles and Structure
· Product Owner: Responsible for maximizing value across all teams.
· Scrum Masters: Work with one or multiple teams, and often with the wider organization.
· Teams (Developers): Cross-functional, self-managing, and responsible for delivering usable Increments each Sprint.
· Additional guidelines for LeSS Huge: Use of Area Product Owners and feature team structures to keep work aligned with the product vision.
Comparison to Other Frameworks
Unlike frameworks that introduce layers of coordination (e.g., program or portfolio levels), LeSS deliberately keeps structures minimalistic. Its philosophy: scaling by removing organizational overhead, not by adding it. The result is greater transparency and faster feedback loops, though it requires strong discipline and a high degree of organizational change.
Advantages
· Simplicity: Keeps processes lean by extending Scrum principles rather than adding new constructs.
· Customer value focus: Work is always tied back to a single Product Backlog.
· Learning at scale: Encourages experimentation and adaptation across multiple teams.
· Reduced overhead: By limiting roles and structures, coordination becomes lightweight.
Challenges
· Organizational resistance: Many companies are more comfortable adding roles/layers than removing them.
· Requires maturity: Success with LeSS demands strong Scrum fundamentals and experienced Scrum Masters.
· Coordination overhead: With many teams, alignment on backlog items and increments can still become challenging without disciplined practices.
Practical Relevance
LeSS is best suited for organizations seeking to scale product development without creating bureaucracy. It works well in contexts where:
· There is a single product vision,
· Teams can be organized as feature teams,
· Leadership is ready to remove silos and traditional project structures.
CALADE Perspective
At CALADE, we see LeSS as a valuable option for organizations that want to scale agility through simplification rather than complication. Our coaches help assess whether LeSS is a fit, guide organizations through the structural changes required, and support leaders and teams in learning how to apply Scrum values consistently across multiple teams.
Related Terms
· Scrum
· SAFe (Scaled Agile Framework)
· Nexus
· Product Owner
· Feature Teams
← back to list