Scrum Professional Scrum Product Owner II PSPO-II Exam Questions

Answer : C, E

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.

Answer : C

The Sprint Goal is a summary statement of the Sprint objective, which ideally has a cohesive theme. The Sprint Goal also gives the Scrum Team guidance and flexibility on how to achieve the objective. The Sprint Goal is crafted by the entire Scrum Team during the Sprint Planning, based on the Product Owner's proposal of the most valuable Product Backlog items and the Development Team's forecast of the work that can be done in the Sprint. The Product Owner collaborates with the team to write the Sprint Goal and defines it on the basis of the value being sought. The Product Owner does not define the scope or the solution for the Sprint, but rather the outcome and the benefit. The Product Owner also does not work with stakeholders to set the Sprint Goal, but rather represents their interests and needs. The Product Owner has a role in crafting the Sprint Goal, but not the sole responsibility for it.Reference:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

The Role of the Product Owner during the Sprint

Sprint Goal -- An Essential Ingredient in Scrum Recipe

Answer : A

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal1.The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a ''Done'' Increment2.The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum2. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal2.The Sprint Backlog is not a commitment to deliver a fixed scope of work, but rather a forecast of what the Developers believe they can do in the Sprint3.Therefore, the Sprint Backlog does not need to be fully defined during the Sprint Planning, but only enough so the Developers can create a realistic forecast of what they can do during the Sprint.Reference:1: Sprint Backlog,2: The Scrum Guide,3: Commitment vs. Forecast

Answer : A, B

Verified Answer: A, B

Very Very Short In the context of Scrum and the PSPO II guidelines, when there is uncertainty about customer needs or market desires, it is recommended to make smaller releases to allow for quicker feedback and adaptation (A), and to increase the focus on validating customer needs to ensure that the product development is aligned with what customers actually want (B). This approach is consistent with the principles of empiricism and agility, which emphasize the importance of transparency, inspection, and adaptation123.

Answer : A, D

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. A major part of that accountability is working with stakeholders and making sure the Scrum Team is focused on the most valuable work.

Why A is correct:

A Product Owner must actively engage with stakeholders and ensure transparency around the product. While the Scrum Guide does not prescribe a specific reporting style, it clearly places the Product Owner in the role of managing value, aligning stakeholder needs, and making sure the Product Backlog reflects what is most important. Communicating product direction, priorities, and progress to customers and stakeholders is a key part of that responsibility.

Why D is correct:

This is one of the strongest descriptions of Product Owner work. The Product Owner collaborates with customers and stakeholders to understand needs, determine value, and order the Product Backlog accordingly. The Product Owner is accountable for effective Product Backlog management, which includes developing and explicitly communicating Product Backlog items and ordering them to best achieve goals.

Why B is not the best answer:

The Scrum Guide does not require User Stories. Scrum only requires that Product Backlog items be clear enough and ordered appropriately. User Stories are a common technique, but they are not mandated by Scrum. Therefore, ''writing clear, transparent User Stories'' is not an official Product Owner duty as defined by Scrum.

Why C is incorrect:

The Product Owner should be available to support clarity and decision-making, but Scrum does not say the Product Owner should be with Developers all the time. Scrum promotes self-managing teams, and the Product Owner is one member of the Scrum Team, not a constant on-demand requirement clarifier sitting with Developers at all times.

2020 Scrum Guide -- Product Owner accountabilities: https://scrumguides.org/scrum-guide.html#product-owner

2020 Scrum Guide -- Product Backlog management: https://scrumguides.org/scrum-guide.html#product-backlog

===========

Answer : F

Scrum is a lightweight framework. It defines specific accountabilities, events, artifacts, and commitments, but it does not require any of the items listed in options A through E.

Why F is correct:

None of the listed practices or tools are required by Scrum.

Why A is incorrect:

A burndown chart is a common agile tracking technique, but Scrum does not require it. Teams may use it if helpful, but it is optional.

Why B is incorrect:

A feature burn-up chart is also optional. Scrum does not prescribe burn-up charts or any specific reporting chart.

Why C is incorrect:

Critical Path Analysis comes from traditional project management approaches and is not required by Scrum.

Why D is incorrect:

Refactoring is an excellent engineering practice and often very important for maintaining product quality, but it is not required by the Scrum framework itself. Scrum does not prescribe technical practices.

Why E is incorrect:

A Gantt chart is not required by Scrum. Scrum uses empiricism, iterative delivery, and adaptive planning rather than relying on predictive project scheduling tools as a requirement.

The Scrum Guide only mandates the framework elements of Scrum itself:

Scrum Team accountabilities

Scrum Events

Scrum Artifacts

Artifact Commitments

It does not require specific charts, project-planning tools, or engineering techniques.

2020 Scrum Guide -- Scrum framework overview: https://scrumguides.org/scrum-guide.html

2020 Scrum Guide -- Scrum Events: https://scrumguides.org/scrum-guide.html#events

2020 Scrum Guide -- Scrum Artifacts: https://scrumguides.org/scrum-guide.html#artifacts

===========

Answer : C

In Scrum, the Product Owner is responsible for maximizing the value of the product by understanding and addressing customer needs effectively. When faced with multiple customer segments using the product in different ways, the best approach is to market the product differently to each group rather than fragmenting the product into multiple versions or ignoring existing customers.

Option A (Evaluate building different products): While segmentation can sometimes justify creating multiple products, it adds complexity in development, maintenance, and resource allocation. Scrum focuses on delivering incremental value in a single product rather than splitting efforts across multiple versions unless there's a strong business case.

Option B (Do nothing and invest in future features): This is a risky and reactive approach. Ignoring existing customer groups and only investing in attracting new customers can lead to customer churn and dissatisfaction. A Product Owner should aim for continuous engagement with existing customers to ensure long-term success.

Option C (Keep a single product, but market differently to each group) [Correct Answer]: This aligns with Agile and Scrum principles because it allows the Product Owner to maintain a single product backlog while tailoring marketing messages for different user segments. It helps maximize value delivery without increasing complexity. Instead of fragmenting the product itself, communication and positioning strategies are adjusted to better resonate with different customer types.

Option D (Ensure each release has something for each group): While inclusivity in releases is valuable, forcing every release to cater to all groups can lead to inefficient backlog prioritization. Instead, the Product Owner should balance priorities based on value delivery and strategic goals rather than trying to satisfy all user segments in every release.

Scrum Guide 2020 -- Role of the Product Owner: ''The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.''

Scrum Product Ownership Best Practices -- Focus on a single Product Backlog and strategic prioritization based on value.

Agile Manifesto -- 'Responding to change over following a plan' (customer preferences should inform how a product is marketed, not necessarily how it is built).