Scaling a Scrum Team: Three-Month Retrospective and Challenges of Introducing LeSS
summary
Kaonavi merged two feature teams using LeSS to scale their Scrum setup; they report PO capacity became a bottleneck so they created unit-PO roles tracked in Trello and used delegation poker to delegate work. Quality control began writing acceptance criteria to speed and shift-left testing but criteria have become overly implementation-focused; remaining issues include knowledge gaps, weak team cohesion, and unfinished experiments like all-hands overalls.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:16Reasons for scaling
- 5:37Why LeSS framework
- 7:56LeSS challenges
- 8:17PO workload issues
- 11:26Unit PO experiment
- 12:48Knowledge gap
- 14:56Team cohesion issues
- 17:01Future plans
- 18:48Summary
