Overview
Scrum Team is the fifth SMPC learning-objective area and one of the most heavily studied, because accountability questions appear in many forms. Under the 2020 Scrum Guide, the fundamental unit of Scrum is a small team: one Scrum Master, one Product Owner and Developers. There are no sub-teams or hierarchies. The team is cross-functional, meaning members have all the skills needed to create value each Sprint, and self-managing, meaning it decides internally who does what, when and how. It is typically 10 or fewer people, and the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
The area then examines each accountability: Developers create the Increment, the Product Owner maximizes product value and manages the Product Backlog, and the Scrum Master establishes Scrum and is accountable for the team's effectiveness. CertiProf partner outlines also cover self-managing versus self-organizing teams, agile team characteristics and stakeholders.
How it's tested
Expect who-does-what questions, size and composition questions, and scenarios where someone oversteps an accountability. Some items ask what self-managing means in practice or how stakeholders should influence the product. Watch for options that sound managerial, such as a Scrum Master assigning tasks or a Product Owner estimating work for the Developers.
-
Who is accountable
A responsibility such as ordering the Product Backlog or adhering to the Definition of Done is described, and you pick the accountable member.
-
Team size and structure
A team grows or splits, and you decide what the Guide recommends about size, sub-teams and shared products.
-
Overstepping
A manager, stakeholder or team member takes over a decision that belongs to someone else, and you choose the correct response.
A team of 14 people asks whether to keep one Daily Scrum with everyone. The tempting answer is to keep it because splitting adds coordination. The Guide says teams are typically 10 or fewer, and that larger teams should consider reorganizing into multiple cohesive Scrum Teams focused on the same product, sharing the same Product Goal, Product Backlog and Product Owner. Reorganizing is the better answer.
Topics 5
Official topics from the CertiProf outline, in outline order.
5.1 Scrum Team composition and self-managementSize, structure and the self-managing, cross-functional team.
- What it means
- The Scrum Team consists of one Scrum Master, one Product Owner and Developers. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal, with no sub-teams or hierarchies.
- What to understand
- Teams are typically 10 or fewer people, small enough to stay nimble and large enough to complete significant work in a Sprint. Cross-functional means the team has all skills needed to create value each Sprint. Self-managing means the team decides who does what, when and how; it goes further than the older self-organizing term, which covered how work was done. The whole team is accountable for a valuable, useful Increment every Sprint.
- How it shows up
- Questions test size guidance, the absence of sub-teams and what self-managing allows the team to decide.
- Common confusion
- Believing testers or architects form a separate sub-team or that the team needs a team lead.
5.2 DevelopersPeople committed to creating any aspect of a usable Increment each Sprint.
- What it means
- Developers are the people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint. The term covers anyone doing the work, not only programmers.
- What to understand
- Developers are always accountable for creating a plan for the Sprint (the Sprint Backlog), instilling quality by adhering to a Definition of Done, adapting their plan each day toward the Sprint Goal, and holding each other accountable as professionals. Their specific skills vary with the domain. Developers size work themselves and decide how to turn Product Backlog items into Increments.
- How it shows up
- Expect items asking who owns the Sprint Backlog or who adheres to the Definition of Done.
- Common confusion
- Assuming Developers means software engineers only, or that the Scrum Master builds the Sprint plan.
5.3 Product OwnerAccountable for maximizing the value of the product.
- What it means
- The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team, and for effective Product Backlog management.
- What to understand
- Product Backlog management includes developing and communicating the Product Goal, creating and clearly communicating Product Backlog items, ordering them, and ensuring the backlog is transparent, visible and understood. The Product Owner may delegate the work but stays accountable. The Product Owner is one person, not a committee, and the whole organization must respect their decisions, which are visible in the content and ordering of the Product Backlog and in the inspectable Increment at the Sprint Review. Anyone wanting to change the Product Backlog does so by convincing the Product Owner.
- How it shows up
- Scenarios test single-person authority over the backlog and what the Product Owner can delegate.
- Common confusion
- Thinking a steering committee can act as the Product Owner, or that delegation transfers accountability.
5.4 Scrum MasterAccountable for establishing Scrum and the team's effectiveness.
- What it means
- The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, by helping everyone understand Scrum theory and practice within the Scrum Team and the organization. The Scrum Master is also accountable for the Scrum Team's effectiveness.
- What to understand
- The 2020 Guide describes Scrum Masters as true leaders who serve the Scrum Team and the larger organization. They enable the team to improve its practices within the Scrum framework. Their specific services to the team, the Product Owner and the organization are studied in detail in the Act as Scrum Master area. In this area, focus on what the Scrum Master is not: a project manager, a task assigner or the person who decides product content.
- How it shows up
- Expect items separating the Scrum Master's accountability from Product Owner and Developer decisions.
- Common confusion
- Treating the Scrum Master as the team's manager or as the owner of the Sprint Backlog.
5.5 StakeholdersPeople outside the Scrum Team with an interest in the product.
- What it means
- Stakeholders are people outside the Scrum Team who have an interest in the product, such as customers, users, sponsors and other departments. The Product Owner represents their needs in the Product Backlog.
- What to understand
- Stakeholders collaborate with the Scrum Team most visibly at the Sprint Review, where they inspect the Increment and discuss what to do next. They may be invited to Sprint Planning or Product Backlog refinement when their input helps. Stakeholders do not assign work to Developers directly; requests go through the Product Owner. The Product Owner engages stakeholders, and the Scrum Master facilitates collaboration as requested or needed.
- How it shows up
- Scenarios involve stakeholders bypassing the Product Owner or asking to attend events.
- Common confusion
- Believing stakeholders may attend the Daily Scrum as participants or redirect Developers mid-Sprint.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Scrum Team
One Scrum Master, one Product Owner and Developers.
- Remember
- No sub-teams or hierarchies.
- Tested as
- Composition questions.
- Trap
- Adding a team lead or project manager.
-
10 or fewer
Typical Scrum Team size in the 2020 Guide.
- Remember
- Larger teams should consider splitting into several Scrum Teams on one product.
- Tested as
- Size questions.
- Trap
- Quoting the old 3 to 9 Developers figure as current.
-
Self-managing
Internal decisions on who does what, when and how belong to the team.
- Remember
- Broader than self-organizing.
- Tested as
- Autonomy scenarios.
- Trap
- Expecting a manager to assign tasks.
-
Cross-functional
All skills needed to create value each Sprint.
- Remember
- Skills, not job titles.
- Tested as
- Team design questions.
- Trap
- Assuming every member must have every skill.
-
Developers' accountabilities
Sprint Backlog, Definition of Done, daily adaptation, mutual accountability.
- Remember
- Four items in the Guide.
- Tested as
- Who-owns-what items.
- Trap
- Giving the Sprint Backlog to the Scrum Master.
-
Product Owner is one person
Not a committee.
- Remember
- May represent stakeholder needs in the backlog.
- Tested as
- Authority questions.
- Trap
- Accepting a group as Product Owner.
-
Delegation
The Product Owner may delegate backlog work.
- Remember
- Accountability stays with the Product Owner.
- Tested as
- Delegation scenarios.
- Trap
- Thinking accountability moves too.
-
Scrum Master as true leader
Serves the team and the organization.
- Remember
- Replaced servant-leader wording in 2020.
- Tested as
- Leadership-style questions.
- Trap
- Choosing command-and-control behaviour.
-
Whole-team accountability
The entire Scrum Team is accountable for a valuable Increment each Sprint.
- Remember
- Not just the Developers.
- Tested as
- Shared-accountability items.
- Trap
- Blaming one accountability for the Increment.
-
Stakeholders
People outside the team with a product interest.
- Remember
- Influence through the Product Owner.
- Tested as
- Bypass scenarios.
- Trap
- Letting stakeholders assign work directly.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
The three accountabilities
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Developers | Create the usable Increment | Own the Sprint Backlog and quality via the Definition of Done | Assuming only programmers count |
| Product Owner | Maximize product value | Owns the Product Goal and Product Backlog ordering | Telling Developers how to build items |
| Scrum Master | Establish Scrum and team effectiveness | Serves team, Product Owner and organization | Acting as project manager |
Self-managing vs. self-organizing
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Self-organizing | Team decides how to do its work | 2017 term | Treating it as the 2020 wording |
| Self-managing | Team decides who does what, when and how | 2020 term with wider scope | Assuming no structure or rules apply |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Scrum Master assigns work
- What candidates pick
- The Scrum Master distributing tasks at Sprint Planning.
- Why it looks right
- It looks like efficient coordination.
- Why it's wrong
- Developers are self-managing and create their own plan; the Scrum Master coaches self-management instead.
Clue to watch for Phrases like assigns, allocates or decides who.
-
Product Owner committee
- What candidates pick
- A group of managers acting as Product Owner.
- Why it looks right
- Large products have many stakeholders.
- Why it's wrong
- The Product Owner is one person; stakeholder needs can be represented in the Product Backlog through that person.
Clue to watch for Mention of a board or steering group.
-
Sub-team for testing
- What candidates pick
- A separate QA team inside the Scrum Team.
- Why it looks right
- Specialist testing is common.
- Why it's wrong
- The Guide says there are no sub-teams; testing skills belong to cross-functional Developers.
Clue to watch for Words like hand off to QA.
-
Delegation removes accountability
- What candidates pick
- The business analyst becomes accountable for the backlog.
- Why it looks right
- They do the daily backlog work.
- Why it's wrong
- The Product Owner may delegate but remains accountable for Product Backlog management.
Clue to watch for A delegate making backlog changes.
-
Keep the large team
- What candidates pick
- A team of 15 keeping one Scrum Team.
- Why it looks right
- Avoids coordination overhead.
- Why it's wrong
- The Guide recommends that large teams consider reorganizing into multiple cohesive Scrum Teams sharing one Product Goal, backlog and Product Owner.
Clue to watch for Team sizes well above 10.
-
Stakeholder redirects work
- What candidates pick
- Developers accept a stakeholder's direct request mid-Sprint.
- Why it looks right
- The stakeholder is senior and urgent.
- Why it's wrong
- Requests go to the Product Owner, who decides ordering; the Sprint Goal is protected.
Clue to watch for A stakeholder approaching a Developer.
Answer framework
Use these steps when a question asks who should act or decide within the Scrum Team.
- Decide whether the decision concerns what to build and in which order, how to build it, or how well Scrum is working for the team.
- Assign what and order to the Product Owner, who manages the Product Goal and the Product Backlog and may delegate but remains accountable.
- Assign how, the Sprint plan and quality against the Definition of Done to the Developers, who are self-managing and hold each other accountable.
- Assign process effectiveness, coaching and impediment removal to the Scrum Master, who serves as a true leader rather than a manager.
- Check structure last: one team without sub-teams, typically 10 or fewer, with stakeholders influencing through the Product Owner rather than directly.
Practice question
Want more like this? The SMPC practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the Scrum Team section of the 2020 Scrum Guide and build a three-column table: Developers, Product Owner and Scrum Master. Copy every responsibility the Guide lists under each one, then add a row at the bottom for what each accountability is not, such as the Scrum Master not being a project manager. This single table answers most items in this area.
Next, learn the structural rules: no sub-teams, typically 10 or fewer people, one Product Owner, and multiple teams on one product sharing a Product Goal, Product Backlog and Product Owner. Practise saying why each rule exists in terms of communication, focus and accountability.
Then work through overstep scenarios. Write short cases where a manager assigns tasks, a stakeholder approaches a Developer, or a Scrum Master edits the Product Backlog, and decide who should act and how. Because this area carries a large share of the content, consider giving it more time than the introductory areas and returning to it after studying the events.
FAQ
How much weight does the Scrum Team area carry on the SMPC?
CertiProf does not publish a weight for the Scrum Team area. Accountability questions are common on Scrum exams, so this guide plans for about six of the 40 questions as an editorial estimate.
How big should a Scrum Team be?
The 2020 Scrum Guide says typically 10 or fewer people. Larger groups should consider forming multiple Scrum Teams that share one Product Goal, Product Backlog and Product Owner.
Is the Scrum Master the team's manager?
No. The Scrum Master is accountable for establishing Scrum and for the team's effectiveness, serving as a true leader, not as a manager who assigns work.
Can the Product Owner be a committee?
No. The Product Owner is one person. Others can influence the Product Backlog by convincing that person.
Who owns the Sprint Backlog?
The Developers. They create and adapt the plan for the Sprint.
Are testers part of the Developers?
Yes. Developers means anyone doing the work to create the Increment, including testers, designers and analysts.
Can stakeholders attend Scrum events?
Stakeholders are key participants at the Sprint Review and may be invited to other events for input. The Daily Scrum is for the Developers.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 5 knowledge
Work through a short SMPC set on accountabilities, team size and self-management to confirm you can assign every decision correctly.