Ok, I flipped to LeSS and now what?
summary
A cross-functional pilot proves LeSS can work so the company flips 60% of staff and forms eight product teams while keeping job safety; teams adopt two-week sprints after an unsustainable one-week experiment and see two sprints per PBI with one-sprint completion rising from ~30% to ~40%. Early problems: unclear decision ownership, chaotic learning, and legacy ops — millions of lines of Clipper codebase with six-letter variables. Remediations: decision-delegation workshops, TDD and mob programming consultants, a developer-experience community, and hiring an external modernization partner.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:48Why we flipped to LeSS
- 3:16Designing the LeSS transformation
- 6:15Self-designing teams workshop
- 9:49Forming eight teams
- 10:10First checkpoint: 3 months
- 14:35Actions after first checkpoint
- 15:15Second checkpoint: 6 months
- 21:23Engineering practices investment
- 23:12Fixing product development chaos
- 24:40Legacy code modernization
- 26:25Nine months after flip
- 27:55Key takeaways
- 29:01Q&A