Professional Scrum Product Owner I (PSPO I) Exam Questions

Which statement best describes the Product Owner’s overall accountability according to the Scrum Guide?

✅ A. Maximizing the value of the product resulting from the work of the Scrum Team
⬜ B. Facilitating the Daily Scrum and removing impediments for the Developers
⬜ C. Writing and personally testing every Product Backlog item
⬜ D. Approving the Definition of Done used by a different Scrum Team

Explanation:
The Scrum Guide states that the Product Owner “is accountable for maximizing the value of the product resulting from the work of the Scrum Team.” This is the single, overarching accountability from which all of the Product Owner’s Product Backlog work flows.
Why other options are incorrect:
B: Facilitating events and removing impediments describes how a Scrum Master serves the Scrum Team, not the Product Owner’s core accountability.
C: The Guide never assigns coding or testing work to the Product Owner; turning Product Backlog items into an Increment is the Developers’ accountability.
D: The Definition of Done for a product is not something one team’s Product Owner approves for another team.
Source: What is a Product Owner? | Scrum.org
Source: The 2020 Scrum Guide

---

According to the Scrum Guide, the Product Owner is:

✅ A. One person, not a committee
⬜ B. A role that rotates among the Developers each Sprint
⬜ C. The person who assigns individual tasks to Developers each day
⬜ D. Optional on Scrum Teams with fewer than five members

Explanation:
The Scrum Guide is explicit: “The Product Owner is one person, not a committee.” Concentrating the accountability in one person allows for timely, unambiguous decisions about the Product Backlog.
Why other options are incorrect:
B: The Guide does not describe the Product Owner accountability as something that rotates Sprint to Sprint.
C: The Developers decide how to do their own work; the Product Owner does not assign individual daily tasks.
D: The Guide defines three accountabilities — Developers, Product Owner, Scrum Master — for every Scrum Team regardless of size.
Source: The 2020 Scrum Guide

---

A Product Owner wants the Product Backlog to reflect the interests of many different stakeholders. What does the Scrum Guide say about this?

✅ A. The Product Owner may represent the needs of many stakeholders in the Product Backlog, but the accountability itself remains with one person
⬜ B. Each major stakeholder group should have its own Product Owner for the same product
⬜ C. Each stakeholder group should maintain a separate backlog and merge them at Sprint Review
⬜ D. The Scrum Master should mediate stakeholder requests and make the final ordering decision

Explanation:
The Product Owner “may represent the needs of many stakeholders in the Product Backlog,” but this accountability “cannot be distributed across several people or a committee” — it stays with one person who provides timely decision-making.
Why other options are incorrect:
B: Multiple Product Owners for one product would split the single accountability the Guide requires.
C: The Product Backlog is described as “the single source of work undertaken by the Scrum Team”; multiple backlogs would break that.
D: The Scrum Master serves and supports the Product Owner but does not take over ordering decisions.
Source: What is a Product Owner? | Scrum.org
Source: The 2020 Scrum Guide

---

A stakeholder asks a Developer to personally move a favorite feature to the top of the Product Backlog. What does the Scrum Guide indicate should happen?

✅ A. The Developer should direct the stakeholder to the Product Owner, since ordering the Product Backlog is the Product Owner’s accountability
⬜ B. The Developer may reorder the Product Backlog directly, since Developers do the work
⬜ C. The Scrum Master should reorder the Product Backlog on the stakeholder’s behalf
⬜ D. The whole Scrum Team should vote on the new order at the next Daily Scrum

Explanation:
“Ordering Product Backlog items” is one of the Product Owner’s explicit Product Backlog management accountabilities. Anyone wanting to change an item’s order or priority must work through the Product Owner.
Why other options are incorrect:
B: Developers are accountable for turning Product Backlog items into an Increment, not for ordering the backlog.
C: The Scrum Guide does not assign backlog-ordering authority to the Scrum Master.
D: The Daily Scrum exists for the Developers to inspect progress toward the Sprint Goal, not to vote on backlog order.
Source: The 2020 Scrum Guide
Source: What is a Product Owner? | Scrum.org

---

If a Product Owner delegates the work of managing the Product Backlog to someone else, who remains accountable for the outcome?

✅ A. The Product Owner
⬜ B. Whoever performed the delegated work
⬜ C. The Scrum Master
⬜ D. Accountability transfers permanently to the delegate

Explanation:
The Scrum Guide states: “The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the Product Owner remains accountable.” Delegating the task never delegates the accountability.
Why other options are incorrect:
B: The person doing delegated work is not the accountable party — the Guide is explicit that accountability stays with the Product Owner.
C: The Scrum Master’s service to the Product Owner does not make the Scrum Master accountable for backlog outcomes.
D: Accountability does not transfer with delegated tasks under Scrum.
Source: The 2020 Scrum Guide

---

Which TWO of the following are explicitly listed in the Scrum Guide as part of the Product Owner’s Product Backlog management accountabilities?

✅ A. Developing and explicitly communicating the Product Goal
✅ B. Ensuring that the Product Backlog is transparent, visible, and understood
⬜ C. Facilitating the Sprint Retrospective for the Developers
⬜ D. Personally estimating story points for every Product Backlog item

