PSM-I Exam Dumps - Scrum Professional Scrum Master Questions and Answers

The correct answer is C. Scrum defines accountabilities for product value, team effectiveness, and creating Done Increments, but it does not give the Scrum Master, Product Owner, or Scrum Team formal managerial authority to hire or fire people. Personnel decisions such as removing someone from a team are typically the responsibility of the organization and its management structure. In this case, the hiring manager or appropriate people manager would be responsible for removing the Developer if that becomes necessary.

Option A is incorrect because although the Scrum Master helps remove impediments, that does not mean they have authority over employment or staffing decisions. Option B is incorrect because the Product Owner is accountable for maximizing product value, not for personnel management. Option D is incorrect because the Scrum Team is self-managing with respect to its work, but it does not generally have organizational authority to remove employees from the team.

The Scrum Master should still help the team address the conflict by coaching, facilitating conversations, and improving collaboration. But if actual removal is required, that action belongs to the organization’s management system, not to a Scrum accountability.

According to the Scrum Guide 1 , 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, in order to produce integrated Increments that are potentially releasable, the best suited structure for Development Teams is to develop functionality from beginning to end throughout all technical layers.

According to the Scrum Guide 1 , the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. Therefore, one reason why the Product Owner wants the Development Team to adhere to its definition of “Done” is to have complete transparency into what has been done at the end of each Sprint.

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? "

 According to the Scrum Guide, a Scrum Team is not only allowed to meet with stakeholders during Sprint Review, but also during Sprint Planning and throughout the Sprint as needed. The Sprint Review is an opportunity for the Scrum Team and the stakeholders to collaborate on what was done in the Sprint and what to do next. However, it is not the only time that stakeholder feedback is welcomed and valued.

 According to the Scrum Guide, a Development Team needs a Sprint Goal because it provides guidance and focus for building an Increment that delivers value. The other options are not valid reasons for having a Sprint Goal, as they are either incorrect (such as giving purpose only to Sprint 0 or ensuring implementation of all Product Backlog items) or irrelevant (such as knowing everything from the Product Backlog).

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

The correct answer is E, because all of these topics can be discussed during a Sprint Retrospective. The Scrum Guide states that “the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. … During each Sprint Retrospective, the Scrum Team plans ways to improve product quality by adapting the definition of ‘Done’ as appropriate.” Therefore, the Scrum Team can discuss any aspect of their process, communication, skills, or definition of ‘Done’ that may help them improve.

The Product Owner is responsible for engaging the stakeholders, as stated in the Scrum Guide 1 : “The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner.”

According to the Scrum Guide 1 , the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.