PSPO-I Sample Questions & Answers

In Scrum and agile product development, 'value' is not a single, universal metric. It is determined by the Product Owner for their product and context. It can encompass a wide range of factors, including financial return (ROI), customer satisfaction (NPS), increased market share, reduced risk, employee happiness, and the value of learning through experimentation. The Product Owner's job is to synthesize these factors to maximize the overall value delivered.

The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint, which includes meeting the Definition of Done. While the Developers are required to conform to the DoD and the Scrum Master coaches the team in its importance, the issue of consistently failing to meet it is a whole-team problem. It should be inspected during the Sprint Retrospective by the entire Scrum Team to identify the root cause and create a plan for improvement.

A release burn-up chart typically has two lines. The bottom line tracks the cumulative work completed over time (the 'burn-up'). The top line represents the total scope of the work for the release. This top line can move up or down as scope is added or removed, which is a key advantage of the burn-up chart over a burn-down chart as it visualizes scope changes. The distance between the two lines shows the remaining work.

The Scrum Guide 2020 introduced commitments for each artifact to enhance transparency and focus. The Product Goal is the commitment for the Product Backlog. It describes a future state of the product and serves as a long-term target for the Scrum Team. The Product Backlog is the emergent, ordered list of what is needed to achieve the Product Goal.

The Scrum Guide states that if the work turns out to be different than expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal. Adaptation should happen as soon as new information is learned to minimize deviation. Waiting for a formal event like the Daily Scrum can delay this crucial conversation. The goal is to preserve the Sprint Goal, and this often requires adjusting the 'what' (the Sprint Backlog items) to achieve the 'why' (the Sprint Goal).

Net Promoter Score (NPS) is a widely used market research metric that asks respondents to rate the likelihood that they would recommend a company, product, or a service to a friend or colleague. It is a direct measure of customer satisfaction and loyalty. Velocity and Story Points are measures of output, not outcome or value, and are used by the Developers for forecasting. Total Cost of Ownership (TCO) is a financial estimate to help determine the direct and indirect costs of a product, not a measure of customer satisfaction.

While Openness is also relevant (sharing the information), the act of delivering difficult news to powerful stakeholders, which goes against their desires, requires Courage. It is the courage to do the right thing and be transparent about reality, even when it's uncomfortable. This upholds the principles of empiricism and builds trust with stakeholders in the long run.

The Sprint Review's purpose is to inspect the outcome of the Sprint and determine future adaptations. It is a collaborative working session where the Scrum Team and stakeholders discuss progress toward the Product Goal and decide what to do next. The most tangible outcome for the Product Owner is an updated Product Backlog that incorporates stakeholder feedback and new opportunities, ensuring the next Sprint will focus on the most valuable work.

In complex environments, detailed upfront plans are unreliable. Scrum is founded on empiricism, which means making decisions based on what is known. David should use the team's observed performance to create a more realistic forecast. The conversation with stakeholders should shift from 'Will we get everything?' to 'What is the most valuable subset we can get by the holiday?'. This approach is transparent, manages risk, and ensures the team focuses on maximizing value within the existing constraints. It treats the date as a constraint and scope as negotiable, which is a key agile principle.