Understanding LeSS: Origin, Principles, Framework, and Implementation Strategies

Preface

The author recounts first encountering System Thinking and LeSS in 2019, then revisiting the framework two years later to deepen understanding and reinforce learning through writing.

1. Origin of LeSS

LeSS (Large‑Scale Scrum) was created by Craig Larman and Bas Vodde around 2005 during Nokia Siemens Networks' transition to agile. After experimenting with over 600 trials, they distilled their findings into the LeSS methodology and published two books.

2. LeSS Full Diagram

The full LeSS diagram consists of four layers: experiments, guidelines (about 50), the framework itself, and ten underlying principles.

3. LeSS Principles

The ten principles are grouped into three categories: (1) Scrum‑related (large‑scale Scrum is still Scrum, transparency, empirical process control), (2) LeSS‑specific (less is more, whole‑product focus, customer‑centricity), and (3) Meta‑principles (queue theory, systems thinking, lean thinking, continuous improvement).

4. LeSS Framework

LeSS defines two variants based on team size: the LeSS framework for 2‑8 Scrum teams and LeSS Huge for more than eight teams. Both share key points: a single Product Owner, one Product Backlog, a common Sprint, and one integrated product increment.

In the standard LeSS framework, multiple Scrum teams share one Product Backlog, one Sprint cadence, and one Sprint Review. Planning is split into a joint Sprint Planning 1 (all teams) and individual Sprint Planning 2 for each team. Each team maintains its own Sprint Backlog, daily stand‑ups remain team‑level, and retrospectives are conducted both at team and whole‑system levels.

LeSS Huge introduces Area Product Owners (APOs) for larger requirement areas (4‑8 teams each) while retaining a single overall Product Owner and Product Backlog. Views of the backlog can be filtered per area, but the underlying backlog remains unified.

5. LeSS Launch Strategy

The official launch steps include training everyone, defining the product and definition of done, building well‑structured teams, ensuring only the Product Owner provides work, and removing the project manager from the team. A practical, field‑tested approach adds a one‑day team training, a 1‑3 month pilot selection period, preparation of the pilot (training, product list, technical setup), and a two‑day “flip” phase to start the LeSS sprint rhythm.

6. LeSS vs. SAFe

LeSS suits flat, lightweight organizations that prefer minimal role addition, while SAFe adds hierarchical layers and roles, making it more appropriate for larger, more bureaucratic enterprises. The article advises readers to consider their own context when choosing between the two scaling frameworks.