Professional Scrum Product Owner I (PSPO I) — Questions and Answers

Question 1: Why is it important that only one person owns the Product Backlog?

Because committee management leads to conflicting priorities and unclear direction for the Scrum Team (Correct answer)
Because Scrum rules prohibit shared ownership for legal reasons
Because stakeholders cannot be trusted to manage backlogs
Because the Scrum Master must verify ownership compliance

Correct answer: Because committee management leads to conflicting priorities and unclear direction for the Scrum Team

Single ownership ensures clear, consistent direction; shared backlog management creates conflicting priorities that confuse Developers and dilute focus.

Question 2: What is an Increment in Scrum, and why does it matter to product strategy?

A daily build created by Developers
A document describing planned features for the next quarter
A usable, potentially releasable piece of the product that adds value and meets the Definition of Done (Correct answer)
A stakeholder report on Sprint progress

Correct answer: A usable, potentially releasable piece of the product that adds value and meets the Definition of Done

Each Increment is a concrete step toward the Product Goal; its releasability allows the Product Owner to make strategic decisions about when to release.

Question 3: A stakeholder demands a feature to be implemented in the next sprint, but the Product Owner has already prioritized other high-value items. How should the Product Owner respond?

Explain the current priorities and negotiate a solution based on business value. (Correct answer)
Ask the stakeholder to discuss the change with the Scrum Master.
Immediately escalate the issue to management.
Accept the demand and change the Sprint Backlog.

Correct answer: Explain the current priorities and negotiate a solution based on business value.

The Product Owner is responsible for the Product Backlog and its prioritization to maximize value. When a stakeholder demands a feature, the Product Owner should transparently explain the existing high-priority items and their associated business value. This opens a negotiation to find a solution that best serves the product's overall value, balancing stakeholder needs with strategic priorities.

Question 4: What is the Product Goal in Scrum?

A long-term objective for the product that the Scrum Team works toward (Correct answer)
The Sprint Goal for the current Sprint
A list of features approved by stakeholders
A detailed project plan with milestones

Correct answer: A long-term objective for the product that the Scrum Team works toward

The Product Goal is a long-term objective that gives the Scrum Team direction and provides context for all Sprint Goals and backlog prioritization.

Question 5: How can A/B testing support a Product Owner's decision-making?

By providing empirical evidence about which product variation delivers more value to users (Correct answer)
By replacing stakeholder input in feature decisions
By proving that new features are always better than existing ones
By measuring individual Developer productivity

Correct answer: By providing empirical evidence about which product variation delivers more value to users

A/B testing provides empirical data about user behavior and preference, enabling evidence-based product decisions rather than relying on assumptions or opinions.

Question 6: How can the Product Owner ensure that the Scrum Team delivers value consistently over time?

Set fixed priorities at the start of the project and avoid changes.
Continuously refine and reprioritized the Product Backlog based on feedback. (Correct answer)
Increase the length of sprints to give the team more time to deliver.
Encourage the team to work overtime to meet deadlines.

Correct answer: Continuously refine and reprioritized the Product Backlog based on feedback.

Consistent value delivery in Scrum is achieved through continuous adaptation. The Product Owner ensures this by regularly refining the Product Backlog, incorporating new insights, stakeholder feedback, and market changes. This dynamic process of reprioritization ensures the Development Team is always working on the most valuable items at any given time, keeping the product aligned with evolving needs.

Question 7: How does customer churn rate inform a Product Owner's backlog priorities?

Churn rate is a financial metric irrelevant to backlog ordering
Low churn means the product needs no further development
High churn means the PO should increase marketing spend
High churn signals unmet user needs or product problems that may warrant prioritizing retention improvements over new features (Correct answer)

Correct answer: High churn signals unmet user needs or product problems that may warrant prioritizing retention improvements over new features

High churn indicates the product is failing to sustain user value, often signaling that addressing retention issues should take priority over new feature development.

Question 8: During a Sprint Review, a stakeholder suggests a new feature that could add value to the product. How should the Product Owner respond?

Ignore the suggestion if it was not part of the initial product vision.
Ask the Development Team to implement the feature immediately.
Politely thank the stakeholder and add the feature to the Product Backlog. (Correct answer)
Request the Scrum Master to handle the stakeholder's feedback.

