Which two ways of creating Scrum Teams are consistent with Scrum's values? (choose the best two answers)

Question

Options

• ABring all the people together and let them organize into Scrum Teams.
• BManagers personally re-assign current subordinates to new teams.
• CExisting teams propose how they would like to go about organizing into the new
• DManagers collaborate to assign individuals to specific teams.
• EThe Chief Product Owner determines the new team structures and assignments.

• A
  72% (26)
• B
  6% (2)
• D
  14% (5)
• E
  8% (3)

Explanation

A and C are correct because Scrum is grounded in the values of self-organization, respect, and commitment - teams are most effective when they have agency in how they form. Option A lets people self-organize naturally, and Option C respects the knowledge existing teams have about their own dynamics by letting them propose their own structure. Both approaches treat developers as capable professionals rather than resources to be managed.

Why the distractors are wrong:

• B & D: Both involve managers making unilateral or collaborative assignments - this imposes structure top-down, violating the Scrum value of self-organization and the principle that teams choose how they work.
• E: A Chief Product Owner role doesn't exist in Scrum (only a single Product Owner per product), and even if it did, dictating team structure is a management override, not self-organization.

Memory tip: Ask yourself "Who decides?" - in Scrum, the team decides. Any answer where a manager, executive, or external role assigns people to teams is wrong. Look for answers where people choose or propose their own arrangements.

No community discussion yet for this question.