Explanation:
The Scrum Guide lists effective Product Backlog management as including: developing and explicitly communicating the Product Goal; creating and clearly communicating Product Backlog items; ordering Product Backlog items; and ensuring the Product Backlog is transparent, visible, and understood.
Why other options are incorrect:
C: Facilitating the Sprint Retrospective is not one of the four listed Product Backlog management accountabilities, and retrospective facilitation is typically associated with the Scrum Master.
D: The Guide assigns sizing (estimating) of Product Backlog items to the Developers, not to the Product Owner.
Source: The 2020 Scrum Guide
Source: What is a Product Owner? | Scrum.org

---

A single product is being built by three separate Scrum Teams. According to Scrum.org, how many Product Backlogs should exist for that product?

✅ A. One Product Backlog, used to describe the upcoming work on the product
⬜ B. One Product Backlog per team, synchronized weekly
⬜ C. One Product Backlog per Developer specialty (e.g., frontend, backend, QA)
⬜ D. As many Product Backlogs as there are stakeholder groups

Explanation:
Scrum.org explains: “Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.” This keeps a single source of ordered work even when several teams contribute to it.
Why other options are incorrect:
B: Splitting the backlog per team contradicts the idea of a single, shared source of work for the product.
C: Backlogs are not divided by Developer specialty in Scrum.
D: Stakeholder groups do not each get a separate Product Backlog; the Product Owner consolidates their needs into the one backlog.
Source: What is a Product Backlog? | Scrum.org

---

Which TWO of the following are ways the Scrum Guide says the Scrum Master serves the Product Owner?

✅ A. Helping find techniques for effective Product Goal definition and Product Backlog management
✅ B. Facilitating stakeholder collaboration as requested or needed
⬜ C. Deciding the final order of the Product Backlog whenever the Product Owner is unavailable
⬜ D. Writing and publishing Product Backlog items on the Product Owner’s behalf without review

Explanation:
The Scrum Guide lists several ways the Scrum Master serves the Product Owner, including helping find techniques for effective Product Goal definition and Product Backlog management, and facilitating stakeholder collaboration as requested or needed.
Why other options are incorrect:
C: The Guide does not authorize the Scrum Master to take over backlog-ordering decisions, even temporarily; ordering remains the Product Owner’s accountability.
D: Nothing in the Guide describes the Scrum Master publishing backlog items unilaterally and without the Product Owner’s involvement.
Source: The 2020 Scrum Guide

---

Per Scrum.org’s description of Product Backlog Management, who ultimately decides what work the Scrum Team pursues now, later, or not at all?

✅ A. The Product Owner
⬜ B. A majority vote of the Developers
⬜ C. The most senior stakeholder
⬜ D. The Scrum Master, based on the roadmap

Explanation:
Scrum.org states that the Product Owner “is accountable for managing the Product Backlog” and “ultimately decides on what work to pursue now, later or not at all,” even though the responsibility for doing that work can be delegated.
Why other options are incorrect:
B: Developers may size and select items for a Sprint, but the ultimate now/later/never decision rests with the Product Owner.
C: A stakeholder’s seniority does not override the Product Owner’s accountability for the Product Backlog.
D: The Scrum Master supports backlog management but does not make this decision.
Source: What is Product Backlog Management? | Scrum.org

---

How many accountabilities does the Scrum Guide define within a Scrum Team, and what are they?

✅ A. Three: the Developers, the Product Owner, and the Scrum Master
⬜ B. Four: the Developers, the Product Owner, the Scrum Master, and a Project Manager
⬜ C. Two: the Development Team and the Product Owner
⬜ D. It is left undefined and varies by organization

Explanation:
“Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master.” The Guide also states there are no sub-teams or hierarchies within a Scrum Team.
Why other options are incorrect:
B: A Project Manager is not one of the Guide’s defined accountabilities.
C: The Guide names three accountabilities, not two — the Scrum Master is also an explicit accountability.
D: The Guide is explicit and consistent about these three accountabilities; it does not leave them to organizational discretion.
Source: The 2020 Scrum Guide

---

According to the Scrum Guide, what is the Product Backlog?

✅ A. An emergent, ordered list of what is needed to improve the product, and the single source of work for the Scrum Team
⬜ B. A fixed list of requirements signed off before work begins
⬜ C. A list of technical tasks maintained solely by the Developers, without Product Owner involvement
⬜ D. A backlog of defects only, kept separate from feature requests

Explanation:
The Scrum Guide defines the Product Backlog as “an emergent, ordered list of what is needed to improve the product” and states it “is the single source of work undertaken by the Scrum Team.”
Why other options are incorrect:
B: The Product Backlog is emergent — it changes as more is learned — not a fixed, frozen list.
C: The Product Owner is accountable for ordering the backlog and ensuring it is transparent, so it is not maintained solely by the Developers.
D: The Product Backlog covers all product work, not just defects.
Source: The 2020 Scrum Guide
Source: What is a Product Backlog? | Scrum.org

---

What is Product Backlog refinement, per the Scrum Guide?

✅ A. The act of breaking down and further defining Product Backlog items into smaller, more precise items, done on an ongoing basis
⬜ B. A formal ceremony that the Guide requires to consume exactly 10% of every Sprint
⬜ C. A one-time event that happens only at the very start of a product’s life
⬜ D. A task performed exclusively by the Scrum Master, without the Developers

