PSM-I Exam Dumps - Professional Scrum Master I

Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.

According to the Scrum Guide, two actions that the Scrum Master should support in this scenario are forecasting the Product Backlog items that are most likely to meet the Sprint Goal and creating the Sprint Backlog, and discussing why this happened and what changes will make it less likely to recur during the next Sprint Retrospective. These actions are consistent with Scrum values and principles, such as empiricism, adaptation, and continuous improvement. The other options are not valid actions, as they are either wasteful (such as canceling the Sprint or continuing the Sprint Planning past its timebox) or ineffective (such as asking everyone to take more time to analyze the Product Backlog).

In Scrum, the Developers have the autonomy to manage their work and the Sprint Backlog. When an unexpected request comes in, even from someone as authoritative as the CEO, it should not be added directly to the Sprint Backlog without discussion.  The correct approach is for the Developers to discuss the new item with the Product Owner and the rest of the Scrum Team to understand its impact on the current Sprint Goal and to collaboratively decide the best course of action 1 2 .

This is in line with the Scrum values of  Courage ,  Focus ,  Commitment ,  Respect , and  Openness .  The team must have the courage to push back on changes that could disrupt their Sprint Goal, stay focused on their commitments, respect the agreed-upon process, and be open about the implications of introducing new work mid-Sprint 1 .

The Scrum Guide also states that once the Sprint begins, no one can force the Development Team to work on different requirements than those they forecasted for the Sprint 1 . If the CEO’s request is deemed important enough to warrant a change in the Sprint’s direction, it may lead to a negotiation of scope with the Product Owner or, in extreme cases, to the cancellation of the Sprint if the Sprint Goal becomes obsolete.  However, these are decisions that should be made collaboratively by the entire Scrum Team, not unilaterally by any single member, regardless of their position in the company

https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

Scrum is a framework for developing, delivering, and sustaining complex products. Scrum has three roles: the Product Owner, the Scrum Master, and the Developers. The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment in each Sprint. The Developers are not limited by titles such as programmer, designer, tester, architect, engineer, etc. The Developers are responsible for all aspects of quality, including finding and fixing bugs, tracking quality metrics, and verifying the work of other Developers. Therefore, Scrum has no “tester” role, and the Developers are responsible for quality.

A Developer is accountable for creating a plan for the Sprint, the Sprint Backlog, and organizing the work required to meet the Sprint Goal, as stated in the Scrum Guide: " Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for:

Creating a plan for the Sprint, the Sprint Backlog;

Instilling quality by adhering to a Definition of Done;

Adapting their plan each day toward the Sprint Goal; and,

Holding each other accountable as professionals. "

The correct answers are A and B, because these are true about the Product Owner role. The Product Owner is one person, not a committee or a team, who is accountable for ordering the Product Backlog and maximizing the value of the product. 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. … For the Product Owner to succeed, the entire organization must respect his or her decisions.”

The Sprint Backlog is the Development Team’s plan for the Sprint, as stated in the Scrum Guide 1 : “The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.”

An example of an Increment is a valuable, useful set of product features, as stated in [4]: “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, each Increment must be usable.”