PSM-I · Question #132
How often should Development Team membership change?
The correct answer is A. As needed, while taking into account a short term reduction in productivity. Development Team membership should change only as needed, and when it does, the team should acknowledge that there will be a short-term reduction in productivity. Changing team composition disrupts the forming-norming-storming-performing cycle and team cohesion. Scrum values…
Question
How often should Development Team membership change?
Options
- AAs needed, while taking into account a short term reduction in productivity.
- BNever, because it reduces productivity.
- CAs needed, with no special allowance for changes in productivity.
- DEvery Sprint to promote shared learning.
How the community answered
(17 responses)- A88% (15)
- C6% (1)
- D6% (1)
Explanation
Development Team membership should change only as needed, and when it does, the team should acknowledge that there will be a short-term reduction in productivity. Changing team composition disrupts the forming-norming-storming-performing cycle and team cohesion. Scrum values stability of the team for sustained velocity and quality. However, 'never' (Option B) is too absolute - changes can be necessary. Changing every Sprint (D) is an anti-pattern that prevents teams from ever reaching high performance.
Topics
Community Discussion
No community discussion yet for this question.