PSM-I Exam Dumps - Scrum Professional Scrum Master Questions and Answers

The correct answer is C, because if burndown charts are used to visualize progress, they track work remaining across time. A burndown chart is a graphical representation of the amount of work left to do versus the time available. It helps the Scrum Team monitor and forecast the progress toward the Sprint Goal.

According to the Scrum Guide1, the heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. The length of a Sprint should be short enough to keep the business risk acceptable to the Product Owner, short enough to be able to synchronize the development work with other business events, and no more than one calendar month.

References: Scrum Guide

According to the Scrum Guide1, the heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. The 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.

References: Scrum Guide

The Developers determine how many Product Backlog items they select for a Sprint, as stated in the Scrum Guide: “The Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence.”

The next Sprint begins immediately after the conclusion of the previous Sprint, as stated in the Scrum Guide: “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.”

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

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, an 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. For the purpose of transparency, when does Scrum say a new increment of working software must be available? At the end of every Sprint.

References: Scrum Guide

 According to the Scrum Guide, the Daily Scrum is held at the same time and same place to reduce complexity and promote consistency. The other options are not valid reasons for holding the Daily Scrum at the same time and same place, as they are either irrelevant (such as naming the place) or incorrect (such as being demanded by the Product Owner or booking rooms in advance).

According to the Scrum Guide1, when multiple Scrum Teams are working together on one product, they must coordinate their work with each other. One way to do this is through Nexus, a framework for scaling Scrum. Nexus helps to reduce cross-team dependencies and integration issues by making them more transparent. The key concern when multiple Development Teams are working from the same Product Backlog is minimizing dependencies between teams so that they can deliver an integrated Increment that meets the definition of “Done”.

References: Scrum Guide, Nexus Guide

According to the Scrum Guide, the purpose of a Sprint is to produce a valuable useful Increment that meets the Definition of Done and the Sprint Goal. This means that the Developers work on items from the Product Backlog that deliver value to the stakeholders and align with the product vision. The other option is not valid, as it implies that producing an Increment is not the purpose of a Sprint.