PSM-I Exam Dumps : Professional Scrum Master I

The correct answers are B and D. The Scrum Master is accountable for the Scrum Team’s effectiveness and helps the team improve its practices within the Scrum framework. One important way this happens is by facilitating Scrum Team decisions. That makes Option B correct. The Scrum Master does not make decisions for the team, but helps create the conditions for effective collaboration, self-management, and sound decision-making. This support improves the team’s ability to inspect, adapt, and work productively.

Option D is also correct because the Scrum Master serves the Scrum Team by causing the removal of impediments to the Scrum Team’s progress. Impediments reduce flow, create delays, and lower effectiveness. By helping remove those obstacles, the Scrum Master enables the team to focus on creating valuable Increments.

Option A is incorrect because ordering the Product Backlog is the Product Owner’s accountability, not the Scrum Master’s. Option C is too narrow. While the Scrum Master helps ensure Scrum events are positive, productive, and within the timebox, simply starting and ending meetings on time is not one of the two primary ways they help maximize team productivity. Their deeper contribution is enabling effectiveness and removing barriers.

According to the Scrum Guide, 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 topics that are appropriate for discussion are those that relate to how the team does its work, such as team relations, Definition of Done, and processes, tools, communication, collaboration, quality, etc. The other options are not appropriate topics for discussion in a Sprint Retrospective, as they belong to other Scrum events (such as arranging the Sprint Backlog for the next Sprint in the Sprint Planning or evaluating the value of work in the Product Backlog in the Sprint Review).

The correct answer is D. The Sprint Goal provides the Developers with a common, specific objective that creates focus and coherence during the Sprint. Rather than treating the Sprint as a collection of unrelated backlog items, the Sprint Goal gives the team a shared purpose for the work they are doing. This helps the Developers make trade-offs, collaborate more effectively, and adapt the Sprint Backlog while still moving toward a meaningful outcome.

Option A is incorrect because Scrum does not define Sprint 0 as part of Scrum, and the Sprint Goal applies to every Sprint. Option B is incorrect because the Sprint Goal is highly valuable. The Product Backlog provides ordered possibilities for future work, but the Sprint Goal explains the purpose of the current Sprint. Option C is incorrect because the Sprint Goal does not guarantee that every selected Product Backlog item will be completed. The team may renegotiate scope with the Product Owner as more is learned, while still aiming to achieve the Sprint Goal.

The Sprint Goal supports flexibility. It allows the Developers to adjust their plan during the Sprint without losing direction. That is why Scrum uses a goal-oriented approach rather than only a task-oriented one.