Explanation:
“Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size.”
Why other options are incorrect:
B: The Scrum Guide does not mandate any fixed time-box or percentage (such as a common industry ‘10% rule’) for refinement — that is a widespread practice, not a Guide requirement.
C: Refinement is described as ongoing, not a single upfront event.
D: Refinement is a collaborative activity involving the Product Owner and Developers, not an exclusive Scrum Master task.
Source: The 2020 Scrum Guide
Source: What is a Product Backlog? | Scrum.org

---

Who is responsible for sizing (estimating) Product Backlog items, according to the Scrum Guide?

✅ A. The Developers who will be doing the work
⬜ B. The Product Owner, based on business value
⬜ C. The Scrum Master, using historical velocity
⬜ D. A separate estimation committee

Explanation:
Scrum.org’s summary of the Guide is direct: “The Developers who will be doing the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs.”
Why other options are incorrect:
B: The Product Owner may influence trade-offs but does not perform the sizing itself.
C: Sizing is not assigned to the Scrum Master in the Guide.
D: No separate estimation committee is described in Scrum.
Source: What is a Product Backlog? | Scrum.org

---

What does the Product Goal represent?

✅ A. A future state of the product that serves as a long-term target for the Scrum Team to plan against
⬜ B. The exact list of Product Backlog items to be finished in the current Sprint
⬜ C. A short-term target owned jointly by the Scrum Master and Developers
⬜ D. A marketing slogan approved by the organization’s executives

Explanation:
“The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against… The Product Goal is the long-term objective for the Scrum Team.”
Why other options are incorrect:
B: That describes the Sprint Backlog / Sprint Goal’s shorter-term scope, not the Product Goal.
C: Developing and communicating the Product Goal is a Product Owner accountability, not a joint Scrum Master/Developers one.
D: The Guide describes the Product Goal as a directional target for the product, not a marketing slogan.
Source: The 2020 Scrum Guide
Source: What is a Product Goal? | Scrum.org

---

Each Scrum artifact has an associated commitment that provides transparency and focus. What is the commitment for the Product Backlog?

✅ A. The Product Goal
⬜ B. The Sprint Goal
⬜ C. The Definition of Done
⬜ D. The Sprint Backlog

Explanation:
Scrum.org explains: “The commitment of the Product Backlog is the Product Goal.” (For comparison, the Sprint Backlog’s commitment is the Sprint Goal, and the Increment’s commitment is the Definition of Done.)
Why other options are incorrect:
B: The Sprint Goal is the commitment associated with the Sprint Backlog, not the Product Backlog.
C: The Definition of Done is the commitment associated with the Increment.
D: The Sprint Backlog is a separate artifact, not a commitment of the Product Backlog.
Source: What is a Product Goal? | Scrum.org

---

How many Product Goals can a Product Backlog have at any given time, per Scrum.org’s explanation?

✅ A. Only one; the Scrum Team must fulfill or abandon it before taking on the next
⬜ B. As many as there are active stakeholders
⬜ C. One per Sprint
⬜ D. Unlimited, as long as each is listed in the backlog

Explanation:
“There is only one Product Goal for the Product Backlog at any given time… They must fulfill (or abandon) one objective before taking on the next.”
Why other options are incorrect:
B: Product Goals are not created per stakeholder; there is a single one for the product’s backlog.
C: A Product Goal is a longer-term target than a single Sprint; it is not replaced every Sprint.
D: The Guide’s supplementary material is explicit that there is only one at a time, not an unlimited list.
Source: What is a Product Goal? | Scrum.org

---

When are Product Backlog items generally considered ready for selection in a Sprint Planning event?

✅ A. When they can be Done by the Scrum Team within one Sprint, usually after refinement activities
⬜ B. As soon as the Product Owner writes a one-line title for them
⬜ C. Only after a formal sign-off from every stakeholder
⬜ D. When the Scrum Master assigns them a numeric priority

Explanation:
Scrum.org states: “Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for selection in a Sprint Planning event. They usually acquire this degree of transparency after refining activities.”
Why other options are incorrect:
B: A one-line title alone does not give an item the transparency the Guide describes as needed for readiness.
C: The Guide does not require a formal, all-stakeholder sign-off for readiness.
D: Numeric priority assignment by the Scrum Master is not how readiness is determined.
Source: What is a Product Backlog? | Scrum.org

---

According to the Scrum Guide, what does the Sprint Backlog consist of?

✅ A. The Sprint Goal (why), the Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how)
⬜ B. Only the Product Backlog items selected for the Sprint
⬜ C. A fixed plan that cannot be updated once the Sprint begins
⬜ D. The Product Goal plus the Definition of Done

Explanation:
The Sprint Backlog is “composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).”
Why other options are incorrect:
B: This omits both the Sprint Goal and the delivery plan, which are explicit parts of the Sprint Backlog.
C: The Guide states the Sprint Backlog “is updated throughout the Sprint as more is learned,” so it is not fixed.
D: The Product Goal and Definition of Done are commitments of different artifacts (the Product Backlog and the Increment, respectively), not components of the Sprint Backlog.
Source: The 2020 Scrum Guide

---

The Scrum Guide describes the Sprint Backlog as “a plan by and for” whom?

✅ A. The Developers
⬜ B. The Product Owner
⬜ C. The Scrum Master
⬜ D. The organization’s leadership

