🧱 LeSS
Large‑Scale Scrum (LeSS) is a lightweight, Agile scaling framework that extends one‑team Scrum to multiple teams working together on a single product. It keeps Scrum simple, removes organizational complexity, and focuses on whole‑product delivery, not team silos.
The key idea: LeSS is Scrum, scaled — not Scrum plus extra layers.
What LeSS is?
Section titled “What LeSS is?”LeSS is an organizational design system for large product development efforts. It applies the principles, roles, events, and artifacts of Scrum across many teams while minimizing additional processes and roles.
Two variants exist:
- LeSS — for 2–8 teams (up to ~50–60 people)
- LeSS Huge — for hundreds to thousands of people working on one product
Core principles of LeSS
Section titled “Core principles of LeSS”LeSS is built on principles that preserve agility at scale:
- Large‑Scale Scrum is Scrum — not a new method, but Scrum applied to many teams
- Empirical process control — inspect & adapt product, processes, and organizational design
- Transparency — shared Definition of Done, shared Sprint, shared product
- More with less — fewer roles, fewer artifacts, less overhead
- Whole‑product focus — one Product Backlog, one Product Owner, one shippable increment
- Customer‑centricity — reduce cycle time, increase feedback loops
- Systems thinking — optimize the whole system, not individual team efficiency
How LeSS works (operating model)
Section titled “How LeSS works (operating model)”LeSS keeps Scrum’s structure but applies it across multiple teams:
One product, one Sprint
Section titled “One product, one Sprint”All teams:
- Share one Product Backlog
- Share one Product Owner
- Deliver one shippable product increment every Sprint
- Work in one common Sprint
Cross‑functional feature teams
Section titled “Cross‑functional feature teams”Teams are:
- Cross‑functional
- Full‑stack
- Responsible for end‑to‑end features
- Not organized by component or specialty
Events at scale
Section titled “Events at scale”LeSS modifies Scrum events slightly:
- Sprint Planning Part 1 — PO + representatives from all teams coordinate backlog selection
- Sprint Planning Part 2 — each team plans its work independently
- Daily Scrum — per team, but open for cross‑team observation
- Overall Product Backlog Refinement — optional meeting for alignment across teams
Coordination mechanisms
Section titled “Coordination mechanisms”LeSS avoids extra roles and instead uses lightweight coordination patterns:
- “Just Talk”
- Code communication
- Travelers (team members temporarily joining other teams)
- Communities of Practice
Why organizations choose LeSS
Section titled “Why organizations choose LeSS”LeSS is designed for companies that want:
- Simplicity at scale
- Low overhead compared to frameworks like SAFe
- Whole‑product focus instead of team‑level optimization
- Fast learning cycles across many teams
- Customer‑centric delivery
It is especially effective when:
- You have multiple Scrum teams building one product
- You want to avoid heavy governance layers
- You value continuous improvement and organizational transparency
LeSS vs SAFe vs Scrum
Section titled “LeSS vs SAFe vs Scrum”| Framework | Scale | Philosophy | Best for |
|---|---|---|---|
| Scrum | 1 team | Lightweight, empirical | Small product teams |
| LeSS | 2–8 teams (LeSS), 8+ (Huge) | Minimal roles, whole‑product focus | Companies wanting simple scaling |
| SAFe | Enterprise | Prescriptive, structured | Large enterprises with governance needs |