Pass the Scrum Professional Scrum Master PSM-I Questions and answers with ExamsMirror

The correct answer is B. To present the Scrum Teams with insights and resources that help them improve. According to the Scrum Guide1, “The role of management in Scrum is to support the Product Owner with insights and information into high-value product and system capabilities.” Management also helps the Scrum Team by providing an environment that fosters agility, learning, and collaboration2. Management does not directly control or monitor the work of the Developers, nor does it interfere with the self-organization and autonomy of the Scrum Team3. Management’s function in Scrum is to enable and empower the Scrum Team to deliver value and continuously improve.

According to the Scrum Guide1, there are three roles in a Scrum Team:

The Product Owner

The Developers

The Scrum Master

The Product Owner is accountable for maximizing value resulting from work by Developers. Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. 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. Every Scrum team must have a Product Owner and Scrum Master, as outcomes are affected by their participation and availability. The other options are false, as they imply that the Product Owner and Scrum Master roles are optional or interchangeable.

References: Scrum Guide

The correct answer is A, because the Scrum Guide states that “the definition of ‘Done’ is a formal description of the state of the Increment when it meets the quality measures required for the product.” Therefore, non-functional requirements should be part of the definition of ‘Done’ and ensure every Increment meets them.

According to the Scrum Guide, multiple Scrum Teams working on the same product do not have to have the same Sprint start date. They may start their Sprints at different times, as long as they synchronize their work and integrate their Increments at least by the end of each Sprint. The other option is not valid, as it implies that having the same Sprint start date is mandatory for multiple Scrum Teams.

According to the Scrum Guide, the Product Owner must participate in the Daily Scrum when he or she is actively working on items on the Sprint Backlog; however, they participate as a Developer, not as an authority figure. This means that the Product Owner can share progress, plans, and impediments with the other Developers and collaborate with them on delivering value. The other options are not valid reasons for the Product Owner to participate in the Daily Scrum, as they are either irrelevant (such as representing stakeholders or discussing impediments) or inappropriate (such as being asked by the Scrum Master).

Correct Answer: C and E

Short Explanation: According to the Scrum Guide 20201, the product has one Product Backlog, which is the single source of work undertaken by the Scrum Team. The Product Backlog is ordered by the Product Owner, who is accountable for maximizing the value of the product resulting from the work of the Scrum Team. There should be only one Product Owner per product, who may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner1. Having multiple Product Owners or Product Backlogs would create confusion, inconsistency, and waste in the Scrum process.

The two intended outcomes of the Daily Scrum are A and D.

A. Identification of impediments that may prevent the Developers from achieving the Sprint Goal.

The Daily Scrum is an opportunity for the Developers to inspect their progress toward the Sprint Goal and to identify any impediments or challenges that may hinder them from completing the work in the Sprint Backlog1. The Scrum Master can help the Developers remove these impediments or find ways to overcome them2.

D. A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal.

The Daily Scrum is also an opportunity for the Developers to adapt their plan for the next 24 hours based on their current situation and the Sprint Goal1. The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work1. This creates focus and improves self-management.

B, C, and E are not intended outcomes of the Daily Scrum.

B. An update of completed tasks and of the remaining work so the Scrum Master can plan the next day.

The Daily Scrum is not a status meeting or a report for the Scrum Master or anyone else2. The Developers are responsible for conducting and facilitating the Daily Scrum, not the Scrum Master1. The Scrum Master’s role is to ensure that the event happens, that it is positive and productive, and that it stays within the 15-minute timebox2.

C. An updated Scrum board to make Sprint progress transparent for the stakeholders.

The Daily Scrum is an internal meeting for the Scrum Team, not for external stakeholders1. The Scrum board is a tool that can help the Developers visualize their work, but it is not an outcome of the Daily Scrum. The outcome of the Daily Scrum should be an updated Sprint Backlog and an updated Sprint plan to achieve the Sprint Goal3.

E. A status report for the upper management indicating what each individual has done, will be doing, and what is impeding him/her.

The Daily Scrum is not a status report for anyone, especially not for upper management2. The purpose of the Daily Scrum is to inspect and adapt the work of the Developers, not to report on individual activities or performance1. The focus of the Daily Scrum should be on the collective work and progress of the Developers as a self-organizing team2.

The correct answer is D, because the recommended size for a Development Team is 3 to 9 members. The Scrum Guide states that “fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful.”

The next Sprint begins immediately after the conclusion of the previous Sprint, as stated in the Scrum Guide: “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.”

According to the Scrum Guide, a Scrum Team is cross-functional if it includes skilled individuals who together have all the skills necessary to create value each Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of cross-functionality, as they either imply that the Developers work in silos or rely on external people (such as business analysts, architects, testers, or separate teams).