Explanation:
The Guide states the Sprint Backlog “is a plan by and for the Developers,” reflecting that the Developers create and own how they will accomplish the Sprint Goal.
Why other options are incorrect:
B: The Product Owner’s planning artifact is oriented around the Product Backlog and Product Goal, not the Sprint Backlog’s internal plan.
C: The Scrum Master is not described as the owner of the Sprint Backlog plan.
D: Organizational leadership plays no role in authoring the Sprint Backlog.
Source: The 2020 Scrum Guide

---

During a Sprint, the Developers learn that some planned work is unnecessary to reach the Sprint Goal. What does the Scrum Guide say happens to the Sprint Backlog?

✅ A. Scope may be clarified and renegotiated with the Product Owner as more is learned
⬜ B. The Sprint Goal itself must be changed to match the new scope
⬜ C. Only the Scrum Master is allowed to modify the Sprint Backlog
⬜ D. No change can occur until the next Sprint Planning event

Explanation:
The Guide notes that the Sprint Backlog “is updated throughout the Sprint as more is learned,” and “scope may be clarified and renegotiated with the Product Owner as more is learned.”
Why other options are incorrect:
B: The Sprint Goal, once finalized, provides stable focus for the Sprint; it is the scope of work — not the goal — that gets renegotiated.
C: The Sprint Backlog belongs to the Developers, who update it themselves during the Sprint.
D: This contradicts the Guide’s description of the Sprint Backlog as a living plan updated throughout the Sprint.
Source: The 2020 Scrum Guide

---

What does the Scrum Guide say about Product Backlog item attributes such as description, order, and size?

✅ A. They often vary with the domain of work
⬜ B. They are standardized identically for every industry by the Guide
⬜ C. They must always include a fixed story-point estimate
⬜ D. They are set once when an item is created and never revisited

Explanation:
The Guide states refinement adds “details, such as a description, order, and size,” and that “attributes often vary with the domain of work.”
Why other options are incorrect:
B: The Guide explicitly says attributes vary rather than being standardized across all domains.
C: Story points are a common industry technique, not something the Scrum Guide mandates.
D: Refinement is an ongoing activity, so attributes are revisited and updated over time, not fixed at creation.
Source: The 2020 Scrum Guide

---

Beyond ordering the Product Backlog, what is the Product Owner accountable for ensuring about it?

✅ A. That it is transparent, visible, and understood
⬜ B. That every item carries a fixed delivery deadline
⬜ C. That it never contains more than a set number of items
⬜ D. That every Developer signs off on each item before it is added

Explanation:
The Scrum Guide lists as a Product Owner accountability: “Ensuring that the Product Backlog is transparent, visible and understood.”
Why other options are incorrect:
B: The Guide does not require fixed deadlines on Product Backlog items.
C: No item-count limit is specified in the Guide.
D: Developer sign-off on every added item is not a Guide requirement.
Source: The 2020 Scrum Guide

---

What does Scrum.org say is a core purpose of the Product Owner role?

✅ A. To bridge the gap between strategy and agile product management in order to create valuable products using Scrum
⬜ B. To manage the organization’s HR processes for the Scrum Team
⬜ C. To act as a substitute Scrum Master when needed
⬜ D. To own the codebase and approve every pull request

Explanation:
Scrum.org’s PSPO I certification page states: “Earning PSPO I shows your understanding of how to bridge the gap between strategy and agile product management in order to create valuable products using Scrum.”
Why other options are incorrect:
B: HR process management is not described as a Product Owner responsibility.
C: The Product Owner and Scrum Master are distinct, separate accountabilities; one does not substitute for the other.
D: Approving pull requests is technical work belonging to the Developers, not the Product Owner.
Source: Professional Scrum Product Owner™ I Certification | Scrum.org

---

The Scrum Guide is intentionally minimal about how to order the Product Backlog for value. Which statement is accurate?

✅ A. The Scrum Guide does not mandate any specific prioritization technique such as MoSCoW or WSJF — it only requires that the Product Backlog be ordered
⬜ B. The Scrum Guide requires the MoSCoW method for ordering the Product Backlog
⬜ C. The Scrum Guide mandates Weighted Shortest Job First (WSJF) as the ordering technique
⬜ D. The Scrum Guide requires a numeric business-value score on every Product Backlog item

Explanation:
The Scrum Guide only states that the Product Backlog is “ordered” and that ordering it is a Product Owner accountability; it does not name or require MoSCoW, WSJF, RICE, or any other specific prioritization technique. Such techniques are common industry practice layered on top of the framework, not Scrum Guide requirements.
Why other options are incorrect:
B: MoSCoW is never mentioned in the Scrum Guide.
C: WSJF is never mentioned in the Scrum Guide; it originates from other frameworks and industry practice.
D: The Guide does not require any numeric scoring scheme on Product Backlog items.
Source: The 2020 Scrum Guide

---

How does Scrum.org define Product Backlog Management?

✅ A. The act of adjusting and ordering items on the Product Backlog so the Scrum Team can deliver the most valuable product possible
⬜ B. The act of writing detailed acceptance criteria for every user story
⬜ C. A quarterly roadmap review conducted by executives
⬜ D. Assigning story points to items using a fixed formula

Explanation:
“Product Backlog Management is the act of adjusting and ordering items on the Product Backlog so that the Scrum Team can deliver the most valuable product possible.”
Why other options are incorrect:
B: Writing acceptance criteria is a possible refinement activity, not the definition of Product Backlog Management itself.
C: This is not how Scrum.org defines the term; it is not an executive review cadence.
D: No fixed story-point formula is described as part of Product Backlog Management.
Source: What is Product Backlog Management? | Scrum.org

