Free Scrum PSPO-I Practice Exam with Questions & Answers | Set: 3

The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:

Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users.

Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often.

Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how valuable or desirable the product is for the customers or stakeholders.

The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are the ones who determine how many Product Backlog items they select for a Sprint, based on their capacity and the Sprint Goal1. The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog[3][3] . The Product Owner does not have the authority to tell the Developers how much work they should do, as this would violate the principle of self-management4.

The Scrum Guide states that “the Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint”. It also states that “the Developers can do the work of any other role on the Scrum Team, as long as accountability is met”. Therefore, the Developers on the Scrum Team should write the user documentation, as it is part of the Definition of Done and the work needed to deliver a “Done” Increment. The other options are not acceptable, as they violate the Scrum values of commitment, focus, and respect, and they create dependencies, delays, and waste.

The Scrum Guide, section 2.2. Developers

Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.3.The Product Owner and the Definition of Done

Professional Scrum Product Owner I (PSPO I) Sample Questions, question 12

Correct Answer: True

Dependencies are relationships between Product Backlog items that affect their order of implementation. For example, a Product Backlog item may depend on another one to be completed first, or it may have a dependency on a third-party system or resource. Dependencies could influence how the Product Owner orders Product Backlogitems, as they may introduce risks, constraints, or uncertainties that affect the value delivery. The Product Owner should try to minimize dependencies and order the Product Backlog items in a way that maximizes value and minimizes waste.

[Professional Scrum Product Owner], chapter 6: “Dependencies are relationships between Product Backlog items that affect their order of implementation.”

[Managing Dependencies on Agile Projects]: “Dependencies can have a significant impact on the delivery of value.”

The typical size for a Scrum Team is 10 or fewer people, including the Product Owner, the Scrum Master, and the Developers. The Scrum Guide states that " The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three people decrease interaction and results in smaller productivity gains. Having more than ten people requires too much coordination. Large teams generate too much complexity for an empirical process to be useful. " 1 This means that the optimal Scrum Team size is between 3 and 10 people, depending on the context and the nature of the work.

1: The Scrum Guide2, page 6

2: The Scrum Guide

The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are:

It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and focus on delivering value that contributes to the product vision.

It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to work on. It helps the Scrum Team prioritize and optimize their work based on value and impact.

It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress towards the Product Goal.

Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a Product Goal is or how Scrum works.

In accordance with Scrum theory, a group of 100 people should be divided into multiple Scrum Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing themselves into teams because:

It respects the self-organization and empowerment of the people. The people are the ones who have the knowledge, skills, and experience to create and deliver the product. They are also the ones who will work together as Scrum Teams, collaborating and coordinating their efforts. Therefore, they should have the autonomy and authority to decide how to form their teams, based on their preferences, interests, and capabilities.

It supports the alignment and coherence of the Scrum Teams. The people should have a clear and shared understanding of the product, the product vision, and the rules of the Scrum framework before forming their teams. This can help them to align their goals and missions, to ensure that they are working on the same product and towards the same vision. It can also help them to follow the same principles and practices of Scrum, to ensure that they are working effectively and consistently.

It fosters the collaboration and synergy of the Scrum Teams. The people should form their teams in a way that maximizes their collaboration and synergy. This can mean choosing team members that complement each other’s skills and strengths, that have good rapport and trust, that can communicate and coordinate well, and that can deliver a valuable Increment each Sprint.

Scrum is a framework that is designed to be lightweight and easy to adopt. To get started with Scrum, the minimal requirements are indeed a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas, and a Scrum Master to facilitate and guide the process. This aligns with the core principles of Scrum, which emphasize self-organization, collaboration, and the ability to deliver increments of value quickly and frequently.

The Scrum Guide outlines the roles within a Scrum Team and the necessity of having a Product Backlog with enough ‘Ready’ items to fill a Sprint. The guide also emphasizes the importance of having a clear definition of ‘Done’ before starting the first Sprint

In Scrum, when Developers encounter difficulties in delivering an Increment due to a lack of understanding of a functional requirement, they should collaborate with the Product Owner. This collaboration is crucial as the Product Owner has the responsibility to clarify the items in the Product Backlog and to ensure that the Development Team understands the work to be done. The Product Owner is accountable for maximizing the value of the product and must work with the Development Team to find out what is feasible and acceptable for the Increment being developed. This approach aligns with the Scrum principle of collaboration and self-organization within the Scrum Team.

The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) materials emphasize the importance of collaboration between the Product Owner and the Development Team to ensure a clear understanding of the Product Backlog items and to optimize the value of the work being done

To say that an event has a timebox means that the event has a fixed duration that cannot be exceeded. The Scrum Guide states that " All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. " 1 This means that the timebox sets an upper limit for the event, but the event can end sooner if the goal is met.

1: The Scrum Guide2, page 10

2: The Scrum Guide