Scrum Updated PSM-I Exam Questions and Answers by elyza

The correct answer is A, because the Product Owner does not need to be present at the Daily Scrum. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. … The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal.” Therefore, the Daily Scrum is an internal event for the Development Team, and the Product Owner can attend only if invited by the Development Team.

According to the Scrum Guide1, each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Therefore, a good way to continue is for the Development Team to make sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.

References: Scrum Guide

The best answer is B. A valuable, useful Increment that meets the Definition of Done.

According to the Scrum Guide1, “an Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.” The Scrum Guide also states that “work cannot be considered part of an Increment unless it meets the Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.”

Therefore, a Scrum Team should deliver a valuable, useful Increment that meets the Definition of Done at the end of each Sprint. This ensures that the product is potentially releasable and that the stakeholders can inspect and provide feedback on it.

A, C, and D are not correct answers.

A. A single document, if that is what management asked for.

This answer does not reflect the Scrum values of commitment, focus, and respect1. A Scrum Team should not deliver a single document just because management asked for it, but rather deliver an Increment that provides value to the customers and users. A document may be part of an Increment, but it is not an Increment by itself.

C. Failing unit tests, to identify acceptance tests for the next Sprint.

This answer does not reflect the Scrum principle of empiricism1. A Scrum Team should not deliver failing unit tests, but rather deliver an Increment that is thoroughly verified and meets the quality standards. Failing unit tests indicate that the work is not done and that there are defects or errors in the product. A Scrum Team should use unit tests to ensure that the product works as expected and to identify and fix any issues before delivering the Increment.

D. An Increment of software with minor known bugs in it.

This answer does not reflect the Scrum value of openness1. A Scrum Team should not deliver an Increment of software with minor known bugs in it, but rather deliver an Increment that meets the Definition of Done and is free of any known defects or issues. Delivering an Increment with bugs in it can compromise the trust and satisfaction of the stakeholders and can lead to technical debt or rework in the future. A Scrum Team should strive to deliver high-quality products that meet or exceed the expectations of the customers and users.

According to the Scrum Guide1, 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 created by the development organization (or Development Team if none is available from the development organization). The definition guides the Development Team in creating a “Done” Increment.

References: Scrum Guide