PSM-I Exam Dumps - Professional Scrum Master I

According to the Scrum Guide, when multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint, in order to accurately inspect what is done and ensure that there is no technical debt or unfinished work at the end of each Sprint. The other options are not valid, as they imply that integration can be skipped, delayed, or done only for some teams, which is not consistent with Scrum values and principles.

According to the Scrum Guide1, 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 Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Product Owner is part of the Scrum Team and should participate as a Scrum Team member in the Sprint Retrospective.

References: Scrum Guide

The correct answer is B, because a Product Owner is best described as a value optimizer. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Therefore, a Product Owner should focus on delivering value to the customers and stakeholders through the product.

According to the Scrum Guide, a Scrum Team is cross-functional if it includes skilled individuals who together have all the skills necessary to create value each Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of cross-functionality, as they either imply that the Developers work in silos or rely on external people (such as business analysts, architects, testers, or separate teams).

According to the Scrum Guide, a Scrum Master fulfills a different role from a traditional project manager. A Scrum Master is a servant-leader and a coach for the Scrum Team and the organization, not a manager or a supervisor. A Scrum Master does not assign tasks, set deadlines, or monitor progress, but rather facilitates self-organization, collaboration, and empiricism within the Scrum Team and the organization.

 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.

When a Development Team determines that it will not be able to finish the complete forecast, both the Product Owner and the Development Team have to be present when reviewing and adjusting the Sprint work selected, as stated in [6]: “If there is not enough work remaining for all members of a Development Team then they can renegotiate scope with their Product Owner. If there is too much work remaining then they can also renegotiate scope with their Product Owner.”

During the Sprint Retrospective, the Scrum Team may add items to the Sprint Backlog for the next Sprint, as stated in [5]: “The purpose of each Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team plans ways to implement improvements identified during this meeting into its way of working. By doing this it reinforces empiricism throughout its work. Improvements may be implemented at any time during a Sprint or they may be planned for subsequent Sprints.”