Correct answer: Politely thank the stakeholder and add the feature to the Product Backlog.

The Sprint Review is an opportune moment for stakeholders to inspect the Increment and provide feedback, including new ideas. The Product Owner should welcome such input, thank the stakeholder, and then add the suggestion to the Product Backlog for future consideration and prioritization. This ensures that valuable feedback is captured and evaluated without disrupting the current Sprint.

Question 9: A stakeholder requests a feature that conflicts with the current product strategy. What should the Product Owner do?

Add the feature to the Product Backlog and prioritize it low.
Discuss the feature with the stakeholder and explain the product vision and strategy. (Correct answer)
Ask the Scrum Master to handle the discussion with the stakeholder.
Reject the request outright.

Correct answer: Discuss the feature with the stakeholder and explain the product vision and strategy.

The Product Owner is the sole person responsible for managing the Product Backlog and ensuring its alignment with the product vision and strategy. When a stakeholder requests a feature that conflicts with this strategy, the Product Owner should engage in a constructive discussion. Explaining the rationale behind the current vision helps the stakeholder understand the impact of their request and fosters alignment.

Question 10: How should the Product Owner use market feedback to refine product strategy?

Continuously incorporate market signals, user data, and competitive insights to adapt the strategy and backlog (Correct answer)
Defer to stakeholders to interpret all market feedback
Only collect feedback after the full product is launched
Update strategy only during annual planning cycles

Correct answer: Continuously incorporate market signals, user data, and competitive insights to adapt the strategy and backlog

Empirical product management requires continuous inspection of market feedback and adaptation of strategy and backlog to maximize value over time.

Question 11: What is a product roadmap and how does it relate to the Product Backlog?

A roadmap is maintained by the Scrum Master
A roadmap replaces the Product Backlog in long-term planning
A roadmap communicates the strategic direction and likely evolution of the product; the backlog is its operational expression (Correct answer)
A roadmap is a contract with stakeholders for fixed deliverables

Correct answer: A roadmap communicates the strategic direction and likely evolution of the product; the backlog is its operational expression

A product roadmap visualizes strategic intent and direction, while the Product Backlog represents the near-term ordered list of work to achieve that direction.

Question 12: In the Kano Model, which category describes features that customers expect as a baseline and cause dissatisfaction when absent but little delight when present?

Attractive (Delighters)
Indifferent features
Basic (Must-be) features (Correct answer)
Performance (One-dimensional) features

Correct answer: Basic (Must-be) features

Basic (Must-be) features are table-stakes that customers expect; their absence causes dissatisfaction but their presence does not generate proportional satisfaction.

Question 13: What does 'product thinking' mean for a Product Owner?

Planning all product features in advance before any Sprint
Thinking only about features requested by stakeholders
Focusing on outcomes and user value rather than just output and feature delivery (Correct answer)
Thinking about the technical implementation first

Correct answer: Focusing on outcomes and user value rather than just output and feature delivery

Product thinking shifts focus from delivering features to achieving outcomes and solving real user problems, enabling better value decisions.

Question 14: What is the role of the Definition of Done in ensuring product quality?

It is optional if the team has a strong testing culture
It is a shared standard that ensures every Increment meets minimum quality requirements before being considered complete (Correct answer)
It is defined differently for each Product Backlog item
It is a checklist completed by the Scrum Master at Sprint end

Correct answer: It is a shared standard that ensures every Increment meets minimum quality requirements before being considered complete

The Definition of Done creates a shared quality standard that ensures Increments are truly complete and potentially releasable, preventing hidden technical debt.

Question 15: How many Product Goals can a Scrum Team pursue at one time?

One per team member
As many as stakeholders define
One at a time (Correct answer)
Two — one for current release and one future

Correct answer: One at a time

A Scrum Team focuses on one Product Goal at a time, completing or abandoning it before moving to the next, to maintain focus and coherence.

Question 16: In the Kano Model, 'Performance features' (one-dimensional quality) are best described as features that:

Are technically required but entirely invisible to the user
Customers do not notice until they are completely absent
Surprise and delight customers when unexpectedly present
Generate customer satisfaction proportional to their quantity and quality (Correct answer)

Correct answer: Generate customer satisfaction proportional to their quantity and quality

Performance features follow a linear satisfaction curve — more of them means more satisfaction, and less means less satisfaction, making them directly tied to competitive differentiation.

