The Product Owner
PSM I PSM I · Scrum Team & Accountabilities
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. That single sentence is the whole accountability, and everything else the Product Owner does serves it. How value is maximized varies widely across organizations, teams, and individuals — there is no prescribed method — but the accountability itself never moves. The Product Owner decides what is most valuable to work on next, makes those decisions visible through the ordering of the Product Backlog, and answers for the results. This is a business accountability, not a technical one: the Product Owner does not tell the Developers how to build things, just as the Developers do not tell the Product Owner what is most valuable. The exam tests this boundary constantly, because in real organizations it is the boundary most often crossed.
The Product Owner is also accountable for effective Product Backlog management, which the Guide breaks into four activities: developing and explicitly communicating the Product Goal; creating and clearly communicating Product Backlog items; ordering Product Backlog items; and ensuring that the Product Backlog is transparent, visible, and understood. The Product Owner may do this work personally or delegate the responsibility to others — but regardless of who does the work, the Product Owner remains accountable. Delegation is not abdication. If a business analyst writes the items and a committee orders them, and the backlog becomes a mess, the accountability still sits with the Product Owner. The exam loves this distinction: options where the Product Owner hands accountability to someone else are always wrong.
The Product Owner is one person, not a committee. This rule exists because value decisions need a single point of accountability — a committee cannot be accountable, and a backlog ordered by compromise satisfies nobody. The Product Owner may represent the needs of many stakeholders in the Product Backlog, and anyone who wants to change the backlog can try to convince the Product Owner. But the decision is the Product Owner's alone. For Product Owners to succeed, the entire organization must respect their decisions, which are visible in the content and ordering of the Product Backlog and through the inspectable Increment at the Sprint Review. When a senior executive bypasses the Product Owner and tells Developers to build something directly, the framework is broken — not because executives have no say, but because their say must travel through the Product Owner and the single ordered backlog.
Ordering: the Product Owner's sharpest tool
Ordering is how the Product Owner maximizes value in practice. The Product Backlog is an ordered list, and order is a decision: items at the top are the most valuable, the most urgent, or the best next step toward the Product Goal. Ordering is not the same as prioritizing by a single formula — value, risk, learning, dependencies, and stakeholder needs all feed into it — but it is always the Product Owner's call. The Developers may influence the Product Owner by helping them understand trade-offs, and the Scrum Master may coach the Product Owner on techniques, but neither of them orders the backlog. The exam often presents a scenario where Developers want to work on a technically interesting item while the Product Owner has ordered a less glamorous item first: the correct answer is that the Product Owner's ordering stands, and the Developers select from the top of the backlog in Sprint Planning. The Developers choose how much they can take on and how to do it; they do not choose what is most valuable.
The Product Owner and the Sprint
During the Sprint, the Product Owner's role continues. The Product Owner is the only person who can cancel a Sprint, and only when the Sprint Goal becomes obsolete — for example, if the company changes direction and the goal no longer makes sense. Scope may be clarified and renegotiated with the Product Owner as more is learned during the Sprint: if the Developers discover the work is bigger than expected, they collaborate with the Product Owner to adjust scope while protecting the Sprint Goal. The Product Owner answers the Developers' questions about the items, clarifies what is needed, and accepts that the Developers own the plan for the Sprint. At the Sprint Review, the Product Owner is part of the Scrum Team presenting results to stakeholders and discussing progress toward the Product Goal; the Product Backlog may be adjusted based on what is learned. Note what the Product Owner does not do during the Sprint: they do not manage the Developers, do not change the Sprint Backlog themselves, and do not add work mid-Sprint without the Developers' agreement in the context of the Sprint Goal.
Worked scenario
A stakeholder — the head of sales — walks up to two Developers and asks them to build a reporting feature immediately, bypassing the Product Owner. The Developers, wanting to help, start work on it. Two things have gone wrong. First, the stakeholder bypassed the single ordered backlog: the right path is to convince the Product Owner, who weighs the request against everything else and orders it accordingly. Second, the Developers took on unplanned work without involving the Product Owner in a scope discussion. The Scrum Master's job here is to coach everyone involved: help the stakeholder understand that the Product Owner is the single point of entry for new work, help the Product Owner engage with the stakeholder's need, and help the Developers understand that taking direction from outside the team breaks both self-management and the Product Owner's accountability. The fix is not a rulebook — it is teaching the organization to respect the Product Owner's decisions.
Value is a judgement, not a formula
Maximizing value sounds simple until you have to do it. Value is not the same as revenue, and it is not the same as stakeholder satisfaction: a feature that pleases one loud stakeholder may deliver less value than a quiet improvement that helps thousands of users. The Product Owner weighs value, risk, learning, and dependencies, and makes the call — knowing that some decisions will be wrong and that the empirical loop will reveal them. Saying no is part of the job: every item accepted into the backlog is an item the team will spend time on, and a Product Owner who accepts everything has ordered nothing. The exam tests this through scenarios where the Product Owner must choose between competing requests: the correct answer is the one where the Product Owner decides based on value toward the Product Goal, and makes the reasoning transparent through the backlog's ordering.
Exam traps to watch for
- Thinking the Product Owner can delegate accountability. Work can be delegated; accountability for the Product Backlog always stays with the Product Owner.
- Letting a committee or a manager order the backlog. The Product Owner is one person, not a committee, and ordering is their accountability alone.
- Confusing the Product Owner with a project manager. The Product Owner maximizes value and manages the backlog; they do not assign tasks or manage Developers.
- Believing stakeholders can add work directly. Anyone can try to convince the Product Owner, but only the Product Owner changes the Product Backlog's content and order.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.What is the Product Owner accountable for?
Explanation: The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Establishing Scrum is the Scrum Master's accountability. Creating a usable Increment is the Developers' commitment, shared by the whole team. Removing impediments is the Scrum Master's work.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Scrum Team
Q2.The Product Owner asks a business analyst to write Product Backlog items and order them. The backlog becomes confusing and poorly ordered. Who remains accountable for effective Product Backlog management?
Explanation: The Product Owner may delegate the responsibility for backlog work to others, but regardless, the Product Owner remains accountable. The business analyst did the work but does not hold the accountability. The Scrum Master coaches but does not own the backlog. The Developers work from the backlog but are not accountable for managing it.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Scrum Team
Q3.Which statement about the Product Owner is TRUE?
Explanation: The Guide states that the Product Owner is one person, not a committee — value decisions need a single point of accountability. Sharing the role between two people breaks that single accountability. Seniority is not a requirement; the role is about value decisions, not rank. The Product Owner is not elected by Developers each Sprint.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Scrum Team
Q4.A senior executive wants a new feature added to the product urgently. According to the Scrum Guide, what is the correct way to get it into the Product Backlog?
Explanation: Those who want to change the Product Backlog can do so by trying to convince the Product Owner, who alone decides its content and ordering. Going directly to Developers bypasses the single ordered backlog. The Scrum Master does not change the backlog on anyone's behalf. The Retrospective is for inspecting the team's way of working, not for adding product features.
Exam objective: PSM I Focus Area: Managing Products with Agility — Stakeholders & Customers
Q5.Who is the ONLY person with the authority to cancel a Sprint?
Explanation: Only the Product Owner has the authority to cancel a Sprint, and only when the Sprint Goal becomes obsolete. The Scrum Master cannot cancel a Sprint even with the team's agreement. Developers cannot vote to cancel. Management has no such authority within the Scrum framework.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q6.During a Sprint, the Developers discover that a selected item is much larger than estimated. What SHOULD happen?
Explanation: During the Sprint, scope may be clarified and renegotiated with the Product Owner as more is learned — the Developers and Product Owner collaborate to adjust while protecting the Sprint Goal. Working overtime in silence hides the problem and breaks transparency. Dropping the item without discussion breaks the agreement with the Product Owner. Sprints cannot be extended; their length is fixed.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Backlog Management
Q7.Which of the following is part of effective Product Backlog management, for which the Product Owner is accountable?
Explanation: Ordering Product Backlog items is one of the four activities of effective Product Backlog management, alongside developing and communicating the Product Goal, creating and communicating items, and ensuring the backlog is transparent, visible, and understood. Sizing is the Developers' responsibility — they do the work. How items are implemented is the Developers' decision. The Daily Scrum is the Developers' event, not the Product Owner's.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Backlog Management
Q8.The Developers believe a technically interesting item should be worked on before the item the Product Owner ordered first. What is the correct outcome?
Explanation: Ordering the Product Backlog is the Product Owner's accountability, and the organization must respect the Product Owner's decisions. Self-management means the team decides who does what, when, and how — not what is most valuable. The Scrum Master does not order the backlog. Voting on ordering would make the Product Owner a committee, which the Guide rules out.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Value
Q9.How are the Product Owner's decisions made visible to the organization?
Explanation: The Product Owner's decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review. Weekly status reports are not a Scrum mechanism. The Sprint Backlog belongs to the Developers, not the Product Owner. A quarterly management-approved project plan is not part of Scrum.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Backlog Management