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

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

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

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 2: What is a product roadmap and how does it relate to the Product Backlog?

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

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 3: What is the Scrum Master's role relative to the Product Owner?

The Scrum Master reports the PO's performance to management
The Scrum Master manages the Product Owner and approves backlog decisions
The Scrum Master creates the Product Backlog on behalf of the PO
The Scrum Master helps the Product Owner understand effective backlog management and facilitates Scrum events (Correct answer)

Correct answer: The Scrum Master helps the Product Owner understand effective backlog management and facilitates Scrum events

The Scrum Master serves the Product Owner by coaching backlog management practices, facilitating events, and removing impediments that affect the PO's effectiveness.

Question 4: Why should velocity be used with caution in release forecasting?

Because it is defined by management, not the team
Because it is a lagging, variable metric that cannot guarantee future performance (Correct answer)
Because only the Scrum Master is authorized to interpret velocity
Because Scrum prohibits using velocity for planning

Correct answer: Because it is a lagging, variable metric that cannot guarantee future performance

Velocity varies Sprint to Sprint based on team factors and item complexity, making it a useful trend indicator but not a precise predictive tool.

Question 5: A Product Owner is unsure how to define a compelling Product Vision. Which of the following should they focus on to create it?

The specific features that need to be implemented in the next Sprint.
The business objectives and customer needs the product aims to fulfill. (Correct answer)
The daily progress of the Scrum Team.
The technical details of how the product will be built.

Correct answer: The business objectives and customer needs the product aims to fulfill.

A compelling Product Vision focuses on the 'why' behind the product, addressing the core business objectives it aims to achieve and the specific customer needs it will satisfy. By understanding these fundamental drivers, the Product Owner can articulate a clear purpose and value proposition. This strategic focus ensures the vision is meaningful and resonates with both the team and stakeholders.

Question 6: What is the difference between a product vision and a product strategy?

They are the same thing described differently
Vision is the long-term aspiration for the product; strategy is the approach to achieving that vision (Correct answer)
Strategy is created first, then vision follows
Vision is for stakeholders only; strategy is for the team

Correct answer: Vision is the long-term aspiration for the product; strategy is the approach to achieving that vision

The vision describes where the product is going, while the strategy describes how it will get there through choices about markets, features, and priorities.

Question 7: In the MoSCoW prioritization framework, which category represents features that are critical and must be delivered for the product to be considered viable?

Should have
Must have (Correct answer)
Could have
Won't have this time

Correct answer: Must have

Must have items are non-negotiable requirements; without them the product cannot be launched or would fail to meet its core purpose.

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

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

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 9: How often should the Product Backlog be updated or refined by the Product Owner?

Before each Sprint Planning session.
Only when the stakeholders request a change. (Correct answer)
Once at the beginning of the project.
Continuously, as new information and feedback emerge.

Correct answer: Only when the stakeholders request a change.

The Product Backlog is a dynamic artifact that reflects the most valuable work for the product. Significant updates or re-prioritizations are often triggered by new information or changes in market conditions, which frequently come in the form of stakeholder requests. These requests necessitate a re-evaluation of existing items and potential adjustments to the backlog's order and content to maintain alignment with evolving business goals.

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

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

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 11: What is the Net Promoter Score (NPS) and why might a Product Owner track it?

A metric that measures customer loyalty by asking how likely users are to recommend the product (Correct answer)
A measure of team satisfaction with the Product Owner
A financial metric for revenue forecasting
A measure of feature completion percentage

Correct answer: A metric that measures customer loyalty by asking how likely users are to recommend the product

NPS measures customer loyalty and satisfaction, providing the Product Owner with a signal about overall product health and user advocacy.

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

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

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 13: 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.
Politely thank the stakeholder and add the feature to the Product Backlog. (Correct answer)
Ask the Development Team to implement the feature immediately.
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 14: What does transparency in Scrum artifacts mean for a Product Owner?

Sharing all internal team discussions with stakeholders
Allowing stakeholders to modify the Product Backlog directly
Ensuring the Product Backlog and Increment accurately represent the true state of the product for informed decisions (Correct answer)
Publishing all team metrics publicly

Correct answer: Ensuring the Product Backlog and Increment accurately represent the true state of the product for informed decisions

