Scrum Professional Scrum Product Owner I PSPO-I Exam Questions

Answer : B

The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that 'The Developers are required to conform to the Definition of Done, as defined by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.'1 This means that the Product Owner does not have the final say over the Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.

1: The Scrum Guide2, page 14

2: The Scrum Guide

Answer : A, B, C

The Product Owner orders the Product Backlog items according to various criteria, such as:

The value of Product Backlog items. The Product Owner aims to maximize the value of the product and the work of the Scrum Team. Therefore, they prioritize the items that deliver the most value to the stakeholders and the users, considering factors such as customer satisfaction, market share, revenue, social impact, etc.

The dependencies between Product Backlog items. The Product Owner tries to minimize the dependencies between items, as they may create complexity, uncertainty, and risk. Therefore, they order the items in a way that reduces or eliminates the dependencies, or resolves them as early as possible.

The dependencies to other products. The Product Owner also considers the dependencies that the product has to other products, such as platforms, frameworks, libraries, services, etc. Therefore, they order the items in a way that aligns with the availability and compatibility of those products.

Scrum Guide 2020, page 11: ''The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood.''

Scrum Guide 2020, page 11: ''The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions.''

Scrum Guide 2020, page 11: ''Higher ordered Product Backlog items are clearer and more refined than lower ordered ones.''

Answer : D

A Sprint is a time-boxed period when a Scrum Team works to complete a set amount of work that delivers value to the customer1. A Sprint concludes when the time-box expires, regardless of whether all the tasks, Product Backlog items, or Definition of Done are completed or not23. The Product Owner has the authority to cancel a Sprint if they determine that the Sprint Goal is obsolete or the work done is no longer valuable1. Therefore, the Product Owner decides when enough has been delivered to meet the Sprint Goal, and the Sprint ends accordingly.

Answer : B

A Product Owner is not the same thing as a traditional Project Manager. A Product Owner is a role in Scrum, a framework for developing, delivering, and sustaining complex products. A Project Manager is a role in traditional project management, a discipline for planning, executing, and controlling projects.

A Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.

A Project Manager is accountable for delivering the project within the predefined scope, time, and cost constraints. The Project Manager is responsible for defining and managing the project plan, resources, risks, issues, and dependencies. The Project Manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.

Some of the main differences between a Product Owner and a Project Manager are:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html

Product Owner: https://www.scrum.org/resources/what-is-a-product-owner

Project Manager: https://www.pmi.org/about/learn-about-pmi/what-is-project-management

Answer : B

The Developers are the people in the Scrum Team who are accountable for creating a ''Done'' Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is used to assess when work is complete on the product Increment.

The amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning depends on the Definition of Done. The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum.

The Developers must ensure that each Product Backlog item they complete during a Sprint meets the Definition of Done. This means that they must perform all the necessary tasks and activities to deliver a high-quality product functionality that is usable, valuable, and potentially releasable. This may include analysis, design, development, testing, documentation, integration, deployment, or any other aspects that contribute to the quality and usability of the product.

The other options are not valid or relevant measures for the amount of work required of the Developers to complete a Product Backlog item. They are either too vague, arbitrary, or unrealistic. They are:

As much as they can fit into the Sprint, with remaining work deferred to the next Sprint: This is a too vague and unrealistic measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the timebox or scope of the Sprint. It may lead to incomplete or unfinished work, technical debt, or scope creep.

All development work and at least some testing: This is a too arbitrary and insufficient measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the Definition of Done or the potentially releasable nature of the Increment. It may lead to low-quality or unusable work, defects, or rework.

A proportional amount of time on analysis, design, development, and testing: This is a too restrictive and prescriptive measure for the amount of work required of the Developers. It does not account for the complexity or variability of the product functionality delivered. It also does not respect the self-organization or cross-functionality of the Developers. It may lead to over-engineering or waste.

Scrum Guide: https://www.scrumguides.org/scrum-guide.html

Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done

Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum

Answer : B

The Scrum Guide states that ''Sprints are the heart of Scrum where ideas are turned into value''. It also states that ''Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint''. Furthermore, it states that ''Sprints are limited to one calendar month. When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase''. Therefore, the correct answer is B. The other options are not acceptable, as they contradict the Scrum principles of empiricism, self-organization, and adaptation.

The Scrum Guide, section 3.1. Sprints

Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2. The Product Owner and the Sprint

Answer : C

The Sprint Retrospective is a time-boxed event for the Scrum Team to inspect how the last Sprint went and plan for improvements in the next Sprint. The Scrum Guide states that 'The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.'1 This means that the Sprint Retrospective should be held at the end of each Sprint, regardless of the project or release status. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements, including to product quality and working relationships.1

1: The Scrum Guide2, page 16

2: The Scrum Guide