Professional Scrum Master PSM-I Updated Exam

The correct answers are C, E, and F, because these phrases best describe the purpose of a definition of “Done”. It creates transparency over the work inspected at the Sprint Review, as it defines what it means for an Increment to be potentially releasable. It guides the Development Team in creating a forecast at the Sprint Planning, as it helps them estimate how much work they can accomplish in a Sprint. It defines what it takes for an Increment to be ready for release, as it ensures that the product meets the quality expectations of the stakeholders.

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. Therefore, the best description of an increment of working software is additional features in a usable state that complement those delivered in previous iterations.

References: Scrum Guide

According to the Scrum Guide1, one aspect of Scrum Teams inspecting how they work toward their Product Goal is that they create a Sprint Goal every Sprint. The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers on why it is building the Increment. It also provides a basis for inspecting and adapting during the Sprint Review and Sprint Retrospective. The Sprint Goal is created during the Sprint Planning event.

References: Scrum Guide

According to the Scrum Guide, a Development Team is cross-functional if it has all the skills to create a potentially releasable Increment by the end of every Sprint. The other options are not indicators of cross-functionality, as they are either specific practices (such as pair programming or test driven development) or irrelevant factors (such as conflicts within the team or ability to perform every task).