Free Practice Questions for Scrum PSM-I Exam

 The Scrum Master should be concerned about the ability of the Development Teams to produce integrated Increments, as this is one of the goals of Scrum. The Scrum Master should also encourage the Development Teams to figure out a solution for themselves, as this fosters self-management and collaboration. The other options are not relevant or important for the Scrum Master in this situation.

According to the Scrum Guide1, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with domain, practices, and people involved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Scrum Master is part of the Scrum Team and should participate as a Scrum team member and facilitate as requested or needed.

References: Scrum Guide

According to the Scrum Guide, the Developers are accountable for tracking the remaining work toward the Sprint Goal, as they are responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that someone else outside the Development Team (such as the Scrum Master, the Product Owner, or the Project Manager) is accountable for tracking the remaining work, which is not consistent with Scrum values and principles.

According to the Scrum Guide1, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with domain, practices, and people involved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. Therefore, two appropriate topics for discussion during a Sprint Retrospective are:

Identifying high priority process improvements for the next Sprint.

How the team collaborates.

The other options are not relevant or appropriate for the Sprint Retrospective.

References: Scrum Guide

The correct answers are B and D, because the length of the Sprint should be chosen based on the level of uncertainty over the technology to be used and the risk of being disconnected from the stakeholders. The Scrum Guide states that “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month. When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase.”

According to the Scrum Guide1, the Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The other roles are not responsible for making sure everyone on the Development Team does their tasks for the Sprint.

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

The correct answer is B, because a Scrum Master is not the same thing as a traditional PM (Project Manager). The Scrum Guide states that “the Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.” Therefore, a Scrum Master is not a manager, but a servant-leader and a coach for the Scrum Team and the organization.

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