PSM-I Exam Dumps : Professional Scrum Master I

A Sprint may be cancelled only if the Sprint Goal becomes obsolete. This makes Option A the correct answer. The Scrum Guide is very clear that only the Product Owner has the authority to cancel a Sprint, although that decision may be influenced by stakeholders, the Developers, or the Scrum Master. The reason for cancellation is not general disruption, poor forecasting, or the appearance of new work. It is specifically tied to the Sprint Goal no longer having value or relevance.

Option B is incorrect because a new business opportunity does not automatically justify cancelling a Sprint. Scrum is designed to handle change without disrupting the Sprint unless the Sprint Goal itself is no longer valid. Option C is incorrect because feasibility concerns should be addressed through collaboration and adaptation, but they do not by themselves define the cancellation rule. Option D is incorrect because not finishing all selected work is not a reason to cancel a Sprint. Scrum accepts uncertainty, and the team inspects and adapts. The Sprint Goal remains the key commitment, and as long as it is still relevant, the Sprint should continue.

 According to the Scrum Guide 1 , ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does. 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. Therefore, an appropriate action for the Scrum Master to take if the Product Owner is struggling with ordering the Product Backlog is to offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.

A Scrum Team is a cohesive unit of professionals that consists of one Product Owner, one Scrum Master, and Developers, as stated in the Scrum Guide: “The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal.”