Transparency means artifacts must honestly reflect reality so that decisions based on them are well-informed; a misleading backlog undermines the entire empirical process.

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

Cancel the Sprint and replan
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
Force Developers to work overtime to meet the deadline

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 16: What is the role of user personas in PSPO product strategy?

They are created by Developers to guide implementation
They help the Product Owner understand target users and make better prioritization decisions (Correct answer)
They are used only during initial product discovery
They replace the need for actual user research

Correct answer: They help the Product Owner understand target users and make better prioritization decisions

User personas represent target user segments, helping the Product Owner empathize with users and make more informed decisions about value and priority.

Question 17: What is a Minimum Viable Product (MVP) and why is it relevant to a PSPO?

The smallest version of a product that allows validated learning about customers with minimal effort (Correct answer)
A prototype used only for internal testing
A product release with no features removed
A product with the lowest possible quality

Correct answer: The smallest version of a product that allows validated learning about customers with minimal effort

An MVP helps the Product Owner test product hypotheses quickly and cheaply, enabling evidence-based decisions about future investment and direction.

Question 18: What is user retention rate and why does it matter to a Product Owner?

The percentage of users who continue using the product over time, indicating whether it delivers sustained value (Correct answer)
The number of new users acquired each Sprint
A measure of customer support ticket resolution time
A metric tracking how long users spend on each page

Correct answer: The percentage of users who continue using the product over time, indicating whether it delivers sustained value

Retention rate reveals whether users find lasting value in the product; low retention signals that the product is not meeting user needs over time.

Question 19: What are the three Scrum artifacts?

Product Backlog, Sprint Backlog, and Burndown Chart
Vision Document, Release Plan, and Sprint Backlog
Product Backlog, Sprint Backlog, and Increment (Correct answer)
Epic, User Story, and Task

Correct answer: Product Backlog, Sprint Backlog, and Increment

The three Scrum artifacts are the Product Backlog, the Sprint Backlog, and the Increment, each with a corresponding commitment.

Question 20: 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
Delegated to other teams
Deprioritized until capacity allows

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 21: What is the relationship between the Sprint Goal and the Product Goal?

The Product Goal replaces the Sprint Goal each Sprint
The Sprint Goal is a step toward achieving the longer-term Product Goal (Correct answer)
They are set independently with no relationship
They are interchangeable terms

Correct answer: The Sprint Goal is a step toward achieving the longer-term Product Goal

Each Sprint Goal should be a coherent step toward the Product Goal, ensuring Sprint work aligns with the longer-term product vision.

Question 22: A stakeholder requests a change that could potentially alter the priorities in the Product Backlog. What should the Product Owner do?

Immediately add the new request to the current sprint.
Reject the request because it disrupts the current sprint.
Add the request to the bottom of the backlog to handle later.
Evaluate the request based on its value and impact, then adjust the backlog as necessary. (Correct answer)

Correct answer: Evaluate the request based on its value and impact, then adjust the backlog as necessary.

The Product Owner is responsible for maximizing product value, which means the Product Backlog is a living artifact that must adapt to new information. When a stakeholder requests a change, the Product Owner must evaluate its potential value, impact on existing priorities, and alignment with the Product Vision. This evaluation allows for informed decisions to adjust the backlog, ensuring the team always works on the most valuable items.

Question 23: Which prioritization approach orders backlog items based on the ratio of value delivered relative to the effort required?

Alphabetical ordering
Chronological ordering
First In, First Out (FIFO)
Value-to-Effort ratio (Correct answer)

Correct answer: Value-to-Effort ratio

The Value-to-Effort ratio directly orders items by their return on investment, ensuring high-value, low-cost items are delivered first.

Question 24: What is the difference between a forecast and a commitment in Scrum?

Commitments are made by Developers; forecasts are made by the PO
A forecast is an informed estimate based on empirical data; a commitment is a firm promise regardless of uncertainty (Correct answer)
They are the same — Scrum teams always commit to forecasts
Scrum prohibits both forecasts and commitments

Correct answer: A forecast is an informed estimate based on empirical data; a commitment is a firm promise regardless of uncertainty

Scrum replaced commitments with forecasts to reflect the empirical reality that complex work has inherent uncertainty that cannot be fully committed to in advance.

