Free PSPO-II sample questions

Correct answer: Acknowledge the stakeholder's perspective and invite them to a collaborative session to discuss the Product Goal and review the upcoming items in the Product Backlog.

This approach demonstrates respect for the stakeholder while reinforcing the collaborative nature of Scrum. It turns a point of conflict into an opportunity for alignment. Rather than just defending past decisions, it focuses on future collaboration and transparency, inviting the stakeholder to be part of the solution and understand the trade-offs involved in maximizing value towards the Product Goal.

Correct answer: False

The Product Owner is *accountable* for effective Product Backlog management, which includes ensuring that items are clearly expressed. However, they are not necessarily responsible for *doing* all the work. The Product Owner can, and often should, delegate the writing of user stories and acceptance criteria to the Developers or collaborate with them on it. The key is accountability, not sole execution.

Correct answer: The Product Goal.

The Product Goal is the long-term objective for the Scrum Team. It provides context and direction for the Product Backlog and upcoming Sprints. By establishing a clear Product Goal, the Product Owner can help both the stakeholders and the Scrum Team understand how the work being done contributes to a larger, valuable objective, thus creating alignment and purpose.

Correct answer: Run a workshop with key stakeholders and some Developers to agree a Product Goal for the MVP and a small first slice that covers compliance risk and sales value.

A shared Product Goal for the MVP gives the conflicting stakeholders one objective to order work against. Agreeing on it with them and some Developers builds support and finds a small first slice that serves both groups.

Correct answer: Insufficient time is being spent on Product Backlog refinement.

Product Backlog refinement is the ongoing activity of adding detail, estimates, and order to items. When items are ambiguous and larger than anticipated, it's a strong indicator that refinement is not being done effectively. This leads to an inaccurate forecast during Sprint Planning and subsequent failure to meet the Sprint Goal. Effective refinement ensures that items at the top of the backlog are well-understood and ready for selection in a Sprint.

Correct answer: Present a burn-up chart showing a likely range of completion dates or a likely range of scope for the target date, based on historical data.

This approach is rooted in empiricism. It uses past performance (historical data) to project future outcomes. Presenting a range (the 'cone of uncertainty') is transparent about the inherent variability and risk in product development. It avoids making a false promise of a fixed scope and date, instead providing a probabilistic forecast that helps stakeholders make informed decisions while acknowledging uncertainty. It visualizes the trade-offs between scope, date, and cost.

Correct answers: Current Value (CV); Unrealized Value (UV)

Current Value is the value the product delivers today, such as customer satisfaction and revenue. It tells you how the product performs now.

Unrealized Value is the extra value the product could create if it met the needs of all potential customers. It shows the future potential, so it helps decide where to invest.

Correct answer: Courage

It takes courage to make difficult decisions that may be unpopular with influential stakeholders, especially when those decisions are based on evidence and are in the best interest of the product's value. The Product Owner shows courage by prioritizing value maximization over pleasing a single stakeholder.

Correct answer: The Product Owner role remains as one person, who is now accountable for a single Product Backlog that serves all five teams, requiring more emphasis on delegation and refinement.

In Nexus, and in Scrum generally, there is only one Product Owner for a product, regardless of the number of teams. This person is accountable for the single Product Backlog. To be effective at scale, this Product Owner must excel at communicating the Product Goal and vision, and delegating work related to Product Backlog management (like writing PBIs) to the Developers, while remaining accountable for maximizing value.

Correct answer: Explain that estimates are for the Developers to get a shared understanding of the work and to help with forecasting, not as a commitment, and then facilitate a collaborative refinement session.

This approach addresses the root of the team's concern: the misuse of estimates as commitments. By clarifying that estimates are a tool for the Developers' own planning and for creating empirical forecasts (not deadlines), the Product Owner builds trust. Facilitating collaborative refinement helps the team understand the work better, which naturally makes estimating easier and more valuable for them. The emphasis is on the outcome (shared understanding and forecasting ability) rather than the act of estimating itself.