Answering: “How often should Scrum Team membership change?” (PSM I)

Scrum Team membership can change as needed, but the team should expect a short-term drop in productivity when it does. Changes are allowed, and their cost should be considered.

Exam Question

How often should Scrum Team membership change? (choose the best answer)

• A. Every Sprint to promote shared learning.
• B. As needed, while taking into account a short-term reduction in productivity.
• C. Never, because it reduces productivity.
• D. As needed, with no special allowance for changes in productivity.

Correct Answer

B. As needed, while taking into account a short-term reduction in productivity.

Why This Is the Correct Answer

Scrum does not lock team membership, and the Scrum Guide says teams may reorganize into multiple cohesive Scrum Teams when they grow too large. Every change still disrupts how the team works together. New members need to learn the product, the codebase and the team’s habits, and the existing members need to adjust. Teams usually go through a period of lower productivity while they settle. Changing membership when there is a real need, such as missing skills or a new product focus, is fine. Making changes without accounting for the dip leads to false expectations.

Why the Other Options Are Wrong

A. Every Sprint to promote shared learning. Constant rotation keeps the team from ever building stable working relationships. The learning gained does not offset the loss.

C. Never, because it reduces productivity. Teams sometimes need new skills or a new shape. A rule of never would stop useful changes.

D. As needed, with no allowance for productivity changes. This ignores a real effect. Plans and forecasts should reflect the dip after a team change.

Exam Tip

Look for the balanced option. Scrum.org answers rarely say “never” or “every Sprint” about team changes, and favor change with eyes open to its cost.

Key Takeaways

• Team membership may change when there is a real need.
• Every change causes a short-term productivity dip.
• Stable teams are preferred but not mandatory.