The Story of LeSS
summary
A lightweight scaling approach born from years of experiments at Nokia and other large product groups, LeSS prescribes a few pages of rules and ten principles and scales Scrum to small and very large efforts by reorganizing people into feature teams, enforcing continuous integration/daily builds, and keeping one product backlog and one product owner. Teams co-plan in a shared room, produce one integrated shippable increment each sprint, and report fewer asynchronous handoffs—applied successfully from 2–8 teams (Basic LeSS) up into 8+ teams (LeSS Huge).
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:15Scrum and LeSS overview
- 3:48Scrum and team-based dev
- 8:12LeSS history and evolution
- 10:03Traffic analogy and industry trends
- 13:02Nokia’s agile transformation
- 19:58Microsoft’s LeSS influence
- 21:46Feature teams in scaling
- 26:28Component vs feature teams demo
- 30:18Moving to Singapore and LeSS books
- 33:17Feedback, Shu Ha Ri, and rules
- 36:11LeSS framework structure
- 39:44More with less principle
- 45:38Summary
related talks
50mThe Story of LeSS
52mThe Story of LESS
42mLarge Scale Scrum – More with LeSS
20mScaling a Scrum Team: Three-Month Retrospective and Challenges of Introducing LeSS
21m600 Days of LeSS: A Practice Chronicle
36mLeSS is More: The Automotive Journey
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!