Questions for the PSPO-II were updated on : Dec 01 ,2025
When determining the ordering of an item on the Product Backlog, what are some things a Product
Owner should consider?
(choose the best four answers)
A. Alignment with organizational strategy and goals.
B. The techniques the Developers will use to implement the item.
C. Risk. For example; business risk, market risk, or technology risk.
D. Alignment with other Product Backlog items.
E. Importance to users or customers.
A, C, D, E
Let's analyze each option to determine the best considerations for a Product Owner when ordering
A. Alignment with organizational strategy and goals.
This is a correct answer.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Business Strategy
The Product Backlog should reflect the overall business strategy and contribute to achieving
organizational goals.
Professional Scrum Competency: Managing Products with Agility - Product Vision
The Product Vision is guided by the organizational strategy. The Product Backlog ordering should help
realize that vision.
Additional Explanation: A Product Owner must ensure the product is strategically aligned,
maximizing the return on investment for the organization.
B . The techniques the Developers will use to implement the item.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Self-Managing Teams
The Developers are responsible for determining how they will implement Product Backlog items. The
Product Owner focuses on the what and why.
Additional Explanation: The Product Owner should trust the Developers' expertise in technical
implementation. While high-level technical feasibility might be a consideration, the specific
techniques used are within the Developers' domain.
C . Risk. For example; business risk, market risk, or technology risk.
Verification: This is a correct answer.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Evidence-Based Management
Identifying and mitigating risks is crucial for maximizing product value. Addressing high-risk items
early can prevent significant problems later.
Professional Scrum Competency: Managing Products with Agility - Business Strategy
Understanding and mitigating business and market risks is essential for strategic product
development.
Additional Explanation: Addressing high-risk items early (when appropriate) allows for early learning
and adaptation, reducing overall project risk.
D . Alignment with other Product Backlog items.
Verification: This is a correct answer.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning
Considering dependencies and relationships between Product Backlog items is essential for effective
release planning.
Professional Scrum Competency: Managing Products with Agility - Product Backlog Management
The Product Backlog should be ordered in a way that considers dependencies and logical groupings
of items to deliver coherent functionality.
Additional Explanation: Grouping related items or addressing dependencies early can improve
development efficiency and create more valuable increments.
E. Importance to users or customers.
Verification: This is a correct answer.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Stakeholders & Customers
Understanding and prioritizing based on user and customer needs is fundamental to delivering a
valuable product.
Professional Scrum Competency: Managing Products with Agility - Product Value
Delivering value to users and customers is the ultimate goal, and the Product Backlog ordering
should reflect this.
Additional Explanation: Focusing on user and customer value helps ensure that the most important
features are delivered first, maximizing user satisfaction and business impact.
In conclusion, the four best considerations for ordering the Product Backlog are: alignment with
organizational strategy and goals, risk, alignment with other Product Backlog items, and importance
to users or customers. These factors help the Product Owner maximize product value, manage risks,
and ensure the product aligns with business objectives and user needs, in accordance with the PSPO
II competencies.
Your stakeholders are very demanding and each of them has at least one feature that they say is
essential for the next release. As the Product Owner, you have validated that the feature requests are
all valid requests and would likely add value to your product. What should you do?
(choose the best answer)
C
Explanation:
Let's analyze each option and determine the best course of action for a Product Owner in this
situation, keeping in mind the PSPO II objectives and competencies:
C. Release when you can satisfy at least a single outcome, even though not all features are
implemented.
Verification: This is the correct answer.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Product Value
This option aligns with the principle of maximizing value by delivering value early and often.
It emphasizes focusing on valuable outcomes rather than just completing a list of features.
Professional Scrum Competency: Managing Products with Agility - Business Strategy
Releasing a product increment that provides value allows for faster feedback and learning, which can
inform future decisions and help to align the product with the overall business strategy.
Professional Scrum Competency: Managing Products with Agility - Stakeholders & Customers
While stakeholder management is important, focusing on delivering a valuable outcome is a better
way to manage expectations and build trust in the long term.
Scrum Guide: The Scrum Guide emphasizes the importance of delivering a "Done", usable, and
potentially releasable product Increment every Sprint. This aligns with the concept of releasing when
a valuable outcome is achieved.
Additional Explanation: By focusing on outcomes, the Product Owner can prioritize the most valuable
features that contribute to that outcome. This may mean that not all stakeholder requests are met in
the initial release, but it allows for delivering value sooner and adapting based on feedback.
A . Wait until all essential features are complete before releasing the product.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Product Value
This approach delays the realization of value and increases the risk of building the wrong thing.
Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning
Waiting for all features delays feedback and learning, making it difficult to adapt the product to
changing market conditions or user needs.
Scrum Guide: This contradicts the iterative and incremental nature of Scrum, where the goal is to
deliver value frequently.
B . Pick the two most influential stakeholders and satisfy their needs, then release.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Product Value
Prioritizing based on influence rather than value can lead to building the wrong product.
Professional Scrum Competency: Managing Products with Agility - Stakeholders & Customers
While stakeholder management is important, the Product Owner's primary responsibility is to
maximize product value, not to cater to the most influential stakeholders.
Additional Explanation: This approach can damage trust with other stakeholders and create a
political environment rather than a collaborative one.
D . Escalate to the steering committee to make the call.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Evolving the Agile Organization - Portfolio Planning
The Product Owner is empowered to make decisions about the product and should not routinely
escalate prioritization decisions.
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Self-Managing Teams
The Product Owner is accountable for maximizing the value of the product. Escalating to a steering
committee undermines this accountability.
Additional Explanation: This approach undermines the Product Owner's authority and can lead to
delays and inefficient decision-making.
In conclusion, the best approach is to release when a valuable outcome can be achieved, even if not
all requested features are implemented. This aligns with the principles of iterative development,
value maximization, and frequent feedback, all of which are core to Scrum and emphasized in the
PSPO II competencies.
When is the Sprint Backlog created?
(choose the best answer)
C
Explanation:
Let's break down why the correct answer is C and why the others are incorrect, referencing the
Professional Scrum Product Owner™ II (PSPO II) objectives and associated competencies:
C . During Sprint Planning.
Verification: This is the correct answer.
Explanation and Reference:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Scrum Events
Sprint Planning is the event where the Scrum Team collaboratively plans the work for the upcoming
Sprint. Creating the Sprint Backlog is a key part of this event.
Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning
The Sprint Backlog represents the team's forecast of what they believe they can deliver in the Sprint
to achieve the Sprint Goal. This forecasting occurs during Sprint Planning.
Scrum Guide: The Scrum Guide states, "The work to be performed in the Sprint is planned at the
Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team. [...] Sprint
Planning answers the following questions: What can be Done this Sprint? How will the chosen work
get done?" The answer to the second question results in the creation of the Sprint Backlog.
A . During the Sprint.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Scrum Events
While the Sprint Backlog can be updated during the Sprint as the Developers learn more, it is initially
created before the Sprint starts, during Sprint Planning.
Scrum Guide: The Scrum Guide says "The Sprint Backlog is a plan by and for the Developers. It is a
highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint
in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the
Sprint as more is learned. It should have enough detail that they can inspect their progress in the
Daily Scrum." This means that Sprint backlog is already created before sprint starts.
B . Prior to Sprint Planning.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Scrum Events
The Sprint Backlog is created during Sprint Planning through collaboration between the Developers
and the Product Owner. Before Sprint Planning, the Product Owner prepares a prioritized Product
Backlog, but this is not the Sprint Backlog.
Scrum Guide: The Sprint Backlog emerges from the discussion and negotiation that happens during
Sprint Planning. It is not pre-defined.
D . At the beginning of the project.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning
The Sprint Backlog is specific to each Sprint and is created at the beginning of each Sprint, not at the
beginning of the entire project.
Scrum Guide: Scrum is iterative and incremental. Planning the work for the entire project upfront is
not in line with Scrum principles. The Sprint Backlog is created anew during each Sprint Planning
event.
In conclusion, the Sprint Backlog is created during Sprint Planning, where the Scrum Team
collaboratively decides what work they will undertake in the upcoming Sprint and how they will
accomplish it, aligning with the PSPO II competencies and the Scrum Guide.
Why does a Scrum Team need a Sprint Goal?
(choose the best answer)
C
Explanation:
Let's break down why the correct answer is C and why the others are incorrect, referencing the
Professional Scrum Product Owner™ II (PSPO II) objectives and associated competencies:
C. The Scrum Team is more focused through a common yet specific goal.
Verification: This is the correct answer and aligns perfectly with the purpose of a Sprint Goal as
defined in the Scrum Guide and emphasized within the PSPO II competencies.
Explanation and Reference:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Empiricism
The Sprint Goal promotes transparency within the team about what they are trying to achieve during
the Sprint.
It provides a basis for inspection during the Sprint, allowing the team to adapt their plans based on
progress toward the Sprint Goal.
Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning
The Sprint Goal helps the team focus on achieving a specific, valuable outcome each Sprint.
It provides a basis for forecasting what can be achieved in the Sprint.
Professional Scrum Competency: Managing Products with Agility - Product Value
The Sprint Goal should be aligned with maximizing product value, providing a clear link between the
work done in the Sprint and the overall product vision.
Scrum Guide: The Scrum Guide states, "The Sprint Goal is an objective set for the Sprint that can be
met through the implementation of Product Backlog. It provides guidance to the Developers 1 on
why it is building the Increment. 2 [...] During Sprint Planning the Scrum Team also crafts a Sprint
Goal. The Sprint Goal is an objective set for the Sprint that can be met through the implementation
of Product Backlog." 3 This clearly emphasizes that the Sprint Goal provides focus and guidance.
A. A Sprint Goal ensures that all the Product Backlog items selected for the Sprint are implemented.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Empiricism
Scrum acknowledges that the plan for the Sprint (what Product Backlog items are chosen) may
change as the team learns more during the Sprint.
The Sprint Goal is the commitment, and while the team strives to complete the selected Product
Backlog items, the primary focus is on achieving the Sprint Goal, even if it means adapting the plan.
Scrum Guide: While the selected Product Backlog items are the initial plan, the Scrum Guide states,
"The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal."
This implies that the focus is on the coherent function (represented by the Sprint Goal), not
necessarily the completion of every single Product Backlog item.
B . A Sprint Goal only gives purpose to Sprint 1.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning
Every Sprint should have a Sprint Goal, providing ongoing direction and focus for the team.
Scrum Guide: The Scrum Guide explicitly states that a Sprint Goal is crafted during Sprint Planning,
implying that it's a necessary component of every Sprint, not just Sprint 1.
D . Sprint Goals are not valuable. Everything is known from the Product Backlog.
Verification: This is incorrect.
Explanation and Reference:
Professional Scrum Competency: Managing Products with Agility - Product Value
Sprint Goals are crucial for maximizing product value by providing focus and ensuring the team is
working on the most important aspects in each Sprint.
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the
Scrum Framework - Empiricism
The Sprint Goal provides context and purpose beyond the individual Product Backlog items. It helps
the team understand the "why" behind the work.
Scrum Guide: The Scrum Guide's emphasis on the Sprint Goal throughout the Sprint lifecycle
(planning, daily Scrum, review, retrospective) demonstrates its importance.
In conclusion, the Sprint Goal serves as a unifying and focusing mechanism for the Scrum Team,
promoting commitment to a specific outcome within each Sprint and is, therefore, a crucial element
for successful Scrum implementation, aligning perfectly with the PSPO II competencies and the
Scrum Guide.
Choose the two measurements which provide the best indicator to the Product Owner that
value is being delivered.
(choose the best two answers)
AD
Explanation:
According to the Professional Scrum Product Owner™ II (PSPO II) guidelines, the best indicators of
value delivery are those that reflect the product’s impact on customers and its usage in the market.
Customer satisfaction (Option A) is a direct measure of how well the product meets customer needs
and expectations.
High customer satisfaction is a strong indicator that the product is delivering
value1
.
Frequency of feature use (Option D) provides insights into which features are most valuable to users
by showing how often they are used.
This metric helps Product Owners understand user behavior
and prioritize features that deliver the most value1
.
On-time release trends (Option B) and velocity (Option C) are more about the process and efficiency
of the development team rather than direct indicators of value to the customer. Scope implemented
(Option E) measures the amount of work done but does not necessarily correlate with customer
value. Therefore, options A and D are the best choices for measuring value delivery as per the PSPO II
resources.
Given only the information in the following three statements:
. Product A has a greater potential market than Product B.
. Product A has lower customer satisfaction than Product B.
· Product B produces more revenue at the present time.
Which investment strategies should you consider for these two products?
(choose the best answer)
D
Explanation:
The Professional Scrum Product Owner™ II (PSPO II) emphasizes the importance of a strategic
approach to product management. According to the PSPO II resources, it is essential to:
Continually measure the impact of new investments or marketing efforts for both products (Option
A). This aligns with the PSPO II focus on evidence-based management and making decisions based on
empirical data.
Invest in Product A to increase its market share, customer satisfaction, and revenue (Option B). The
PSPO II materials suggest that a product with a greater potential market but lower customer
satisfaction requires attention to improve its standing and capitalize on its market potential.
Investigate an increase in marketing for Product B to grow its market share (Option C). Even though
Product B is currently generating more revenue, the PSPO II guides recommend exploring
opportunities to expand its market share, which could lead to even greater revenue.
Therefore, a comprehensive investment strategy that includes all the above actions is recommended
for managing products with agility, as per the PSPO II guidelines. This approach ensures that both
products are given the opportunity to maximize their market potential while maintaining a focus on
customer satisfaction and revenue growth. It’s a holistic strategy that considers the different
strengths and opportunities of each product.
Which of the following are advantages of a Product Goal that is well-understood by the Scrum
Team?
(choose the best three answers)
BCD
Explanation:
B. It helps the Scrum Team keep focus and they can check any decision against it: A well-understood
Product Goal acts as a powerful magnet that propels Scrum teams towards value delivery34
.
It
guides efforts, prioritizes activities, fosters collaboration, and ensures focus on delivering value to
customers34
.
C. It provides overall direction so Sprints will feel less like isolated pieces of work: The Product Goal
provides context to the Product Backlog2
.
It can be thought of as the ‘why’ we are doing all of this
work2
.
It can be used as the elevator pitch to 'what is the Scrum Team working on?'2
.
D. It makes it easier to inspect incremental progress at the Sprint Review: As each Increment is
produced, the Product incrementally moves toward the Product Goal2
.
How that value is
incrementally determined is very context-specific2
.
Who owns the Sprint Backlog?
(choose the best answer)
A
Explanation:
Self-Management: The Developers have autonomy over how they achieve the Sprint Goal. The Sprint
Backlog reflects their plan for turning Product Backlog items into a valuable Increment.
Accountability: The Developers are held accountable for delivering the Sprint Goal, and thus own the
detailed plan within the Sprint Backlog.
Scrum Guide: The Scrum Guide explicitly states, "The Sprint Backlog is a plan by and for the
Developers"
Which activities will a Product Owner likely engage in during a Sprint?
(choose the best three answers)
ABE
Explanation:
A. Reorder items in the Product Backlog: The Product Owner is responsible for ordering the Product
Backlog to maximize value12
.
B. Answer questions from the Developers about items in the current Sprint: The Product Owner is
engaged throughout the sprint, answering questions on how things are supposed to function &
look4
.
E. Gather information and opinions from stakeholders: Gathering information and opinions from
stakeholders is a key activity for the Product Owner, as it helps in understanding the value and
ordering the Product Backlog
Your stakeholders are very demanding and each of them has at least one feature that they say
is essential for the next release. As the Product Owner, you have validated that the feature
requests are all valid requests and would likely add value to your product. What should you do?
(choose the best answer)
C
Explanation:
Focus on Value: Scrum emphasizes delivering increments of value early and often. Each release
should focus on a clear outcome for users, even if it doesn't encompass every desired feature.
Iterative Approach: Releasing a smaller, focused increment lets you gather feedback, course-correct,
and add features incrementally based on what provides the most value.
Stakeholder Management: Involve stakeholders in the prioritization process, explaining the rationale
behind focusing on a specific outcome to gather input and secure buy-in.
Why should the Product Owner care that the Developers adhere to the Definition of Done?
(choose the best two answers)
AB
Explanation:
A. To influence the Total Cost of Ownership of the product: Adhering to the Definition of Done
ensures that the product meets the required quality standards, which can influence the Total Cost of
Ownership1
.
B. To have transparency into what has been done at the end of each Sprint: The Definition of Done
provides a shared understanding of what work was completed and what standards were met as part
of the Increment2
.
This creates transparency and allows the Product Owner to understand what has
been accomplished at the end of each Sprint12
.
When determining the ordering of an item on the Product Backlog, what are some things a
Product Owner should consider?
(choose the best four answers)
ABCD
Explanation:
A. Importance to users or customers: The value an item brings to the customer is a key factor in
ordering the Product Backlog1
.
B. Alignment with organizational strategy and goals: The Product Owner should consider how well an
item aligns with the organization’s strategy and goals1
.
C. Risk: Business, market, and technology risks are important considerations when ordering the
Product Backlog1
.
D. Alignment with other Product Backlog items: Dependencies and impact on other items in the
Product Backlog should be considered1
.
The Definition of Done is used to:
(choose the best three answers)
ACD
Explanation:
A. Increase transparency: The Definition of Done (DoD) creates transparency by providing everyone a
shared understanding of what work was completed and what standards were met as part of the
Increment1
.
C. Create a shared understanding of when work is complete: The DoD is a shared understanding
among the team members of when a product increment is ready for release2
.
D. Describe the work that must be done before the Sprint can be declared complete: The DoD
includes all of the characteristics and standards an Increment needs to meet in order to be
released1
.
Once the Definition of Done is met, the Increment is Done and can be delivered1
.
Who is accountable for maintaining and communicating the Product Goal?
(choose the best answer)
A
Explanation:
The Product Owner is accountable for maintaining and communicating the Product Goal.
This
responsibility includes ensuring that the goal is visible to everyone and provides direction and
purpose for the Scrum Team and its stakeholders
Which of the following might be considered when ordering Product Backlog items?
(choose all that apply)
ABCDE
Explanation:
According to the PSPO II guide and Scrum.org competencies, when ordering Product Backlog items, a
Product Owner should consider various factors to maximize the value of the work done by the Scrum
Team. These factors include:
A. Dependencies to other products: Recognizing dependencies to other products is crucial for the
Product Owner to ensure that the Scrum Team is working on items that can be completed and
deliver value without being blocked by external dependencies.
B. Value of Product Backlog items: The primary role of a Product Owner is to maximize the value
delivered by the Scrum Team, and ordering items based on their value is a fundamental aspect of this
responsibility.
C. Dependencies between Product Backlog items: Understanding and managing dependencies
between Product Backlog items helps in planning Sprints more effectively, ensuring that the team is
working on items in a logical sequence.
D. Cost of delay: The cost of delay is a critical economic factor that influences the ordering of Product
Backlog items. Items that would result in a higher cost if delayed should be prioritized.
E. Cost of implementation: While value maximization is the goal, the cost of implementation cannot
be ignored. Balancing the cost and the expected value is essential for effective Product Backlog
management.
These considerations are in line with the Scrum.org Professional Scrum competencies, particularly
under 'Managing Products with Agility', where it's emphasized that Product Owners should have a
deep understanding of market value, product feasibility, and the importance of making trade-offs to
maximize value.