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

According to the Scrum Guide, the timebox for a Sprint Planning event is 8 hours for a one-month Sprint, proportionally shorter for shorter Sprints. The other options are not valid, as they are either too long (such as monthly), too vague (such as whenever it’s done), or too short (such as 4 hours for a one-month Sprint).

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.

The correct answer is D. 10 or fewer. According to the Scrum Guide 20201, “The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.” The other options are outdated or incorrect. Option A was based on the previous version of the Scrum Guide, which suggested a range of 3 to 9 developers2. Option B is too vague and does not account for the upper limit of team size. Option C is too specific and does not allow for flexibility.

According to the Scrum Guide, the Developers on the Scrum Team should write the user documentation, as they are responsible for creating a “Done” Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that the user documentation can be deferred, ignored, or outsourced, which is not consistent with Scrum values and principles.

During the Sprint, the Scrum Master’s role is to facilitate inspection and adaptation opportunities as requested or needed, and to coach the team members in self-management, as stated in 3: “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. The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.”

The correct answer is C, because the Scrum Guide states that “the Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint.” Therefore, enough work should be defined during the Sprint Planning event so that the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint.

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, in order to turn Product Backlog items into an Increment of potentially releasable product functionality, the Development Team should have all the skills needed.

References: Scrum Guide

The correct answer is F, because all of the Scrum Values are affected by a lack of trust in the Scrum Team. Trust is essential for the Scrum Team to work effectively and deliver value. Without trust, the Scrum Team may lose focus, respect, openness, courage, and commitment.

According to the Scrum Guide1, during each Daily Scrum, each Developer answers three questions:

• What did I do yesterday that helped meet our Sprint Goal?
• What will I do today to help meet our Sprint Goal?
• Do I see any impediment that prevents me or our Development Team from meeting our Sprint Goal?

The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward achieving their Sprint Goal and producing a usable Increment. The other options are not relevant or appropriate for the Daily Scrum.

References: Scrum Guide

The timebox for the Sprint Review is four hours for a one-month Sprint, as stated in [4]: “The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”; additionally, they discuss any changes to scope or budget or potential value. The entire group then collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is a working session and attendees should inspect based on facts. A Sprint Review is held at the end of every Sprint for a maximum duration of four hours for a one-month Sprint.”