Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
A Product Owner is needed for every:
(choose the best answer)
The Product Owner is the sole person accountable for managing the Product Backlog and ensuring the value of the work the Scrum Team performs. The Product Owner is one person, not a committee.The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item's priority must address the Product Owner1.The Product Owner is responsible for the product and its outcome2.
A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers.A product could be a physical product, a software product, a service, a project, or something else3.A product has a product vision, which is the overarching goal of the product, the reason for creating it, and the impact it should have on its customers and users4.
A portfolio is a collection of products or projects that are aligned with a strategic goal or an organizational unit5. A program is a group of related projects or products that are managed in a coordinated way to obtain benefits and control not available from managing them individually. A portfolio or a program may have a portfolio or program manager, who is responsible for overseeing the alignment, prioritization, and governance of the portfolio or program . However, these roles are not equivalent to the Product Owner role, as they do not have the same accountabilities and authorities as the Product Owner.
Therefore, the correct answer is that a Product Owner is needed for every product, not for every portfolio or program.Reference:1:Scrum Guide2:Understanding and Applying the Scrum Framework3:Managing Products with Agility4: [Product Vision]5: [Portfolio] : [Program] : [Portfolio Management] : [Program Management]
A separate Product Backlog is needed for every:
(choose the best answer)
According to the Professional Scrum Product Owner II certification guide1, a Product Backlog is an ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. The Product Backlog is owned by the Product Owner, who is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Therefore, a separate Product Backlog is needed for every product, not for every Scrum Team, portfolio, program, or all of the above.Multiple Scrum Teams can work on the same product and share the same Product Backlog2.A portfolio or a program may consist of multiple products, each with its own Product Backlog3.Reference:1: Professional Scrum Product Owner II Certification | Scrum.org2: What is a Product Backlog?| Scrum.org3: Product Backlog Explained [+ Examples] | Atlassian
What activities would a Product Owner typically undertake in the phase between the end of the
current Sprint and the next Sprint's Sprint Planning?
(choose the best answer)
If a Scrum Team uses Product Backlog refinement, when should it occur?
(choose the best two answers)
Product Backlog refinement is an ongoing activity that can occur at any time during a Sprint, as needed. The Product Owner and Developers collaborate on this task, ideally in advance of the upcoming Sprint to ensure clarity and readiness of the work . If refinement has not been done in preceding Sprints, it should be done in the current Sprint to maintain the flow of valuable work (E).This approach is consistent with the Scrum principle of continuous improvement and the iterative, incremental nature of Scrum12.
When should the Product Owner update the project plan?
(choose the best answer)
In Scrum, there is no separate artifact called a project plan. The Product Backlog is the plan for the product development, and it contains all the features, requirements, enhancements, and fixes that are needed to deliver a valuable product. The Product Backlog is not a static or fixed document, but rather an emergent and dynamic one. It is constantly updated and refined by the Product Owner and the Developers as they learn more about the product, the users, the market, and the technology. The Product Backlog is updated whenever new information and insights emerge, which can happen at any time during the product development process. Therefore, option C is the best answer.
Option A is not correct because the Daily Scrum is not a status meeting, but rather a time-boxed event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. The Product Owner does not need to update the Product Backlog after the Daily Scrum, unless there is a significant change in the product vision, strategy, or value proposition that affects the Product Backlog items.
Option B is not correct because the Sprint Retrospective is not a time to update the Product Backlog, but rather a time-boxed event for the Scrum Team to inspect their way of working and identify potential improvements. The Product Owner does not need to update the Product Backlog before the Sprint Retrospective, unless there is a need to communicate a change in the Product Goal or the product roadmap that affects the Product Backlog items.
Option D is not correct because the Sprint Planning is not a time to know how much work will have to be done in the Sprint, but rather a time-boxed event for the Scrum Team to collaborate on selecting and planning the Product Backlog items that will deliver the Sprint Goal. The Product Owner does not need to update the Product Backlog before the Sprint Planning, unless there is a need to reorder or clarify the Product Backlog items that are the most valuable and relevant for the upcoming Sprint.Reference:
Professional Scrum Product Owner II Assessment
Understanding and Applying the Scrum Framework
Managing Products with Agility
What is a Product Backlog?
Product Backlog Explained
Every Scrum Team must have a Product Owner and Scrum Master.
(Choose the best answer)
According to the Scrum Guide (2020), every Scrum Team must have a Product Owner and a Scrum Master. These roles are essential for the team's success in delivering value.
However, Scrum does not strictly mandate that a Scrum Master or Product Owner must be 100% dedicated to a single team. Their effectiveness and participation can vary based on the context, but their involvement significantly influences the team's performance.
Analysis of Each Option:
Option A (Correct Answer):
The Scrum Team's performance can be affected by how actively the Product Owner and Scrum Master engage with the team.
The Product Owner is responsible for maximizing the product's value, which requires close collaboration with stakeholders and the Development Team. If they are not actively involved, it can lead to unclear priorities and delays.
The Scrum Master ensures that Scrum is understood and enacted properly. A disengaged Scrum Master may result in impediments going unresolved and a lack of continuous improvement.
This aligns with the Scrum Guide, which states that both roles must ensure effective communication and support the team throughout the Sprint.
Option B (Incorrect):
Saying 'No' implies that a Scrum Team does not necessarily require a Product Owner and Scrum Master, which contradicts the Scrum Guide.
The Scrum Guide (2020) clearly states that each Scrum Team consists of a Scrum Master, Product Owner, and Developers.
Option C (Incorrect):
While dedication is beneficial, the Scrum Guide does not require the Product Owner and Scrum Master to be 100% dedicated to only one team.
In large organizations or scaling frameworks (such as Scrum@Scale or SAFe), a Scrum Master may serve multiple teams, and a Product Owner may manage multiple related products or backlogs.
What matters is effectiveness, not exclusivity---as long as they fulfill their responsibilities, their time allocation is flexible.
Key Takeaways:
Every Scrum Team must have a Product Owner and Scrum Master (Scrum Guide, 2020).
Their level of participation affects the team's success, but they do not have to be 100% dedicated to a single team.
The Scrum Guide does not require exclusivity, but both roles should be involved enough to fulfill their responsibilities effectively.
Scrum Guide 2020 -- 'The Scrum Team consists of a Scrum Master, a Product Owner, and Developers.'
Scrum Roles and Responsibilities -- The impact of Product Owner and Scrum Master engagement on team performance.
Scaling Scrum (Scrum@Scale, SAFe) -- Product Owners and Scrum Masters can work across multiple teams, depending on the organizational structure.
The smallest product Increment that is valuable enough to release is one that:
(choose the best answer)
The smallest product Increment that is valuable enough to release is one that delivers a single new or improved outcome for the customers or users of the product.This is because the outcome is the ultimate measure of value, not the output or the features1.An outcome is a change in behavior, attitude, or situation that results from using the product2.An outcome can be achieved by delivering a single feature, fixing a defect, or improving an existing functionality, as long as it meets the Definition of Done and the Sprint Goal3. Therefore, the best answer is A.
The other options are not correct because:
B . Adds a new feature.This is not a sufficient condition, as a new feature may not deliver a valuable outcome if it is not aligned with the product vision, the customer needs, or the market conditions4.
C . Fixes at least one defect.This is not a necessary condition, as a defect may not affect the value of the product if it is minor, rare, or irrelevant to the customer5.
D . Delivers all ''must do'' Product Backlog items. This is not a realistic condition, as the Product Backlog is a dynamic and emergent artifact that changes based on feedback, learning, and discovery.There is no fixed set of ''must do'' items that can guarantee the delivery of value.Reference:1: Outcome vs.Output,2: What is an Outcome?,3: The Definition of Done,4: Feature vs.Outcome,5: Defect vs. Value, : The Product Backlog
Exam domains verified against: Official Scrum PSPO-II exam guide, last checked October 2026.
Examine the theoretical foundations of Scrum and its practical implementation across individual, team, and organizational levels. Focus on how Scrum principles drive productivity, efficiency, and continuous improvement through adaptable practices.
This portion of the exam focuses on key aspects of agile product management. It covers techniques for forecasting and planning releases, developing and communicating product vision, maximizing product value, and effective product backlog management. Additionally, it addresses the alignment of product development with business strategy and the crucial skill of managing stakeholders and customers in an agile environment.
This section delves into the broader organizational aspects of agile adoption. It examines how organizational design and culture can be shaped to support agile practices, explores strategies for building and managing agile portfolios, and introduces evidence-based management as a means to guide decision-making and measure organizational progress in agile transformations.
Common questions about the exam itself