Question 25: What is product strategy in the context of PSPO?

The plan for how the product will achieve its vision and deliver value to users and the business (Correct answer)
The Sprint-by-Sprint implementation schedule
The technical architecture decisions made by Developers
A marketing plan for the product launch

Correct answer: The plan for how the product will achieve its vision and deliver value to users and the business

Product strategy describes how the product will move from its current state toward the Product Vision, guiding prioritization and investment decisions.

Question 26: What is the purpose of the Sprint Review in terms of empiricism?

To measure team performance against Sprint velocity targets
To inspect the Increment and adapt the Product Backlog based on outcomes and environment changes (Correct answer)
To present a project status report to management
To formally approve completed work and close the Sprint

Correct answer: To inspect the Increment and adapt the Product Backlog based on outcomes and environment changes

The Sprint Review is an empirical inspect-and-adapt event where the team and stakeholders evaluate progress and use new information to adapt the backlog.

Question 27: What is the primary responsibility of the Product Owner during Sprint Planning?

Clarify the Product Backlog items and their acceptance criteria (Correct answer)
Approve the Sprint backlog before work begins
Facilitate the Daily Scrum
Assign tasks to Developers

Correct answer: Clarify the Product Backlog items and their acceptance criteria

The Product Owner clarifies Product Backlog items and their acceptance criteria so Developers can make informed decisions during Sprint Planning.

Question 28: 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 29: What does 'Definition of Done' mean for the Product Owner?

Acceptance criteria written by stakeholders only
The PO's sign-off that a feature is complete
A list of tasks the PO assigns to Developers
The minimum quality standard an increment must meet before it can be released (Correct answer)

Correct answer: The minimum quality standard an increment must meet before it can be released

The Definition of Done is the shared quality standard that an Increment must meet, giving the Product Owner confidence the work is truly complete.

Question 30: A Product Owner wants to maximize the value of a product but is unsure if certain features will be valuable to the customer. What is the best course of action?

Defer decision-making until more information is available.
Rely on the Development Team to choose which features to build.
Include all features in the product to avoid missing potential value.
Release a minimal viable product (MVP) and gather feedback from users. (Correct answer)

Correct answer: Release a minimal viable product (MVP) and gather feedback from users.

When there's uncertainty about feature value, the best approach is to test assumptions quickly and efficiently. Releasing a Minimal Viable Product (MVP) allows the Product Owner to gather real-world feedback from users with minimal investment. This validates or invalidates hypotheses before committing to full-scale development, minimizing risk and maximizing learning about customer needs.

Question 31: What are the five Scrum events?

Sprint Planning, Backlog Grooming, Daily Standup, Demo, Retrospective
Kickoff, Planning, Execution, Review, Close
Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself (Correct answer)
Sprint Planning, Sprint Review, Sprint Retrospective, Release Planning, and Stakeholder Review

Correct answer: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself

The five Scrum events are the Sprint (which contains the other four), Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

Question 32: What is the Product Owner's accountability regarding the Product Backlog?

Backlog accountability is shared equally across the entire Scrum Team
The PO approves items added by Developers but does not manage order
The PO delegates backlog management fully to the Scrum Master
The PO is accountable for the Product Backlog's content, order, and transparency (Correct answer)

Correct answer: The PO is accountable for the Product Backlog's content, order, and transparency

The Product Owner is fully accountable for the Product Backlog — its content, ordering by value, and transparency — though they may delegate work to others.

Question 33: How should a Product Owner handle a situation where a critical bug is discovered mid-Sprint?

Immediately add the fix to the Sprint Backlog without discussion
Cancel the Sprint and replan
Discuss the issue with Developers; they may adjust scope while protecting the Sprint Goal (Correct answer)
Wait until the next Sprint to address the bug

Correct answer: Discuss the issue with Developers; they may adjust scope while protecting the Sprint Goal

The Product Owner and Developers collaborate to determine if addressing the bug fits within the Sprint Goal and current capacity.

Question 34: What should happen when a Product Goal is achieved?

A new Product Goal is established to continue development (Correct answer)
The Scrum Master declares the project complete
The product is shut down
The team disbands

Correct answer: A new Product Goal is established to continue development

