PSPO-I Online Practice Questions and Answers

Correct Answer: AD

The Product Owner is one person, not a committee or a team of people. The 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. Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy, roadmap, and backlog. Therefore, the Scrum Team can not have multiple Product Owners. The Product Owner is accountable for ordering the Product Backlog. The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

Correct 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: References: 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

Correct Answer: AD

The 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.

The job of a Product Owner focuses on the following aspects:

The other options are not valid or relevant aspects of a Product Owner's job. They are either too narrow, unrealistic, or unrelated to the product value delivery. They are:

References:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Product Owner: https://www.scrum.org/resources/what-is-a-product-owner User Stories: https://www.agilealliance.org/glossary/user-stories

Correct Answer: C

Management that is external to the Scrum Team is not involved in the Daily Scrum because:

The Daily Scrum is an event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. It is not a status meeting or a reporting session for managers or other stakeholders. The presence of

external managers may hinder the self-organization, collaboration, and transparency of the Developers. It may also create pressure, interference, or distraction for the team.

The Scrum Master is responsible for ensuring that the Daily Scrum is held and that only the Developers participate. The Product Owner and other stakeholders may attend as observers, but only if the Developers find it useful.

References:

Scrum Guide 2020, page 12: "The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work."

Scrum Guide 2020, page 13: "The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. This

creates focus and improves self-management."

Scrum Guide 2020, page 13: "The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting."

Correct Answer: C

The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint. The 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. The Developers 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 Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment. The responsibility of crafting the Sprint Goal is shared by both the Product Owner and the Developers. The Product Owner should come to Sprint Planning with a business objective in mind, based on their understanding of the product vision, goals, value proposition, stakeholder feedback, market conditions, or other relevant factors. The Product Owner should propose how this objective can be achieved by selecting some Product Backlog items that can deliver value to customers or users. The Developers should collaborate with the Product Owner to craft a clear and concise Sprint Goal that expresses what they want to accomplish as a team during this Sprint. The Developers should also ensure that they have enough capacity and skills to deliver on this Sprint Goal. References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal Product Owner: https://www.scrum.org/resources/what-is-a-product-owner Developers: https://www.scrum.org/ resources/what-is-a-developer-in-scrum Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning

Correct Answer: A

The Developers are the ones who are accountable for tracking the remaining work toward the Sprint Goal. The Developers are self-managing and decide how much work they can do in a Sprint1. They also create and update the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers use the Daily Scrum to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. The Product Owner, the Scrum Master, and the Project Manager (if any) do not have the accountability for tracking the remaining work toward the Sprint Goal, as this is the responsibility of the Developers. References:

1: The Scrum Guide, November 2020, p. 6

2: The Scrum Guide, November 2020, p. 10 [3][3]: The Scrum Guide, November 2020, p. 11

Correct Answer: ACD

Correct Answers: A, C, and D.

Explanation: The Sprint Retrospective is an event where the Scrum Team reflects on how they worked together in the last Sprint and identifies ways to improve their collaboration, processes, and quality. Therefore, appropriate topics for

discussion in a Sprint Retrospective are:

Team relations: The Scrum Team should discuss how they communicated, interacted, and supported each other during the Sprint. They should celebrate their successes, acknowledge their challenges, and address any conflicts or issues that

arose. They should also share feedback, appreciation, and suggestions for improvement with each other.

How the Scrum Team does its work: The Scrum Team should inspect the methods, tools, and practices they used to deliver the product increment. They should evaluate what worked well and what could be improved. They should also

identify any impediments, risks, or dependencies that affected their work and how they handled them.

Definition of Done: The Scrum Team should review their Definition of Done and check if it is still relevant, clear, and achievable. They should also assess how well they adhered to it and if they delivered a potentially releasable product

increment that meets the quality standards. They should also consider if they need to update or adapt their Definition of Done based on new insights or feedback. The following topics are not appropriate for discussion in a Sprint

Retrospective:

The value of work currently represented in the Product Backlog: The value of the Product Backlog items is the responsibility of the Product Owner, who should continuously refine and order them based on stakeholder needs and feedback.

The value of the Product Backlog items is not directly related to how the Scrum Team works together and does not affect their improvement actions for the next Sprint.

Arranging the Sprint Backlog for the next Sprint: The Sprint Backlog is the plan for the next Sprint that is created by the Scrum Team during the Sprint Planning event. The Sprint Backlog is based on the Product Backlog items that are

selected for the next Sprint and how the Developers intend to accomplish them. The Sprint Retrospective is not a planning event but a reflection event that focuses on the past Sprint.

References:

[Scrum Guide], section 3.5: "The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness."

[Professional Scrum Product Owner], chapter 7: "The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint." What is a Sprint Retrospective? |

Scrum.org: "During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done" if appropriate and not in conflict with product or organizational

standards."

The Sprint Retrospective - What It Is and Tips for Making the Most of Your Meeting:

"The focus is on how the team worked together in the last sprint, including:

Communication Teamwork Process Tools Systems Work environment Missing competencies Collaboration with external parties"

Correct Answer: C

The Product Owner is the sole person responsible for managing the Product Backlog and ensuring that the value of the work the Scrum Team performs is understood by everyone involved. The Product Owner is the only person who can cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master1. A Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense1. References: Scrum Guide Sprint Cancellation Can Scrum Master cancel a sprint?

Correct Answer: D

Correct Answer: B

Answer: False Very Short Explanation: According to Scrum.org, the Product Owner is not required to create clear and unambiguous acceptance criteria for each item in the product's backlog before it can be selected in Sprint Planning1. Acceptance Criteria is optional and is not prescribed by Scrum12. It can be valuable, but it's not a must12. The Developers can inspect and adapt the Sprint Backlog in any way they see fit, in order to help meet the Sprint Goal2.