---

Which three pillars uphold every implementation of empirical process control that the Product Owner relies on for product planning?

✅ A. Transparency, Inspection, and Adaptation
⬜ B. Planning, Estimating, and Reporting
⬜ C. Prioritization, Negotiation, and Sign-off
⬜ D. Budgeting, Scheduling, and Staffing

Explanation:
The Scrum Guide states that empiricism rests on three pillars: transparency (the process and work must be visible), inspection (artifacts and progress must be inspected frequently), and adaptation (adjusting when results deviate from what’s acceptable).
Why other options are incorrect:
B: These are general project-management terms, not the Guide’s three pillars of empiricism.
C: Negotiation and sign-off are not pillars named in the Scrum Guide.
D: Budgeting, scheduling, and staffing are not the empirical pillars described in the Guide.
Source: The 2020 Scrum Guide

---

Per the Scrum Guide, the Scrum Master helps the Product Owner with which empirical practice?

✅ A. Helping establish empirical product planning for a complex environment
⬜ B. Personally forecasting exact release dates on the Product Owner’s behalf
⬜ C. Replacing the Product Owner during stakeholder negotiations
⬜ D. Approving the Product Backlog order before it is published

Explanation:
Among the ways the Scrum Master serves the Product Owner, the Guide lists “Helping establish empirical product planning for a complex environment.”
Why other options are incorrect:
B: The Guide does not have the Scrum Master personally forecast release dates for the Product Owner.
C: The Scrum Master facilitates stakeholder collaboration “as requested or needed”; this doesn’t mean replacing the Product Owner in negotiations.
D: Approving backlog order is not a Scrum Master task — ordering is the Product Owner’s accountability.
Source: The 2020 Scrum Guide

---

The Scrum Guide mentions burn-down charts, burn-up charts, and cumulative flow diagrams as forecasting practices. What does it say about them?

✅ A. While proven useful, they do not replace the importance of empiricism
⬜ B. They are mandatory artifacts the Product Owner must maintain
⬜ C. They are the Guide’s officially required forecasting techniques
⬜ D. The Guide forbids using them during the Sprint Review

Explanation:
The Guide acknowledges these forecasting practices exist and are “proven useful,” but explicitly cautions that “these do not replace the importance of empiricism” — i.e., they support, but never substitute for, inspection and adaptation.
Why other options are incorrect:
B: The Guide describes these as practices that exist, not mandatory artifacts it requires the Product Owner to maintain.
C: The Guide does not officially require any single forecasting technique; it simply notes several exist.
D: No such prohibition exists in the Guide.
Source: The 2020 Scrum Guide

---

Per the Scrum Guide, which activities is the Scrum Team responsible for regarding the product?

✅ A. All product-related activities, including stakeholder collaboration, verification, maintenance, operation, experimentation, and research and development
⬜ B. Only writing and testing code; stakeholder communication belongs to a separate sales department
⬜ C. Only Sprint-level development tasks; product strategy is entirely external to the Scrum Team
⬜ D. Only the activities explicitly listed in a signed statement of work

Explanation:
The Guide states: “The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.”
Why other options are incorrect:
B: The Guide explicitly includes stakeholder collaboration as a Scrum Team responsibility, not something outsourced entirely.
C: Product strategy activities like research and stakeholder collaboration are explicitly named as in-scope for the Scrum Team.
D: The Guide’s wording is broad (“anything else that might be required”), not limited to a fixed contractual list.
Source: The 2020 Scrum Guide

---

According to the Scrum Guide’s supplementary material, what is a “product”?

✅ A. A vehicle to deliver value, with a clear boundary, known stakeholders, and well-defined users or customers; it could be a service, a physical product, or something more abstract
⬜ B. Any output of a single Sprint, regardless of stakeholder relevance
⬜ C. A term reserved strictly for physical, manufactured goods
⬜ D. A word used interchangeably with ‘project’ in the Scrum Guide

Explanation:
Scrum.org’s Product Goal resource explains: “A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.”
Why other options are incorrect:
B: Not every Sprint output on its own qualifies as ’the product’; the product is the larger vehicle of value the Product Backlog serves.
C: The definition explicitly includes services and abstract offerings, not just physical goods.
D: The Scrum Guide does not use ‘product’ and ‘project’ interchangeably; Scrum is described as a framework for developing products, not a project-management method.
Source: What is a Product Goal? | Scrum.org

---

Which TWO Focus Areas does Scrum.org list under “Managing Products with Agility” for the PSPO I assessment?

✅ A. Product Backlog Management
✅ B. Stakeholders & Customers
⬜ C. Facilitating the Daily Scrum
⬜ D. Writing automated test scripts

Explanation:
Scrum.org’s PSPO I certification page lists the Focus Areas under “Managing Products with Agility” as: Forecasting & Release Planning, Product Vision, Product Value, Product Backlog Management, Business Strategy, and Stakeholders & Customers.
Why other options are incorrect:
C: Facilitating the Daily Scrum is not listed as a PSPO I Focus Area; it relates more to the Developers’ own inspect-and-adapt event.
D: Writing automated test scripts is a technical Developer activity, not a listed PSPO I Focus Area.
Source: Professional Scrum Product Owner™ I Certification | Scrum.org