Once a Product Goal is achieved, a new Product Goal is defined, allowing the product to continue evolving and delivering value.

Question 35: What is the difference between leading and lagging indicators for a Product Owner?

Leading indicators are for engineering; lagging indicators are for business
Leading indicators predict future outcomes; lagging indicators confirm past results (Correct answer)
They are interchangeable terms for the same type of metric
Lagging indicators predict trends; leading indicators confirm history

Correct answer: Leading indicators predict future outcomes; lagging indicators confirm past results

Leading indicators like trial sign-ups predict future success, while lagging indicators like quarterly revenue confirm past performance — both are useful for different decisions.

Question 36: In WSJF, what does 'Time Criticality' specifically measure when calculating the Cost of Delay?

How rapidly the value of a feature decays or the market window closes over time (Correct answer)
The deadline set by the Scrum Master for completing sprint goals
The amount of refinement time the team spends preparing the backlog item
The total number of sprint cycles estimated to complete the feature

Correct answer: How rapidly the value of a feature decays or the market window closes over time

Time Criticality captures the urgency dimension of Cost of Delay — specifically how quickly the opportunity or value erodes if the feature is deferred, distinguishing time-sensitive items from evergreen ones.

Question 37: How does a strong Product Goal benefit the Scrum Team?

It provides a shared focus that helps the team make coherent decisions and prioritize effectively (Correct answer)
It guarantees predictable delivery dates
It eliminates the need for Sprint Planning
It removes the need for stakeholder involvement

Correct answer: It provides a shared focus that helps the team make coherent decisions and prioritize effectively

A well-defined Product Goal aligns the team's efforts, making prioritization decisions clearer and Sprint Goals more purposeful.

Question 38: What is the primary purpose of a Product Vision in Scrum?

To outline a clear goal that guides the direction of product development. (Correct answer)
To define the specific tasks for the Scrum Team during each Sprint.
To provide detailed technical specifications for the Development Team.
To assign roles and responsibilities to stakeholders.

Correct answer: To outline a clear goal that guides the direction of product development.

The Product Vision serves as a foundational, long-term goal that articulates the product's purpose and desired future state. It provides a clear, unifying direction for the entire Scrum Team and stakeholders. This shared understanding ensures that all development efforts are aligned towards achieving a common, valuable outcome.

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

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

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 40: 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?

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

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 41: What is story point estimation, and how does it support release forecasting?

A tool used by project managers to set deadlines
A precise measure of hours to complete a task
A relative complexity measure used to estimate item size and forecast velocity-based delivery timelines (Correct answer)
An exact financial cost estimate for each feature

Correct answer: A relative complexity measure used to estimate item size and forecast velocity-based delivery timelines

Story points capture relative complexity, and when combined with team velocity, they allow the Product Owner to create rough release timeline forecasts.

Question 42: What is the most important metric for a Product Owner to track to ensure the team is maximizing value delivery?

Burndown chart
Return on Investment (ROI) (Correct answer)
Number of completed user stories
Velocity

Correct answer: Return on Investment (ROI)

While velocity and burndown charts track progress and output, Return on Investment (ROI) is the most direct metric for a Product Owner to assess value delivery. ROI measures the financial benefit generated relative to the cost of the investment. This directly reflects how effectively the Scrum Team is maximizing the value of the product in terms of business outcomes.

Question 43: What should the Product Owner prepare before each Sprint Review?

A performance review of each Developer's Sprint contributions
A formal presentation of completed features for management
A release approval document for stakeholders to sign
An updated Product Backlog reflecting current priorities and an understanding of what was accomplished vs. the Sprint Goal (Correct answer)

Correct answer: An updated Product Backlog reflecting current priorities and an understanding of what was accomplished vs. the Sprint Goal

The Product Owner should arrive at the Sprint Review with a current, prioritized backlog and clear context about Sprint Goal achievement to facilitate productive stakeholder discussions.

Question 44: Who is responsible for ensuring that Product Backlog items are refined enough for Sprint Planning?

Stakeholders
The Product Owner, with Developers' input during refinement (Correct answer)
The Developers alone
The Scrum Master

Correct answer: The Product Owner, with Developers' input during refinement