Question 17: What role does the Sprint Review play in release planning?

It provides an inspection point for the Increment and feedback that informs release decisions and backlog adaptation (Correct answer)
It replaces the need for separate release planning activities
It is a formal release gate that must be passed before any release
It is used only to measure team performance

Correct answer: It provides an inspection point for the Increment and feedback that informs release decisions and backlog adaptation

The Sprint Review gives the Product Owner and stakeholders an opportunity to inspect the Increment and use feedback to refine the release strategy and backlog.

Question 18: A Product Owner wants to reduce risk while delivering early value. Which backlog ordering strategy best achieves both goals simultaneously?

Always prioritize the easiest items regardless of their business value
Prioritize high-value, high-risk items early to learn and adapt sooner (Correct answer)
Order all items by stakeholder seniority of the requester
Let the development team decide backlog order based on technical convenience

Correct answer: Prioritize high-value, high-risk items early to learn and adapt sooner

Tackling high-value, high-risk items early surfaces unknowns when the team still has time to adapt, combining early value delivery with empirical risk management.

Question 19: Why should a Product Owner avoid over-committing to long-term roadmap details?

Because Scrum prohibits planning beyond the current Sprint
Because Developers cannot plan more than one Sprint ahead
Because stakeholders should define long-term plans
Because markets and user needs evolve, making rigid long-range plans obsolete quickly (Correct answer)

Correct answer: Because markets and user needs evolve, making rigid long-range plans obsolete quickly

Empiricism in Scrum recognizes that uncertainty grows over time, so over-detailed long-range plans create false certainty and resistance to adaptation.

Question 20: What is the Product Owner's primary contribution to the Sprint Retrospective?

Evaluating individual Developer performance
Sharing observations on collaboration, communication, and product delivery effectiveness from a value perspective (Correct answer)
Setting process improvement goals for the next Sprint
Providing feedback on team technical skills

Correct answer: Sharing observations on collaboration, communication, and product delivery effectiveness from a value perspective

The Product Owner brings a value-delivery perspective to the Retrospective, offering observations on how team processes affect the product's ability to deliver value.

Question 21: During Sprint Planning, how should the Product Owner handle conflicting stakeholder priorities?

Let stakeholders decide during Sprint Planning
Delay Sprint Planning until all stakeholders agree
Present a single prioritized backlog reflecting their best judgment of value (Correct answer)
Allow Developers to resolve the conflict

Correct answer: Present a single prioritized backlog reflecting their best judgment of value

The Product Owner is accountable for ordering the backlog and must present a single prioritized list, having already resolved conflicts with stakeholders beforehand.

Question 22: Which of the following is the most important reason for the Product Owner to engage stakeholders regularly throughout the product development process?

To gather feedback and adjust the product backlog based on changing needs. (Correct answer)
To prevent stakeholders from interfering with the Scrum Team’s work.
To meet contractual obligations with stakeholders.
To keep stakeholders updated on the team's progress.

Correct answer: To gather feedback and adjust the product backlog based on changing needs.

Regular stakeholder engagement is crucial for the Product Owner to continuously gather feedback, understand evolving market needs, and validate product assumptions. This ongoing dialogue allows the Product Owner to inspect and adapt the Product Backlog, ensuring it remains aligned with the highest value opportunities. This continuous feedback loop is vital for maximizing the product's relevance and success.

Question 23: Which statement best describes the Sprint Goal?

A flexible objective that gives the Sprint coherence and focus (Correct answer)
A list of all committed Sprint Backlog items
A statement approved only by stakeholders
A contractual obligation to deliver specific features

Correct answer: A flexible objective that gives the Sprint coherence and focus

The Sprint Goal is a single objective that provides focus and flexibility for the Developers as they work through the Sprint.

Question 24: How should a Product Owner handle technical debt in the product strategy?

Include technical debt items in the Product Backlog and balance addressing debt with delivering new value (Correct answer)
Ignore it since it is a Developer concern only
Resolve all technical debt before adding new features
Delegate all technical debt decisions to the Scrum Master

Correct answer: Include technical debt items in the Product Backlog and balance addressing debt with delivering new value

Technical debt affects product value and sustainability, so the Product Owner should include debt reduction in the backlog alongside feature development.

