The Scrum Team
Structure and Accountabilities
A Scrum Team is a small, cross-functional, self-managing unit of typically ten or fewer people, containing one Scrum Master, one Product Owner, and Developers. The Product Owner maximizes product value and owns effective Product Backlog management, including ordering and clear communication of items. The Scrum Master is accountable for the team's effectiveness and for establishing Scrum as defined. Developers create the increment and hold all skills needed to do so.
Self-Management and Cross-Functionality
Self-managing means the team decides who does what, when, and how; cross-functional means the team collectively has the skills to deliver a valuable increment each Sprint. Traps appear when a question implies a functional manager assigns tasks, or that the Product Owner directs how Developers work. The Product Owner says what and why; Developers decide how and how much.
One Team, No Sub-Teams
There are no "dev team" or "QA team" sub-accountabilities inside the Scrum Team. Candidates often accept answers that create hierarchies within the team. Also note the whole team attends the Daily Scrum if Developers find it useful, though Developers own it.
Worked rule of thumb
For any "who decides?" question, map it: value and ordering → Product Owner; process, facilitation, and coaching → Scrum Master; technical approach and Sprint work selection → Developers. If an answer gives decision rights to someone outside these three, it is usually wrong.
Exam traps
- The Scrum Master is not a project manager, secretary, or task assigner.
- The Product Owner may delegate backlog work but remains accountable.
- A team of one or a team split by specialty conflicts with Scrum's intent.