The Story of LeSS
summary
LeSS presents a minimal scaling prescription: one Product Owner and one backlog for the whole product, teams organized as feature teams and daily builds with heavy test automation and CI. Originating from experiments across ~20 product groups, it scales to dozens of teams (worked up to ~50 teams) and produced long case studies of 500–600 and 3,000 person case studies where organizations move from component teams to feature teams, remove a management layer, and report successful outcomes. LeSS pairs three pages of mandatory rules with 1,000 pages of experiments and practical guides.
AI-written summary · about
chapters (10)
- 0:00Introduction and agenda
- 1:48The essence of Scrum
- 5:07Overview of LeSS
- 7:40Origin story and purpose
- 13:03Scaling challenges at Nokia
- 21:15Feature teams vs components
- 30:19Learning and experimentation
- 36:32The LeSS framework complete
- 39:22The 'More with LeSS' principle
- 44:23Q&A and concluding remarks
related talks
50mThe Story of LeSS
52mThe Story of LESS
21m600 Days of LeSS: A Practice Chronicle
20mScaling a Scrum Team: Three-Month Retrospective and Challenges of Introducing LeSS
36mLeSS is More: The Automotive Journey
42mLarge Scale Scrum – More with LeSS
21mScaling Scrum in Fully Remote Work — Challenges from 3 People to 30 People and 6 Teams over Three Years and Applying Scrum@Scale and LeSS Practices
56mScaling Up!