---

A Product Owner wants a free way to check their baseline knowledge of Product Backlog management and value maximization before attempting PSPO I. What does Scrum.org offer?

✅ A. The Product Owner Open assessment, a free, non-certifying self-check of 15 questions randomly drawn from a larger pool
⬜ B. A mandatory paid mock exam that must be passed first
⬜ C. A one-on-one interview with a Scrum.org trainer
⬜ D. Access to retired, real PSPO I exam questions

Explanation:
Scrum.org describes the Product Owner Open as “a tool for validating your basic knowledge of the Product Owner accountabilities… The assessment consists of 15 questions randomly selected from a larger pool… This assessment is free and does not include any certification.”
Why other options are incorrect:
B: The Open assessment is free and is not a mandatory paid gate.
C: No such interview requirement is described.
D: Scrum.org does not publish retired real exam questions; the Open assessment draws from its own separate practice pool, not actual test content.
Source: Product Owner Open | Scrum.org

---

What is the first topic addressed during Sprint Planning, according to the Scrum Guide?

✅ A. Why is this Sprint valuable?
⬜ B. How will the chosen work get done?
⬜ C. What can be Done this Sprint?
⬜ D. Who will attend the Sprint Review?

Explanation:
Sprint Planning addresses three topics in order, the first being “Why is this Sprint valuable?” — where the Product Owner proposes how the product could increase its value and utility.
Why other options are incorrect:
B: “How will the chosen work get done?” is the third Sprint Planning topic.
C: “What can be Done this Sprint?” is the second Sprint Planning topic.
D: Sprint Review attendance is not one of the three Sprint Planning topics defined in the Guide.
Source: The 2020 Scrum Guide

---

For Sprint Planning Topic One (“Why is this Sprint valuable?”), who proposes how the product could increase its value and utility in the current Sprint?

✅ A. The Product Owner, drawing on the Product Backlog and Product Goal
⬜ B. The Scrum Master, acting alone
⬜ C. An external business analyst outside the Scrum Team
⬜ D. The Developers, without input on value from the Product Owner

Explanation:
The Guide states: “The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal.”
Why other options are incorrect:
B: The Scrum Master facilitates the event but does not propose the value focus alone — that starts with the Product Owner.
C: The Guide describes this as work of the Scrum Team, not an outside analyst.
D: The whole Scrum Team collaborates on the Sprint Goal, but it is the Product Owner who proposes the value angle to start the conversation.
Source: The 2020 Scrum Guide

---

During Sprint Planning, once Product Backlog items are selected, who decomposes them into a plan for delivering the Increment?

✅ A. The Developers, through Topic Three (“How will the chosen work get done?”)
⬜ B. The Product Owner, who assigns detailed tasks
⬜ C. The Scrum Master, using a Gantt chart
⬜ D. A separate project management office

Explanation:
Topic Three of Sprint Planning has the Developers plan the work needed to create an Increment that meets the Definition of Done, typically decomposing items into smaller work units.
Why other options are incorrect:
B: The Product Owner does not assign detailed technical tasks; how the work gets done is at the Developers’ discretion.
C: Gantt charts and a project office are not part of the Scrum Guide’s description of Sprint Planning.
D: No external project management office is described in Scrum.
Source: The 2020 Scrum Guide

---

When must the Sprint Goal be finalized, per the Scrum Guide?

✅ A. Prior to the end of Sprint Planning
⬜ B. At the Daily Scrum on the second day of the Sprint
⬜ C. During the Sprint Review
⬜ D. It never needs to be finalized

Explanation:
The Guide states: “The Sprint Goal must be finalized prior to the end of Sprint Planning.” It is then added to the Sprint Backlog and provides focus for the whole Sprint.
Why other options are incorrect:
B: The Sprint Goal is set before the Sprint’s work begins, not partway through at a Daily Scrum.
C: The Sprint Review occurs at the end of the Sprint, inspecting progress toward a goal already set — not the moment the goal is finalized.
D: The Guide requires the Sprint Goal to be finalized, not left indefinitely open.
Source: The 2020 Scrum Guide

---

What is the purpose of the Sprint Review, per the Scrum Guide?

✅ A. To inspect the outcome of the Sprint and determine future adaptations
⬜ B. To assign story points for the next Sprint
⬜ C. To formally evaluate each Developer’s individual performance
⬜ D. To rewrite the Definition of Done

Explanation:
“The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.”
Why other options are incorrect:
B: Story-point estimation happens during refinement or Sprint Planning, not as the purpose of the Sprint Review.
C: The Guide does not describe the Sprint Review as an individual performance evaluation.
D: Rewriting the Definition of Done is not the purpose of the Sprint Review.
Source: The 2020 Scrum Guide

---

How does the Scrum Guide characterize the Sprint Review?

✅ A. A working session, and the Scrum Team should avoid limiting it to a presentation
⬜ B. A one-way status presentation from the Product Owner to executives
⬜ C. An optional event that can be skipped whenever there is no new Increment
⬜ D. A private, internal meeting that excludes stakeholders

Explanation:
The Guide states plainly: “The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation.”
Why other options are incorrect:
B: The Guide explicitly warns against treating it as a one-way presentation.
C: The Sprint Review is one of the Scrum events held at the end of every Sprint, not an optional one contingent on having a releasable Increment.
D: The Sprint Review specifically invites stakeholders to inspect the Increment; it is not private.
Source: The 2020 Scrum Guide

