Answering: “What tactic should a Scrum Team use to divide a group of 100 people into multiple Scrum Teams?” (PSD)

Ask the people to divide themselves into teams. Self-organizing into Scrum Teams beats having the Product Owner or anyone else assign them, and organizing by technical layer creates component teams.

Exam Question

What tactic should a Scrum Team use to divide a group of 100 people into multiple Scrum Teams?
(choose the best answer)
A. Create teams based on their skills across multiple layers (such as database, UI, etc).
B. Ask the Product Owner to assign the people to teams.
C. Ask the people to divide themselves into teams.

Correct Answer

C. Ask the people to divide themselves into teams.

Why This Is the Correct Answer

Scrum Teams are self-managing, which the Scrum Guide explains as deciding internally who does what, when and how. That principle works well for team formation too. When 100 people split themselves up, they can use what they know about each other’s skills to build teams that are cross-functional, so each team has “all the skills necessary to create value each Sprint.” Guidance such as product areas or a team size of 10 or fewer can be given as constraints, but the choice stays with the people. Teams formed this way usually show stronger commitment and need less time to start working well.

Why the Other Options Are Wrong

A. Create teams based on technical layers such as database or UI. Layer-based teams are component teams. They cannot deliver a Done Increment alone and create handoffs and dependencies.

B. Ask the Product Owner to assign people. The Product Owner manages product value, not people. Assigning team members is not part of their accountability.

Exam Tip

When splitting a large group into Scrum Teams, the expected answer is self-organization. Watch for options that sound efficient but put one person in charge of the split.

Key Takeaways

• Let people form their own teams within clear constraints.
• Each team should be cross-functional.
• Component teams by layer create dependencies.