Overview
Scrum.org lists a single focus area for this competency on the PSPO I page: Self-Managing Teams. Under the Scrum Guide, a Scrum Team decides internally who does what, when and how. For a Product Owner that sets a clear boundary. The Product Owner shapes the direction through the Product Goal, clear Product Backlog items and the ordering, and the Developers decide how much they can take into a Sprint and how to build it.
Candidates must understand what self-management changes about the Product Owner's daily behavior: no task assignment, no capacity targets imposed on the Developers, and no bypassing them to direct individuals. It also covers how the Product Owner supports a team's growth by offering transparency, context and fast answers. The competency links to the framework rules on Developer accountabilities and to stakeholder management, where the Product Owner shields the team from conflicting demands.
How it's tested
Expect scenarios where a Product Owner, manager or stakeholder tries to influence how the Developers work, and you choose the response consistent with self-management. Options often differ only in who makes the call. The reasoning is to separate influence through goals, ordering and information from control over people, tasks and methods.
-
Influence or control
The Product Owner wants something from the Developers. The right option uses the Product Goal, ordering or a conversation; the wrong ones assign, mandate or override.
-
Who decides inside the team
A question asks who chooses an approach, splits tasks or picks how much work enters a Sprint. The Developers decide as a self-managing group.
-
Supporting growth
A struggling team is described and you pick how the Product Owner helps, usually by improving clarity of goals and items, or by working with the Scrum Master, not by taking over.
A Product Owner sees that one senior Developer is slow on a high-value item and wants to move it to another person. Ask who decides who does what: the self-managing team. Then ask what the Product Owner can legitimately do: make the item's value and urgency transparent and raise the concern with the Developers. The answer is to share the context and let the Developers reorganize, not to reassign the work.
Focus areas 1
Official focus areas from the Scrum.org outline, in outline order.
2.1 Self-Managing TeamsHow a self-managing Scrum Team decides who does what, when and how, and how the Product Owner works with it.
- What it means
- Self-managing means the Scrum Team internally decides who does what, when and how, without direction from outside the team. Combined with cross-functionality, it lets the team turn ordered Product Backlog items into a Done Increment each Sprint.
- What to understand
- The Product Owner steers through the Product Goal, clear and ordered Product Backlog items and active collaboration, not through tasks or quotas. The Developers forecast what they can complete and hold each other accountable as professionals. If a team grows too large, it can reorganize into several cohesive Scrum Teams that share one Product Goal, Product Backlog and Product Owner.
- How it shows up
- A scenario describes a Product Owner or manager trying to assign people, set required output or impose a technique, and asks for the most appropriate response.
- Common confusion
- Candidates confuse self-managing with unmanaged. The team still works within Scrum's rules, the Sprint Goal and the Definition of Done; it simply decides internally how to meet them.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Self-managing
A self-managing Scrum Team decides internally who does what, when and how; the 2020 Scrum Guide replaced the earlier term self-organizing with self-managing.
- Remember
- The decision rights are who, what (within the Sprint) and how, held inside the team rather than by an outside manager.
- Tested as
- Most questions in this focus area test whether an option takes one of those decisions away from the team.
- Trap
- Reading self-managing as permission to ignore the Sprint Goal, the Definition of Done or the Product Owner's ordering.
-
Cross-functional
A cross-functional team holds, between its members, every skill required to produce a Done Increment each Sprint without handing work to other groups.
- Remember
- Cross-functionality is about the team as a whole, not every person being able to do every job.
- Tested as
- Dependency scenarios test whether the team can produce a Done Increment alone.
- Trap
- Thinking cross-functional means removing specialists or that each Developer must be a generalist.
-
Developer forecasts
The Developers select how many Product Backlog items they can take into the Sprint, using past performance, capacity and their Definition of Done.
- Remember
- The Product Owner can explain value and discuss trade-offs but cannot set the number of items.
- Tested as
- Sprint Planning scenarios where the Product Owner wants more scope.
- Trap
- Choosing an option where the Product Owner commits the team to a stakeholder deadline without the Developers.
-
Product Owner influence
The Product Owner's levers are the Product Goal, the content and order of the Product Backlog, clarifying items and answering questions quickly.
- Remember
- Influence works through direction and information; control over people and methods belongs to the team.
- Tested as
- Used to pick the legitimate action among options that all aim at the same outcome.
- Trap
- Treating the Product Owner as the team's line manager because they own priorities.
-
Mutual accountability
Developers hold each other accountable as professionals for following their plan and meeting the Definition of Done.
- Remember
- Accountability inside the team is peer-based rather than enforced by the Product Owner.
- Tested as
- Questions where one Developer underperforms and someone outside wants to intervene.
- Trap
- Selecting the Product Owner reporting a Developer to a manager as the first response.
-
Team size and scaling
A Scrum Team is small enough to stay nimble, typically 10 or fewer people; a larger group should split into several cohesive Scrum Teams on the same product.
- Remember
- Split teams share one Product Goal, one Product Backlog and one Product Owner.
- Tested as
- Questions about adding people or forming new teams on a growing product.
- Trap
- Giving each new team its own Product Owner and backlog.
-
Scrum Master service to the team
The Scrum Master coaches team members in self-management and cross-functionality and removes impediments to progress.
- Remember
- When a team struggles with self-management, the Scrum Master is the natural coach, with the Product Owner supporting.
- Tested as
- Questions ask who helps a team that keeps waiting for instructions.
- Trap
- Picking the Product Owner as the person who should start directing a struggling team.
-
Focus on the Sprint Goal
The Sprint Goal gives the self-managing team a shared objective that lets members choose flexibly how to reach it.
- Remember
- A clear Sprint Goal reduces the need for detailed outside direction.
- Tested as
- Scenarios where a team works on disconnected items with no common purpose.
- Trap
- Assuming a long list of detailed tasks from the Product Owner replaces a coherent goal.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Self-managing team vs. directed team
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Self-managing team | Decides internally who does what, when and how | Authority over work methods and assignments sits inside the team | Assuming it has no boundaries; it still works to the Sprint Goal and Definition of Done |
| Directed team | A manager or lead assigns tasks and sets methods | Authority sits outside the people doing the work | Treating a Product Owner who assigns tasks as still running Scrum |
Product Owner influence vs. control
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Influence | Setting the Product Goal, ordering the backlog, explaining value and answering questions | Uses direction and information the Developers need to decide well | Underusing it by staying absent until the Sprint Review |
| Control | Assigning work, dictating scope per Sprint, imposing techniques | Takes decisions that the Scrum Guide gives to the Developers | Justifying it because the Product Owner is accountable for value |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Reassigning a slow item
- What candidates pick
- The Product Owner moves a high-value item from one Developer to another.
- Why it looks right
- It looks like protecting value, which is the Product Owner's accountability.
- Why it's wrong
- Who does what is decided inside the self-managing team; the Product Owner's lever is making the item's urgency and value transparent.
Clue to watch for The option names a specific person the Product Owner moves work to or from.
-
Setting a Sprint quota
- What candidates pick
- The Product Owner tells the Developers they must complete twelve items this Sprint to meet a launch.
- Why it looks right
- Deadlines are real and the Product Owner owns the release.
- Why it's wrong
- The Developers select the items they can complete; the Product Owner discusses ordering and trade-offs, and adapts the release plan to the evidence.
Clue to watch for Numbers of items imposed on the team rather than forecast by it.
-
Mandating a technique
- What candidates pick
- The Product Owner requires the Developers to use a particular testing tool because a stakeholder likes it.
- Why it looks right
- Tools affect quality, which feels like a product concern.
- Why it's wrong
- How the work is done is the Developers' decision; quality expectations belong in the Definition of Done and backlog items, not in Product Owner mandates.
Clue to watch for A how decision dressed up as a quality or stakeholder requirement.
-
Product Owner takes over a struggling team
- What candidates pick
- Because the team waits for instructions, the Product Owner starts giving daily task lists.
- Why it looks right
- It gets work moving quickly.
- Why it's wrong
- It deepens dependence; the Scrum Master coaches self-management while the Product Owner clarifies goals and items.
Clue to watch for A team that lacks initiative, plus options in which someone starts directing it.
-
Reporting peers to management
- What candidates pick
- The Product Owner reports an underperforming Developer to a line manager as the first step.
- Why it looks right
- It feels like proper escalation.
- Why it's wrong
- Developers hold each other accountable as professionals; the first move is a transparent conversation inside the Scrum Team, with Scrum Master support.
Clue to watch for The word first, combined with an option that leaves the team.
Answer framework
Use these steps when a PSPO I question involves the Product Owner and how the Developers work.
- Identify the decision at stake: who works on an item, how it is built, in what sequence, or how much work enters the Sprint.
- Assign it to the self-managing Scrum Team unless it concerns the Product Goal, the content of Product Backlog items or their order, which the Product Owner owns.
- Look for the option where the Product Owner uses legitimate levers: goals, ordering, clarification, fast answers and transparent information about value and deadlines.
- Reject options that impose quotas, assignments or techniques on the Developers, even when the motive is value.
- If the team is struggling with self-management, prefer the Scrum Master coaching it, with the Product Owner sharpening goals, over anyone outside the team taking control.
Practice question
Want more like this? The PSPO I practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Begin by reading the Scrum Guide's sections on the Scrum Team and the Developers, noting every phrase that describes a decision the team makes internally. Then reread the Product Owner section and list the levers it gives the Product Owner: the Product Goal, the Product Backlog items, their order and transparency. Holding those two lists side by side is the core of this competency.
The highest-priority concept is the boundary between influence and control. Underestimated areas are the Developers' forecast at Sprint Planning, the shared-backlog rule when teams split, and the Scrum Master's role when a team is not yet self-managing. Candidates from manager roles should practice spotting options that sound responsible but take a decision away from the Developers.
After studying, revisit framework and stakeholder questions and check each wrong option against the self-management rule; it is often the fastest way to eliminate two distractors. Because this competency has one focus area, keep the time short and move on to Managing Products with Agility.
FAQ
Why does a Product Owner exam include a people and teams competency?
Scrum.org lists Developing People and Teams with the focus area Self-Managing Teams on the PSPO I page. Product Owners work daily with the Developers, and many scenarios test whether they respect the team's decision rights.
How many questions come from Self-Managing Teams?
Scrum.org does not publish question counts by competency or focus area. This page's estimate of about 7 assumes an even split of 80 questions across the 12 listed focus areas.
Can the Product Owner tell the Developers which item to work on first?
The Product Owner orders the Product Backlog, which signals what is most valuable. Within the Sprint, the Developers decide how and in what sequence to complete the work toward the Sprint Goal.
Is self-managing the same as self-organizing?
The 2020 Scrum Guide replaced self-organizing with self-managing to stress that the team decides who does what, when and how, not only how. Study the current term.
What should a Product Owner do if the Developers seem to underperform?
Make the impact on value transparent and raise it with the Scrum Team, often at the Sprint Retrospective. The Scrum Master supports improvement; the Product Owner does not manage individuals.
Does self-management mean the Developers can change the Product Goal?
No. The Product Owner develops and communicates the Product Goal. Developers bring information that may lead the Product Owner to adapt it, but the decision stays with the Product Owner.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 2 knowledge
You have covered self-management and how a Product Owner influences the Developers without directing them. Test whether you can spot options that take decisions away from the team.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the PSPO I AI tutor Get any concept explained your way