---

During the Sprint Review, what do the Scrum Team and invited stakeholders inspect and discuss?

✅ A. The Increment and progress made toward the Product Goal
⬜ B. Only the individual velocity of each Developer
⬜ C. The organization’s annual budget approval process
⬜ D. Personal performance reviews for the Scrum Master

Explanation:
Scrum.org explains: “During the Sprint Review, the Scrum Team and any invited stakeholders and/or customers will inspect the Increment and progress made toward the Product Goal.”
Why other options are incorrect:
B: Individual Developer velocity is not the focus of the Sprint Review’s inspection.
C: Annual budget approvals are not part of the Sprint Review’s purpose.
D: The Scrum Master’s personal performance review is not part of the Sprint Review.
Source: What is a Product Goal? | Scrum.org

---

How do findings from a Sprint Review typically affect the Product Owner’s subsequent work?

✅ A. They influence Sprint Planning and may lead to adaptations of the Product Backlog
⬜ B. They are disregarded, since the Product Backlog is fixed once created
⬜ C. They can only be applied after the entire product ships
⬜ D. They require creating a brand-new Product Goal after every Sprint

Explanation:
Scrum.org notes that Sprint Review discussions “influence Sprint Planning as they can help create focus and form decisions about the next Sprint,” which in practice means the Product Backlog is adapted based on what was learned.
Why other options are incorrect:
B: The Product Backlog is emergent and explicitly meant to be adapted, not fixed.
C: Adaptations happen Sprint by Sprint, not only at final product release.
D: A Product Goal is a longer-term target and is not replaced after every single Sprint.
Source: What is a Product Goal? | Scrum.org

---

Is the Daily Scrum an event where the Product Owner reports status updates to management?

✅ A. No — its purpose is for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog; it is not a status-reporting meeting to management
⬜ B. Yes, the Product Owner is required to report status to management daily as part of the Daily Scrum
⬜ C. Yes, but only the Scrum Master may attend
⬜ D. No, because the Daily Scrum was removed from the current Scrum Guide

Explanation:
“The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.” It is an internal inspect-and-adapt event for the Developers, not a management status report.
Why other options are incorrect:
B: The Guide does not describe the Daily Scrum as a management reporting mechanism for the Product Owner.
C: The Daily Scrum is primarily for the Developers; the Scrum Master is not the sole permitted attendee.
D: The Daily Scrum remains one of the five events in the current Scrum Guide.
Source: The 2020 Scrum Guide

---

Alongside Sprint Planning, the Daily Scrum, and the Sprint Review, which Scrum event does the Product Owner participate in to inspect how the last Sprint went regarding people, relationships, process, and tools?

✅ A. Sprint Retrospective
⬜ B. Backlog Grooming Committee
⬜ C. Quarterly Business Review
⬜ D. Change Advisory Board

Explanation:
The Scrum Guide names five events: the Sprint itself, Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective, where the Scrum Team inspects how the last Sprint went and plans improvements.
Why other options are incorrect:
B: A “Backlog Grooming Committee” is not a Scrum Guide event or body.
C: A Quarterly Business Review is not one of the Guide’s five events.
D: A Change Advisory Board is not part of the Scrum framework as defined in the Guide.
Source: The 2020 Scrum Guide

---

According to the Scrum Guide, who decides how Product Backlog items are turned into Increments of value?

✅ A. The Developers, at their sole discretion — no one else tells them how to do this
⬜ B. The Product Owner, who assigns the technical approach
⬜ C. The Scrum Master, in consultation with architecture standards
⬜ D. The organization’s technical steering committee

Explanation:
The Guide states: “How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value.” This applies to the Product Owner as much as anyone else — the Product Owner sets the what and why, not the technical how.
Why other options are incorrect:
B: The Product Owner does not dictate the technical approach; that is explicitly reserved for the Developers.
C: No architecture-standards consultation role for the Scrum Master is described here.
D: No external steering committee is described as directing this work in the Guide.
Source: The 2020 Scrum Guide

---

What does “self-managing” mean for a Scrum Team, per the Scrum Guide?

✅ A. They internally decide who does what, when, and how
⬜ B. The Product Owner decides who does what and when
⬜ C. An external Scrum Master assigns daily tasks
⬜ D. Self-management applies only to the Product Owner’s own work

Explanation:
“Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint,” and they are “self-managing, meaning they internally decide who does what, when, and how.”
Why other options are incorrect:
B: The Product Owner does not assign who-does-what; that decision is made internally by the team, especially the Developers for their own work.
C: The Scrum Master facilitates and coaches but does not assign daily tasks.
D: Self-management describes the whole Scrum Team’s way of working, not just the Product Owner’s own tasks.
Source: The 2020 Scrum Guide

---

How does the Scrum Guide describe the internal structure of a Scrum Team?

✅ A. There are no sub-teams or hierarchies within a Scrum Team
⬜ B. The Product Owner sits above the Developers in a management hierarchy
⬜ C. The Scrum Master supervises the Developers as their manager
⬜ D. Sub-teams are formed for each Product Backlog item

