Scrum PSM-I Online Access

The correct answer is A, because the Product Owner does not determine how many Product Backlog items the Development Team selects for a Sprint. The Scrum Guide states that “the number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.” Therefore, the Development Team is responsible for choosing the scope of work for a Sprint.

According to the Scrum Guide 1 , each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The time-boxed events in Scrum are:

Sprint Planning (eight hours or less for a one-month Sprint)

Daily Scrum (15 minutes or less for a one-month Sprint)

Sprint Review (four hours or less for a one-month Sprint)

Sprint Retrospective (three hours or less for a one-month Sprint)

The other options are not time-boxed events in Scrum.

According to the Scrum Guide 1 , 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 serves the Developers in several ways, including:

Coaching them in self-management and cross-functionality;

Helping them to create high-value products;

Removing impediments to their progress;

Facilitating Scrum events as requested or needed; and,

Coaching them in organizational environments in which Scrum is not yet fully adopted and understood.

The Scrum Master serves the Product Owner in several ways, including:

Helping find techniques for effective Product Goal definition and Product Backlog management;

Helping the Scrum Team understand the need for clear and concise Product Backlog items;

Helping establish empirical product planning for a complex environment; and,

Facilitating stakeholder collaboration as requested or needed.

The Scrum Master serves the organization in several ways, including:

Leading, training, and coaching the organization in its Scrum adoption;

Planning and advising Scrum implementations within the organization;

Helping employees and stakeholders understand and enact an empirical approach for complex work; and,

Removing barriers between stakeholders and Scrum Teams.

Therefore, two things that are true about the Scrum Master role are:

The Scrum Master teaches the Development Team to keep the Scrum meetings to their time-box, as they help everyone understand Scrum theory and practice.

The Scrum Master helps those outside the team interact with the Scrum Team, as they serve both the Product Owner and the organization.

The other options are not true about the Scrum Master role, as they imply that they have authority or responsibility over things that are not within their accountability.

The Product Owner is responsible for ensuring that the most valuable functionality is produced first, at all times, by ordering and prioritizing the Product Backlog. The Product Owner also interacts with stakeholders to understand their needs and expectations, and to communicate the vision and progress of the product. The other options are not part of the Product Owner role according to Scrum, as they are either too prescriptive or too technical.