PSPO-I Scrum Exam Lab Questions

In Scrum, the Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. One of the primary ways the Product Owner does this is by managing the Product Backlog, which includes clearly expressing Product Backlog items, ordering the items to best achieve goals and missions, and ensuring that the Product Backlog is visible, transparent, and clear to all. This means that the Product Owner has the final authority on the order of items in the Product Backlog, as they are best positioned to understand the strategic and market value of the work to be done.

The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) study materials, specifically the sections on ‘Managing Products with Agility’ and ‘Understanding and Applying the Scrum Framework’, which outline the accountabilities of the Product Owner in managing the Product Backlog

The two best responses to a Project Manager who has raised concerns about progress and money spent are:

Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access. This helps communicate what is needed to improve the product, what is planned for each Sprint, and what has been done so far. It also helps align expectations and priorities among different stakeholders.

Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint. This helps address any issues or risks that may affect the delivery of value and the achievement of the Sprint Goal. It also helps provide feedback and adaptation based on the empirical evidence and data.

Other options, such as showing the Earned Value Analysis (EVA) report, Scrum does not have Project Managers so disregard their concerns, or sharing the last stakeholder briefing document prepared by the Product Owner, are not the best responses as they do not reflect how to effectively collaborate and communicate with the Project Manager or how to apply the Scrum values and principles.

The value delivered by a product can not be determined by revenue alone, because:

Revenue is only one aspect of value, and it may not reflect the true impact or benefit of the product for the stakeholders, the users, and the society. For example, a product may generate high revenue, but also cause environmental damage, ethical issues, or customer dissatisfaction.

Value is a subjective and relative concept, and it may vary depending on the context, the perspective, and the criteria of the evaluation. For example, a product may have different value for different segments of customers, or for different markets or regions.

Value is dynamic and emergent, and it may change over time due to various factors, such as feedback, competition, innovation, or regulation. For example, a product may lose its value as new alternatives or solutions become available, or as customer needs or preferences evolve.

The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that " The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how). " 1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.

1: The Scrum Guide2, page 15

2: The Scrum Guide