PSM-I Exam Dumps - Professional Scrum Master I

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 Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide1. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values1. The Scrum Master is accountable for establishing Scrum2. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization while serving the Scrum Team as well as the larger organization2.

Option B is incorrect because keeping track of resource allocation is not a responsibility of the Scrum Master. The Scrum Master does not manage or control the resources of the Scrum Team or the organization. The Scrum Team is self-organizing and responsible for managing its own work within a Sprint1.

Option C is incorrect because managing the performance of the Scrum Team is not a responsibility of the Scrum Master. The Scrum Master does not evaluate or appraise the performance of the Development Team or the Product Owner. The Scrum Master serves the Development Team by coaching them on self-organization and cross-functionality, and serves the Product Owner by ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team1.

Option D is incorrect because the meetings and the objectives that a Scrum Team sets for itself are not a responsibility of the Scrum Master. The Scrum Master does not dictate or prescribe what meetings or objectives a Scrum Team should have. The Scrum Master facilitates the Scrum Events as requested or needed, and ensures that they are positive, productive, and kept within the time-box1.

A Product Backlog item is considered complete when it meets the Definition of Done, as stated in [5]: “When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment.”

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

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.

According to the Scrum Guide1, Scrum does not require or provide any specific techniques or methods for product definition. Rather, Scrum provides a framework with roles, rules, and events within which complex products can be developed. To get started in terms of what to build, Scrum requires no more than a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas and a Scrum Master to help guide the process.

References: Scrum Guide