Explanation:
The Guide states plainly: “Within a Scrum Team, there are no sub-teams or hierarchies.” All three accountabilities work as one cohesive unit.
Why other options are incorrect:
B: The Product Owner is a peer accountability, not a manager positioned above the Developers.
C: The Scrum Master serves the team; the Guide does not describe this as a supervisory management role.
D: Per-item sub-teams contradict the Guide’s “no sub-teams” statement.
Source: The 2020 Scrum Guide

---

The Scrum Guide describes the Scrum Team as a cohesive unit. Which best reflects this description?

✅ A. It is a small team, cross-functional, with members having all the skills necessary to create value each Sprint, focused on one objective at a time
⬜ B. It is a large, multi-layered program structure with several levels of oversight
⬜ C. It must always include a dedicated business analyst and a project manager
⬜ D. Its structure is defined purely by the Product Owner’s position on the org chart

Explanation:
Scrum Teams are described as small, cross-functional, and focused on one product at a time, with the skills needed to deliver a valuable Increment each Sprint — without sub-teams or hierarchies.
Why other options are incorrect:
B: This contradicts the Guide’s emphasis on a small, focused team rather than a large layered structure.
C: The Guide requires exactly three accountabilities — it does not mandate dedicated business-analyst or project-manager roles.
D: Team structure is described by accountabilities and cross-functionality, not by an org-chart position.
Source: The 2020 Scrum Guide

---

Which Scrum Value most directly reflects a Product Owner being honest and transparent with stakeholders about the true state of the Product Backlog and progress?

✅ A. Openness
⬜ B. Focus, to the exclusion of the other values
⬜ C. A value not among the five listed in the Scrum Guide
⬜ D. Only Courage is relevant to the Product Owner

Explanation:
The Scrum Guide names five Scrum Values: Commitment, Focus, Openness, Respect, and Courage. Openness most directly reflects being transparent about work, progress, and challenges with the team and stakeholders.
Why other options are incorrect:
B: Focus concerns concentrating on the Sprint’s work and goals; it is not specifically about transparency with stakeholders.
C: Openness is in fact one of the five values named in the Guide.
D: All five values apply across the whole Scrum Team, not to the Product Owner via Courage alone.
Source: The 2020 Scrum Guide

---

Which TWO statements about Product Owner delegation and self-management are accurate per the Scrum Guide?

✅ A. The Product Owner may delegate Product Backlog work to others but remains accountable for the outcome
✅ B. Delegating backlog work does not eliminate the Scrum Team’s self-managing nature — the Developers still decide how to do the work
⬜ C. Delegation transfers ultimate accountability away from the Product Owner entirely
⬜ D. Self-management means the Product Owner assigns daily tasks to whoever received delegated work

Explanation:
The Guide states delegated Product Backlog work does not change who is accountable (“Regardless, the Product Owner remains accountable”), and separately affirms that Developers retain sole discretion over how they turn items into an Increment — delegation does not override that self-management.
Why other options are incorrect:
C: This directly contradicts the Guide’s statement that the Product Owner remains accountable regardless of delegation.
D: Self-management means the team internally decides who does what; the Product Owner does not assign daily tasks even to a delegate.
Source: The 2020 Scrum Guide

---

For Product Owners to succeed, what does the Scrum Guide say the organization must do?

✅ A. Respect the Product Owner’s decisions, which are visible in the content and ordering of the Product Backlog
⬜ B. Override the Product Owner’s ordering decisions whenever a senior executive disagrees
⬜ C. Require the Scrum Master to co-sign every backlog change
⬜ D. Replace the Product Owner if Sprint targets are missed mid-Sprint

Explanation:
The Guide states: “For Product Owners to succeed, the entire organization must respect their decisions. These decisions are visible in the content and ordering of the Product Backlog.” This protects the self-management of the Scrum Team from outside interference.
Why other options are incorrect:
B: Overriding the Product Owner on executive say-so contradicts the Guide’s call for the organization to respect Product Owner decisions.
C: No Scrum Master co-signature requirement exists in the Guide.
D: Missing a Sprint target mid-Sprint is not grounds described in the Guide for replacing a Product Owner.
Source: The 2020 Scrum Guide

---

A Scrum Master notices the Product Owner struggling to communicate the Product Goal clearly to a new Developer. Per the Scrum Guide’s description of how the Scrum Master serves the Product Owner, what is an appropriate action?

✅ A. Help find techniques for effective Product Goal definition and Product Backlog management, and help the Scrum Team understand the need for clear, concise Product Backlog items
⬜ B. Take over the Product Owner’s accountability for the Product Goal permanently
⬜ C. Tell the Developer to ignore the Product Goal and just follow the Sprint Backlog
⬜ D. Escalate to the organization to have the Product Owner replaced

Explanation:
The Guide lists exactly this kind of support among how the Scrum Master serves the Product Owner: “Helping find techniques for effective Product Goal definition and Product Backlog management” and “Helping the Scrum Team understand the need for clear and concise Product Backlog items.”
Why other options are incorrect:
B: The Scrum Master serves the Product Owner; the Guide never has the Scrum Master permanently assume the Product Owner’s accountability.
C: The Product Goal gives the Sprint Backlog its context; disregarding it contradicts the Guide’s description of the Product Goal as the long-term objective.
D: Struggling to communicate a goal clearly is not described in the Guide as grounds for escalation to replace the Product Owner — coaching support is the appropriate response.
Source: The 2020 Scrum Guide