Master Scrum PSPO-I Exam with Reliable Practice Questions

Correct : A, C

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

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

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 : D, E

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

Correct : B

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

Correct : D

The Scrum Guide states that ''the Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints''. It also states that ''at the end of a Sprint, the new Increment must be 'Done', which means it must be in useable condition and meet the Scrum Team's definition of 'Done'''. Therefore, the Scrum Team must deliver a valuable, useful Increment that meets the Definition of Done at the end of a Sprint. The other options are not acceptable, as they do not meet the criteria of being valuable, useful, or done.

The Scrum Guide, section 3.4. Increment

Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.1. The Product Owner and the Development Team

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