Study CSM Scrum Team Structure and Shared Responsibility: key concepts, common traps, and exam decision cues.
The Scrum Team is a small, cohesive unit responsible for creating value. CSM questions here often test whether you understand that shared responsibility does not mean role ambiguity. Scrum stays lightweight because the team is cross-functional and self-managing, but its accountabilities remain clear.
| Team characteristic | Why it matters |
|---|---|
| cross-functional | the skills needed to create value are available inside the team |
| self-managing | the team decides how to do the work inside Scrum boundaries |
| shared responsibility for the outcome | success is not handed off across siloed roles |
| clear accountabilities | Product Owner, Scrum Master, and Developers still have distinct focuses |
If a team keeps waiting on external specialists for routine work, the stronger Scrum reading is that the team may not yet be cross-functional enough to create a steady usable Increment.
Why does Scrum emphasize a cross-functional Scrum Team?
A. So team members can avoid collaboration and focus only on specialty work B. So the team can create value without depending on constant external handoffs C. So the Scrum Master can assign tasks to every specialist D. So the Product Owner can manage the team’s technical decisions directly
Best answer: B
Why: Cross-functionality helps the Scrum Team deliver usable results without excessive dependency on outside handoffs.
Why the others are weaker: A weakens collaboration, C misreads the Scrum Master role, and D misplaces technical decision-making.