Scrum Updated PSM-I Exam Questions and Answers by sid

According to the Scrum Guide, the Sprint Backlog is the Developers’ plan for the Sprint, as it contains all the Product Backlog items selected for the Sprint and a plan for delivering them. The other options are not valid descriptions of the Sprint Backlog, as they are either incorrect (such as having a designated owner, being ordered by the Product Owner, or being a complete list of all work) or unnecessary (such as estimating each task in hours).

The two intended outcomes of the Daily Scrum are A and D.

A. Identification of impediments that may prevent the Developers from achieving the Sprint Goal.

The Daily Scrum is an opportunity for the Developers to inspect their progress toward the Sprint Goal and to identify any impediments or challenges that may hinder them from completing the work in the Sprint Backlog1. The Scrum Master can help the Developers remove these impediments or find ways to overcome them2.

D. A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal.

The Daily Scrum is also an opportunity for the Developers to adapt their plan for the next 24 hours based on their current situation and the Sprint Goal1. The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work1. This creates focus and improves self-management.

B, C, and E are not intended outcomes of the Daily Scrum.

B. An update of completed tasks and of the remaining work so the Scrum Master can plan the next day.

The Daily Scrum is not a status meeting or a report for the Scrum Master or anyone else2. The Developers are responsible for conducting and facilitating the Daily Scrum, not the Scrum Master1. The Scrum Master’s role is to ensure that the event happens, that it is positive and productive, and that it stays within the 15-minute timebox2.

C. An updated Scrum board to make Sprint progress transparent for the stakeholders.

The Daily Scrum is an internal meeting for the Scrum Team, not for external stakeholders1. The Scrum board is a tool that can help the Developers visualize their work, but it is not an outcome of the Daily Scrum. The outcome of the Daily Scrum should be an updated Sprint Backlog and an updated Sprint plan to achieve the Sprint Goal3.

E. A status report for the upper management indicating what each individual has done, will be doing, and what is impeding him/her.

The Daily Scrum is not a status report for anyone, especially not for upper management2. The purpose of the Daily Scrum is to inspect and adapt the work of the Developers, not to report on individual activities or performance1. The focus of the Daily Scrum should be on the collective work and progress of the Developers as a self-organizing team2.

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

References: Scrum Guide

There are no activities that a Product Owner would typically undertake in the phase between the end of the current Sprint and the start of the next Sprint, because there is no such phase. The next Sprint starts immediately after the current Sprint, without any gaps or breaks. The other options are either activities that occur during a Sprint (such as refining the Product Backlog) or activities that are not consistent with Scrum (such as working with Quality Assurance departments or updating project plans).