Scrum Professional Scrum Master I PSM-I Exam Questions

Answer : C

The correct answer is C, because if necessary, the Development Team is responsible for removing a team member who is creating a hostile environment. The Scrum Guide states that ''development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.'' Therefore, the Development Team should manage its own composition and dynamics, and may need help from the Scrum Master to facilitate this process.

Answer : B

According to the Scrum Guide, the Product Owner does not make sure that the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are responsible for selecting how much work they can do in a Sprint, based on their capacity and past performance. The Product Owner may influence them by ordering and clarifying the Product Backlog items, but does not control their selection.

Answer : D

The Sprint Backlog is the Development Team's plan for the Sprint, as stated in the Scrum Guide1: ''The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.''

Answer : A

The correct answer is A, because the role of management in Scrum is to facilitate the Scrum Teams with insights and resources that help them improve. The Scrum Guide states that ''the organization respects their self-organization by not telling them how they should do their work.'' Therefore, management should support the Scrum Teams by providing them with an environment that fosters collaboration, learning, and innovation.

Answer : B

The correct answer is B, because the Scrum Guide states that ''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 Development Team on why it is building the Increment.'' Therefore, the Sprint Goal provides the Development Team with a target and overarching direction for the Sprint.

Answer : B

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.

Answer : C, D

According to the Scrum Guide1, collaboration between the Product Owner and Developers is essential for creating valuable products. The Product Owner is accountable for maximizing value resulting from work by Developers. Developers are accountable for creating a plan for the Sprint, which includes selecting items from Product Backlog that they can complete within a Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. Therefore, two valuable actions for a Scrum Master to take if the Product Owner is not collaborating with the Development Team during the Sprint are:

Bring up the problem in the Sprint Retrospective, where the Scrum Team can inspect how they worked together and create a plan for improvements.

Coach the Product Owner in the values of Scrum and incremental delivery, and help them understand their role and responsibilities in collaborating with Developers.

The other options are not valuable actions, as they may undermine trust, respect, and self-organization within the Scrum Team.