Splitting the Team
summary
Two case studies compare outcomes when splitting a team: one split of 7 developers is announced with two weeks’ notice and imposed structure, causes anger, takes about two months to regain predictability and leaves manager trust permanently damaged; another split of 11 developers uses a problem statement, measurable goals and success criteria, four boundary rules, and three months prep with team self-organization, yields two smaller teams that immediately work more predictably and efficiently.
AI-written summary · about
chapters (10)
- 0:00Team splitting challenges
- 1:31Why split a team
- 2:55A-Team split case study
- 5:49Rushed splits consequences
- 6:11B-Team split case study
- 9:43Collaborative restructuring
- 11:12Differences in approaches
- 12:57Team input benefits
- 13:42Preparation steps
- 15:31Conclusion & Q&A
related talks
45mCoaching Teams Through Team Change
43mScaling Yourself for Managing Distributed Teams...
33mTools over Processes over People... Or Not?
33mBuilding Sustainable Teams to Handle Uncertainty
41mDynamic Reteaming at Fast Changing Companies
46mDynamic Reteaming
58mDevs fight your Battle! A Pledge for cross-functional Teams
01h 37mDynamic Reteaming, The Art and Wisdom of Changing Teams