When Rotating Teams as a Tactic to Shorten Lead Time Turned Out to Be LeSS Mob Programming
summary
A LeSS product group rotated developers each sprint so most people join one rotating “focus team” while keeping fixed ops and PBI teams, and added events like epic refinement, team formation, and a pre-planning sprint ritual. This approach produced measurable reductions in epic lead time—three epics finished in six sprints—by reducing reviews and handoffs as skills moved with team members, while creating trade-offs such as harder-to-sustain team retrospectives and less-clear paths for individual growth.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 4:15Team challenges
- 11:02Origins of dynamic teaming
- 15:08Fluid team structure
- 21:48Results and changes
- 29:47Why fluid teams worked
- 37:11Implementation
- 41:03Key takeaways
- 45:19Q&A
related talks
08mLightning Talk: A Tale of Two Spirits
46mDynamic Reteaming
33mBuilding Sustainable Teams to Handle Uncertainty
35mTeam transformation to accelerate value delivery
18mAgile leadership and technical mastery, a harmonious alliance
35mBuilding and Growing an Agile Team
52mToo many cooks! Supporting augmented teams without getting salty
47mDynamic Reteaming at fast Growing Companies