The Product Owner is accountable for backlog readiness but works collaboratively with Developers during refinement sessions to ensure items are clear and estimated.

Question 45: What is the Product Owner's role in the Sprint Retrospective?

They do not attend the Retrospective
They only attend to approve process changes
They facilitate the Retrospective instead of the Scrum Master
They participate as a full Scrum Team member to inspect and improve team processes (Correct answer)

Correct answer: They participate as a full Scrum Team member to inspect and improve team processes

The Product Owner is a full member of the Scrum Team and participates in Retrospectives to inspect collaboration, processes, and interactions for improvement.

Question 46: When two backlog items have similar business value but different risk profiles, which factor should most strongly influence a Product Owner's prioritization decision?

Which feature was originally requested earliest in the backlog history
Which feature carries lower technical risk and can therefore be delivered sooner and more predictably (Correct answer)
Which feature has the greater number of story points
Which feature is supported by the largest number of stakeholders

Correct answer: Which feature carries lower technical risk and can therefore be delivered sooner and more predictably

When value is equal, lower technical risk reduces uncertainty and enables faster, more predictable delivery, making it the rational tiebreaker in prioritization.

Question 47: Which of the following approaches can help a Product Owner maximize the value delivered by the Scrum team?

Asking the team to increase their velocity.
Focusing on building features that deliver business outcomes quickly. (Correct answer)
Releasing all product features at once at the end of the project.
Adding more developers to the team to increase output.

Correct answer: Focusing on building features that deliver business outcomes quickly.

Maximizing value in Scrum involves delivering tangible business outcomes frequently and iteratively. Focusing on building features that quickly achieve desired business outcomes allows for early feedback, validation, and adaptation. This ensures that the team's efforts are consistently directed towards what truly adds value, rather than just increasing output or delaying releases.

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

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

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 49: What is the relationship between product metrics and Product Backlog prioritization?

Backlog order is set by stakeholders; metrics are a separate concern
Metrics are reviewed annually and rarely affect daily prioritization
Metrics provide empirical evidence that informs ordering decisions, ensuring high-value work is prioritized (Correct answer)
Metrics are used only to report to management, not for backlog decisions

Correct answer: Metrics provide empirical evidence that informs ordering decisions, ensuring high-value work is prioritized

Product metrics make value visible, enabling the Product Owner to order the backlog based on evidence rather than opinion, assumption, or politics.

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

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

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 51: Who decides which Product Backlog items are included in a Sprint?

The Developers, with input from the Product Owner (Correct answer)
The stakeholders
The Product Owner alone
The Scrum Master

Correct answer: The Developers, with input from the Product Owner

Developers select which items they can complete in a Sprint, though the Product Owner communicates priority and value.

Question 52: Who is accountable for defining and communicating the Product Goal?

The Product Owner (Correct answer)
Senior management
The Scrum Master
The Developers

Correct answer: The Product Owner

The Product Owner is accountable for defining and communicating the Product Goal as part of their overall accountability for product value.

Question 53: What happens to undone work at the end of a Sprint?

It is cancelled and must be re-written from scratch
It is returned to the Product Backlog for the Product Owner to re-order (Correct answer)
The team must complete it in overtime before the Sprint ends
It is automatically moved to the next Sprint Backlog

Correct answer: It is returned to the Product Backlog for the Product Owner to re-order

Undone Sprint Backlog items are returned to the Product Backlog, where the Product Owner can re-evaluate their priority relative to other work.

Question 54: Where is the Product Goal documented in Scrum?

In the Product Backlog (Correct answer)
In the Scrum Master's report
In the project charter
In the Sprint Backlog

Correct answer: In the Product Backlog

The Product Goal is part of the Product Backlog; the backlog exists to help achieve the Product Goal.

Question 55: 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 defines it independently and imposes it on Developers
The PO understands it and uses it to determine whether an Increment is truly releasable (Correct answer)

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.

Question 56: Which statement best describes the Sprint Goal?

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

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 57: Why is it important for the Product Owner to attend the Sprint Review?

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

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 58: In Scrum, who holds ultimate accountability for the ordering and prioritization of the Product Backlog?

The Scrum Master, who facilitates all backlog ceremonies
The Product Owner, who is responsible for maximizing product value (Correct answer)
Key stakeholders, who fund the product development effort
The Development Team, who must execute the work

