Pass the Scrum Professional Scrum Master PSM-I Questions and answers with ExamsMirror

All of the above topics should be discussed in the Sprint Review, as stated in [4]: "The purpose of this meeting is to inspect what was delivered during this sprint and adapt what we want to deliver next. This means we will discuss three things:

What did we do this sprint?

How did we do it?

What do we want to do next?"

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 Daily Scrum is an event for the Developers of the Scrum Team. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Scrum Master and Product Owner may attend as observers, but only if it is useful for the Developers.

References: Scrum Guide

 According to the Scrum Guide, changing the terminology of Scrum may have negative consequences, such as losing the benefits of Scrum, not understanding what has changed, or having very little change at all. Therefore, all answers apply to this question. The Scrum Guide recommends using the same terminology as in the guide to avoid confusion and misunderstanding.

The best two answers are A and B. As a Scrum Team, prioritizing the list and working on them in order is a good technique to tackle the impediments. This way, the team can focus on the most urgent and important issues first and avoid being overwhelmed by the number of impediments. The Scrum Master discusses the impediments with the Scrum Team is also a helpful technique, as it allows the team to share their perspectives, identify the root causes, and come up with possible solutions. The Scrum Master can also coach the team on how to remove or prevent impediments in the future.

The correct answer is C, because when a Development Team is having trouble delivering a working Increment because they don’t understand a functional requirement, they should collaborate with the Product Owner to determine what is possible and acceptable. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.” Therefore, the Product Owner should clarify the functional requirement and negotiate the scope of work with the Development Team.

There is no such thing as Sprint 0 in Scrum, as stated in [7]: “Sprint 0 is a term used by some people who use Scrum to describe an initial period before starting Sprints where they do some upfront planning or analysis. However, this is not part of Scrum and contradicts its principles of empirical process control, iterative delivery, and responding to change.”

 According to the Scrum Guide, the time-boxed events in Scrum are Sprint Retrospective, Sprint Planning, and Daily Scrum. These events have a maximum duration that cannot be exceeded. The other options are not time-boxed events in Scrum, as they are either not part of Scrum (such as Release Planning, Release Retrospective, Sprint Testing, and Sprint 0) or not events at all (such as Definition of Done).

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