Laws of Software Engineering · Pattern
Pattern
Dynamic Reteaming
Teams change shape over time. People join, leave, split, and merge. Treat reteaming as a normal practice.
How to use it. Plan for the next reteam before the current team is fully formed. Prefer small, frequent changes (one person rotates) to large, infrequent ones (a reorganisation). A team that survives a deliberate reteam is more resilient than one held together only by stability.
How it gets misused. Used to justify constant churn. Reteaming has costs: onboarding, knowledge transfer, and lost context. The discipline is to make changes deliberately and at the right time.
Related
-
Pattern
Team Topologies
Four kinds of team (working on a stream of value, building a platform, helping others, or owning something complicated). Three ways teams can interact (working together, providing a service, or helping someone learn).
- Principle Hackman's Five Conditions for Effective Teams Teams perform when they are real teams, with compelling direction, enabling structures, supportive context, and expert coaching.
Clusters
- The Team Design cluster - How to organise people for software work.