Scrum PSPO-I Practice Test - Questions Answers, Page 14

The Definition of Done is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done1.The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints2. The Increment must be usable and potentially releasable, meaning that it meets the quality standards set by the Scrum Team and the stakeholders[3][3].Doing all work needed to meet the Definition of Done enhances the transparency of the Increment, as it ensures that the Increment is truly done and reflects the current state of the product4. The other options do not enhance the transparency of the Increment, as they either introduce unnecessary complexity, delay, or overhead, or do not provide a clear and consistent way to measure the quality of the work done.

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

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

[3][3]:The Scrum Guide, November 2020, p. 13

4:Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

The Definition of Done is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done1.A Product Backlog item is considered complete when it meets the Definition of Done, which means that it is usable and potentially releasable, and that it meets the quality standards set by the Scrum Team and the stakeholders2. The other options are not sufficient to determine the completeness of a Product Backlog item, as they may not reflect the actual value and quality of the product.

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

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

The Sprint Retrospective is an event for the Scrum Team to inspect how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done1.The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness for the next Sprint2. Therefore, appropriate topics for discussion during a Sprint Retrospective are:

Identifying high priority process improvements for the next Sprint. The Scrum Team should identify the most important things that went well and the potential improvements, and create a plan for implementing some of them in the next Sprint[3][3]. This way, the Scrum Team can continuously improve their performance and deliver more value.

How the team collaborates.The Scrum Team should reflect on how they work together as a self-managing unit, and how they can enhance their skills, tools, and relationships4. This way, the Scrum Team can foster a culture of trust, respect, and collaboration.

The other options are not appropriate topics for discussion during a Sprint Retrospective, as they are either related to the Product Backlog or the Sprint Backlog, which are not the focus of the Sprint Retrospective.The order of items in the Product Backlog is the responsibility of the Product Owner, who manages the Product Backlog based on the value, risk, and dependencies of the items5. The Product Owner may seek input from the Scrum Team or the stakeholders, but the final decision is up to the Product Owner. Documenting acceptance criteria for items in the next Sprint is part of the Product Backlog refinement, which is an ongoing activity throughout the Sprint, not a specific event. The Scrum Team should collaborate on refining the Product Backlog items and adding more details, such as acceptance criteria, as they become more clear and ready for selection in a Sprint Planning.

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

2:The Scrum Guide, November 2020, p. 15

[3][3]:The Scrum Guide, November 2020, p. 15

4:Developing People and Teams, Scrum.org, accessed on December 16, 2023

5:The Scrum Guide, November 2020, p. 7

:The Scrum Guide, November 2020, p. 10

:The Scrum Guide, November 2020, p. 10

:Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

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.

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

The Scrum values are commitment, focus, openness, respect, and courage1.These values are embodied by the Scrum Team, which is a self-managing unit that organizes its own work and delivers a valuable product2. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers[3][3]. The best way to create Scrum Teams is to respect the self-management and empowerment of the people who will do the work, and let them decide how to organize themselves into Scrum Teams.This can be done by bringing all the people together and letting them form Scrum Teams based on their skills, interests, and alignment with the product vision4.Alternatively, existing teams can propose how they would like to reorganize themselves into Scrum Teams, based on their feedback and experience5. These ways of creating Scrum Teams are consistent with the Scrum values, as they foster commitment, focus, openness, respect, and courage among the team members and stakeholders. The other options are not consistent with the Scrum values, as they involve managers or the Chief Product Owner imposing their decisions on the team members, which undermines their self-management and empowerment, and creates a lack of trust and collaboration.

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

2:The Scrum Guide, November 2020, p. 5

[3][3]:The Scrum Guide, November 2020, p. 6

4:Managing Products with Agility, Scrum.org, accessed on December 16, 2023

5:Developing People and Teams, Scrum.org, accessed on December 16, 2023

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.

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

2:The Scrum Guide, November 2020, p. 10

[3][3]:The Scrum Guide, November 2020, p. 6

4:Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

Sprint Planning is an event where the Scrum Team collaborates on the work to be performed during the Sprint1. The topics covered in Sprint Planning are:

What can be done. The Product Owner proposes how the product could increase its value and utility in the current Sprint, based on the Product Goal, the Product Backlog, and the latest market and stakeholder feedback. The Developers assess the capacity and the technical feasibility of the work, and select the Product Backlog items that they can commit to for the Sprint.The Scrum Team crafts the Sprint Goal, which is a concise statement of the purpose and focus of the Sprint2.

How to do it. The Developers plan how they will deliver a "Done" product Increment that meets the Sprint Goal. They create a plan for the first days of the Sprint, and decompose the selected Product Backlog items into smaller work items. The Developers also identify any dependencies, risks, or impediments that may affect their work. The resulting plan is captured in the Sprint Backlog, which is owned and managed by the Developers[3][3].

Why to do it. The Product Owner explains the value and the outcome of the work to be done in the Sprint, and how it aligns with the Product Goal and the stakeholder needs. The Product Owner also clarifies the acceptance criteria and the Definition of Done for the Product Backlog items, and answers any questions from the Developers.The Scrum Team ensures that they have a common understanding of the Sprint Goal and the expected product Increment4.

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

2:The Scrum Guide, November 2020, p. 10

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

4:Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023