Correct answer: The Product Owner, who is responsible for maximizing product value

The Scrum Guide clearly assigns the Product Owner sole accountability for Product Backlog ordering; stakeholders may influence but the Product Owner retains final authority.

Question 59: How should a Product Owner communicate urgency for a particular feature to Developers?

By ordering it high in the Product Backlog and explaining the business value during Planning (Correct answer)
By requesting overtime work
By escalating through the Scrum Master
By setting a deadline on each task

Correct answer: By ordering it high in the Product Backlog and explaining the business value during Planning

The Product Owner communicates urgency through backlog ordering and explaining business context, allowing Developers to understand and respond appropriately.

Question 60: During Sprint Planning, what should the Product Owner be prepared to explain to Developers?

The daily schedule for the Sprint
The exact technical implementation approach
The why behind the highest-priority backlog items (Correct answer)
The release date for each feature

Correct answer: The why behind the highest-priority backlog items

The Product Owner explains the purpose and value behind prioritized items so Developers understand the 'why' and can make good implementation decisions.

Question 61: How often should the Product Owner communicate the Product Vision to the Scrum Team?

During every Daily Scrum.
Continuously throughout the project to ensure alignment. (Correct answer)
Only when significant changes occur.
Only at the beginning of the project.

Correct answer: Continuously throughout the project to ensure alignment.

The Product Vision acts as the guiding star for the product, and its continuous communication ensures everyone on the Scrum Team remains aligned with the overarching goal. Regular reinforcement helps maintain focus, informs decision-making, and ensures that the team's efforts consistently contribute to the product's strategic direction. This prevents divergence and keeps the team working towards a shared understanding of success.

Question 62: 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 is used only to measure team performance
It replaces the need for separate release planning activities
It is a formal release gate that must be passed before any release

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 63: How can the Product Owner ensure that the Product Vision remains relevant throughout the development process?

Regularly gather feedback from stakeholders and customers to refine the vision as needed. (Correct answer)
Update the Product Vision after each Sprint Review.
Stick to the original Product Vision, regardless of market changes.
Let the Scrum Team take ownership of the Product Vision after development starts.

Correct answer: Regularly gather feedback from stakeholders and customers to refine the vision as needed.

The product environment is dynamic, and the Product Vision must evolve to remain relevant. Regularly gathering feedback from stakeholders and customers provides crucial insights into changing market conditions, user needs, and business priorities. This continuous feedback loop allows the Product Owner to inspect and adapt the vision, ensuring the product continues to deliver maximum value.

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

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
A daily build created by Developers
A document describing planned features for the next quarter

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 65: Why is it important for a Product Owner to set baseline metrics before a release?

To comply with Scrum process documentation requirements
To enable meaningful before-and-after comparison that validates whether the release achieved its intended value (Correct answer)
To measure individual Developer contribution to product outcomes
To satisfy stakeholder reporting requirements only

Correct answer: To enable meaningful before-and-after comparison that validates whether the release achieved its intended value

Baseline metrics establish a benchmark, allowing the Product Owner to objectively assess whether a release achieved its value hypothesis after deployment.

Question 66: What is the purpose of product backlog refinement in the context of release forecasting?

To eliminate items the team cannot complete
To ensure items are well understood and estimated so the PO can forecast more accurately (Correct answer)
To assign tasks to Developers for the upcoming Sprint
To finalize the release date with stakeholders

Correct answer: To ensure items are well understood and estimated so the PO can forecast more accurately

Refinement improves the clarity and estimation accuracy of backlog items, enabling more reliable forecasting for release planning.

Question 67: What happens if the Product Owner is unavailable during Sprint Planning?

Developers proceed without PO input
The Sprint is postponed
This is a significant risk; the PO must attend or delegate an informed representative (Correct answer)
The Scrum Master assumes PO responsibilities

Correct answer: This is a significant risk; the PO must attend or delegate an informed representative

Sprint Planning requires PO input on priorities and acceptance criteria; absence is a risk that must be mitigated through delegation or rescheduling.

Question 68: How does the Product Owner contribute to the Sprint Goal?