Question 25: What should a Product Owner do when a key feature will not be ready for a planned release date?

Cancel the Sprint and replan
Force Developers to work overtime to meet the deadline
Evaluate whether to delay the release, release without the feature, or negotiate scope with stakeholders (Correct answer)
Reduce the Definition of Done to allow partial completion

Correct answer: Evaluate whether to delay the release, release without the feature, or negotiate scope with stakeholders

The Product Owner must make a value-based decision: delay for completeness, release a valuable subset, or renegotiate with stakeholders — never compromise quality.

Question 26: In a 2×2 Value vs. Effort priority matrix, how should items with HIGH value and LOW effort be treated?

Scheduled as quick wins and done first (Correct answer)
Delayed until high-effort items are finished
Deprioritized until capacity allows
Delegated to other teams

Correct answer: Scheduled as quick wins and done first

High value, low effort items maximize return on investment and should be prioritized first as they deliver the most value for the least cost.

Question 27: What makes the Daily Scrum different from a status report meeting?

The Daily Scrum is optional if the team communicates well
The Daily Scrum is run by the Scrum Master as a status update to management
The Daily Scrum includes stakeholders providing daily direction
The Daily Scrum is a planning event for Developers to inspect progress toward the Sprint Goal and adapt their plan (Correct answer)

Correct answer: The Daily Scrum is a planning event for Developers to inspect progress toward the Sprint Goal and adapt their plan

The Daily Scrum is a Developer-owned planning event focused on Sprint Goal progress, not a status update for management or the Product Owner.

Question 28: Why is it important for the Product Owner to attend the Sprint Review?

To inspect the Increment and adapt the Product Backlog based on outcomes and stakeholder feedback (Correct answer)
To report velocity to management
To assign new tasks to Developers
To formally approve each completed item

Correct answer: To inspect the Increment and adapt the Product Backlog based on outcomes and stakeholder feedback

The Product Owner uses the Sprint Review to inspect the Increment, gather stakeholder feedback, and make informed backlog adaptations for the next Sprint.

Question 29: What does it mean for the Product Backlog to be 'ordered' rather than 'prioritized'?

It means items are sorted alphabetically for easy reference
It means items are sequenced by value, risk, learning, and dependencies — not just importance (Correct answer)
It means items are ranked by technical complexity first
There is no practical difference between ordered and prioritized

Correct answer: It means items are sequenced by value, risk, learning, and dependencies — not just importance

Ordering considers multiple factors including value, risk, learning opportunities, and dependencies, producing a more nuanced sequence than simple priority ranking.

Question 30: Which of the following is the most effective way for a Product Owner to handle conflicting requirements from different stakeholders?

Let the Scrum team decide which requirement to implement.
Add all conflicting requirements to the backlog.
Implement the requirement of the most senior stakeholder.
Prioritize the requirements based on business value. (Correct answer)

Correct answer: Prioritize the requirements based on business value.

A Product Owner's core responsibility is to maximize the value of the product. When faced with conflicting requirements, the most effective approach is to prioritize them based on their potential business value, aligning with the product vision and strategy. This ensures that the Scrum Team focuses on delivering the most impactful items first, rather than simply accommodating seniority or adding everything to the backlog.

Question 31: How does the Product Owner interact with the Definition of Done?

The PO can waive the DoD for high-priority features
The PO has no involvement with the Definition of Done
The PO understands it and uses it to determine whether an Increment is truly releasable (Correct answer)
The PO defines it independently and imposes it on Developers

Correct answer: The PO understands it and uses it to determine whether an Increment is truly releasable

The Product Owner uses the Definition of Done to understand what constitutes a complete Increment and to make informed release decisions.

Professional Scrum Product Owner I (PSPO I)

The PSPO I assessment validates knowledge of Scrum, the Product Owner accountabilities, and the skills required to maximize the value of a product using Scrum. It tests understanding of product vision, backlog management, stakeholder engagement, and Scrum theory.

Questions

60 min

Time Limit

85%

To Pass

Checking for saved progress...

Exam Rules

You can skip questions and return to them later
Flag questions for review before submitting
No feedback shown until you submit the entire exam
Unanswered questions count as wrong — answer everything
10 pretest questions are mixed in and don't affect your score
Timer auto-submits when time runs out
Your progress is auto-saved every 30 seconds