Scrum PSPO-I Professional Scrum Product Owner I Exam Practice Test

Answer : A

Answer : A, E, F

The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary1.It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments2. If the frequency of the Daily Scrum were to be lowered to every two or three days, three key concerns would be:

The Sprint Backlog may become inaccurate. The Sprint Backlog is the plan for how the Developers will achieve the Sprint Goal, and it is updated throughout the Sprint as more is learned[3][3].The Daily Scrum is a chance for the Developers to inspect the Sprint Backlog and make adjustments based on the current situation4. If the Daily Scrum is less frequent, the Sprint Backlog may not reflect the reality of the work, and the Developers may lose track of their progress and alignment with the Sprint Goal.

Opportunities to inspect and adapt the Sprint Backlog are lost.Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed5. The Daily Scrum is an essential event for the Developers to apply empiricism to their work, by inspecting the Sprint Backlog and adapting it to optimize the value and quality of the Increment. If the Daily Scrum is less frequent, the Developers may miss opportunities to inspect and adapt their work, and may not be able to deliver a valuable, useful Increment every Sprint.

Impediments are raised and resolved more slowly. An impediment is anything that prevents the Scrum Team from delivering a product Increment. The Daily Scrum is a forum for the Developers to identify and communicate any impediments that affect their work, and to seek help from the Scrum Master or other team members. If the Daily Scrum is less frequent, the impediments may not be raised and resolved in a timely manner, and may cause delays or quality issues in the product delivery.

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

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

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

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

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

:The Scrum Guide, November 2020, p. 11

:The Scrum Guide, November 2020, p. 14

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

Answer : B

Sprint 0 is a term that some organizations use to describe a phase of work before the first official Sprint, where they do some upfront planning, design, architecture, or analysis1.However, this term is not consistent with the Scrum framework, which does not prescribe any pre-Sprint activities or phases2. Scrum starts with a Product Backlog that contains at least one valuable and feasible Product Goal, and enough Product Backlog items to initiate the first Sprint[3][3].The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog4. The Product Owner does not have any specific accountability during Sprint 0, because Sprint 0 is not a part of Scrum.

1:Sprint Zero: A Good Idea or Not?, Scrum Alliance, accessed on December 16, 2023

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

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

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

Answer : B

The Developers are the ones who determine how many Product Backlog items they select for a Sprint.The Developers are self-managing and decide how much work they can do in a Sprint1.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, the Scrum Master, and the stakeholders do not have the authority to tell the Developers how many Product Backlog items they should select, as this would violate the principle of self-management[3][3].

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

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

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

Answer : A, C

Non-functional requirements are the criteria that define the quality, performance, security, usability, and other aspects of a product1.They are often implicit or assumed, but they are important to make visible and explicit, as they affect the value and satisfaction of the product2. One effective way to make non-functional requirements visible is to add them to the Product Backlog, which is an ordered list of everything that is known to be needed in the product[3][3].By adding non-functional requirements to the Product Backlog, the Product Owner and the Developers can prioritize, refine, and estimate them, and make them transparent to the stakeholders4.Another effective way to make non-functional requirements visible is to add them to the Definition of Done, which is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done5. By adding non-functional requirements to the Definition of Done, the Developers can ensure that every Product Backlog item and Increment meets the expected quality standards, and that the work is taken care of every Sprint.

1:Non-functional requirement, Wikipedia, accessed on December 16, 2023

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

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

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

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

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

Answer : A

The purpose of a Sprint is to produce a valuable, useful Increment that meets the Sprint Goal and the Definition of Done1.An Increment is a concrete step toward achieving the Product Goal and is the primary measure of progress in Scrum2. 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].

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

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

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

Answer : C, E

The Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices1.The Scrum Master also facilitates Scrum events as requested or needed2. The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3].It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments4. The Scrum Master should coach the team on the purpose and value of the Daily Scrum, and help them find ways to make it more effective and enjoyable. The Scrum Master should also learn why the Developers want to reduce the frequency of the Daily Scrum, and work with them to address any underlying issues or concerns.The Scrum Master should not impose a decision on the team, nor delegate the decision to a vote, as these actions would undermine the self-management and empowerment of the Developers5.

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

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

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

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