The PO writes the Sprint Goal alone
The PO proposes a Sprint Goal based on backlog priorities, which the Scrum Team then refines (Correct answer)
The Scrum Master defines the Sprint Goal
The Developers set the Sprint Goal independently

Correct answer: The PO proposes a Sprint Goal based on backlog priorities, which the Scrum Team then refines

The Product Owner proposes a Sprint Goal aligned with business value, and the whole Scrum Team collaborates to finalize it during Sprint Planning.

Question 69: What does 'actionable metric' mean for a Product Owner?

A metric that directly informs a decision or triggers a specific response when it changes (Correct answer)
A metric that measures team velocity over multiple Sprints
A metric tracked automatically by product analytics tools
A metric that executives can present in board meetings

Correct answer: A metric that directly informs a decision or triggers a specific response when it changes

Actionable metrics are ones where a change in the number tells the Product Owner what to do next, unlike vanity metrics that inform no specific action.

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

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
It is optional if the team has a strong testing culture

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 71: Why might a Product Owner choose to release a product with known defects?

Because the value of early market feedback outweighs the risk of known, low-severity defects (Correct answer)
Because the Definition of Done allows defects by default
Because Developers are not accountable for quality
Because stakeholders demanded it regardless of quality

Correct answer: Because the value of early market feedback outweighs the risk of known, low-severity defects

In some contexts, the learning value of early release outweighs the cost of known minor defects, but this is a deliberate, informed product decision with explicit risk acceptance.

Question 72: 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)
Resolve all technical debt before adding new features
Ignore it since it is a Developer concern only
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 73: During Sprint Planning, how should the Product Owner handle conflicting stakeholder priorities?

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

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 74: How does competitive analysis support a Product Owner's strategy?

It replaces the need for user research
It informs differentiation decisions and helps identify market gaps and opportunities (Correct answer)
It dictates exactly which features must be built
It is only relevant at product launch

Correct answer: It informs differentiation decisions and helps identify market gaps and opportunities

Competitive analysis helps the Product Owner understand the market landscape, enabling smarter differentiation and value positioning decisions.

Question 75: How should a Product Owner measure the success of a newly released feature?

By asking the Scrum Master to evaluate team performance
By measuring team velocity before and after the release
By counting the number of lines of code added
By tracking adoption, usage, and outcome metrics against pre-defined success criteria (Correct answer)

Correct answer: By tracking adoption, usage, and outcome metrics against pre-defined success criteria

Feature success should be measured against pre-defined outcome metrics like adoption rate, user behavior change, or business impact — not activity metrics.

Question 76: Why is it important for a Product Owner to understand business models?

To take over financial management from executives
To replace stakeholder input in backlog planning
To set pricing for the product independently
To make prioritization decisions that align with how the product creates, delivers, and captures value (Correct answer)

Correct answer: To make prioritization decisions that align with how the product creates, delivers, and captures value

Understanding the business model helps the Product Owner prioritize work that maximizes revenue, reduces cost, or improves customer satisfaction in ways that sustain the business.

Question 77: 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 78: Can a Product Owner cancel a Sprint? When is this appropriate?

Yes, at any time for any business reason
Yes, if the Sprint Goal becomes obsolete (Correct answer)
No, only the Scrum Master can cancel a Sprint
No, Sprints can never be cancelled

Correct answer: Yes, if the Sprint Goal becomes obsolete

Only the Product Owner can cancel a Sprint, and this is appropriate when the Sprint Goal has become obsolete due to changing circumstances.

Question 79: In Karl Wiegers' 'Relative Weighting' prioritization technique, features are scored by comparing:

The chronological history of when each feature was first requested
The relative benefit if included versus the relative penalty if excluded (Correct answer)
The development team's technical familiarity with each feature area
The number of stakeholders who requested each feature

Correct answer: The relative benefit if included versus the relative penalty if excluded

Wiegers' technique assigns a priority percentage to each feature by weighing its expected benefit against the business pain incurred if it is omitted, producing a relative ranking.

Question 80: What is the commitment associated with the Product Backlog?

The Product Goal (Correct answer)
The Definition of Done
The Sprint Goal
The Release Plan

Correct answer: The Product Goal

The Product Goal is the commitment for the Product Backlog, providing the long-term direction the backlog is designed to achieve.

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