Pass the Scrum Alliance Scrum Master CSM Questions and answers with ValidTests

The correct statement is:An Increment must be in a usable condition and meet the Definition of Done. Each Increment builds upon previous Increments and must be complete, usable, and meet the agreed-uponDefinition of Doneso it can be inspected during the Sprint Review. Whether or not the Increment is released is a separate decision made by the Product Owner.

According to the2020 Scrum Guide:

An Increment is the result of work done during a Sprint and must meet the Definition of Done.

The Increment isusable, even if the Product Owner decides not to release it.

Why the other options are incorrect:

A. It must have all of the requirements that need to be in the product before the Product Owner will release it:Increments do not require all requirements to be complete before being usable or inspectable. Scrum is iterative, delivering value incrementally.

B. Is not releasable until the Product Owner determines it is done:The Product Owner does not determine whether the Increment is "done"; the team’s adherence to the Definitionof Done determines this.

D. Is not releasable until it has all of the features to be a Minimally Viable Product:Each Increment must meet the Definition of Done, regardless of whether it meets all features for an MVP.

TheSprint Retrospectiveis a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. This event focuses oncontinuous improvementby reviewing processes, collaboration, tools, and their adherence to the Definition of Done.

According to the2020 Scrum Guide, the Sprint Retrospective serves the following purposes:

Toinspecthow the last Sprint went in terms of individuals, interactions, processes, tools, and the Definition of Done.

To identify andagree upon actionable improvementsthat will increase the team's effectiveness in future Sprints.

Why the other options are incorrect:

B. Plan the incomplete work for the next Sprint and submit reasons to the Product Owner:This is not the purpose of the Sprint Retrospective. Sprint Planning is the event where the team plans the upcoming Sprint.

C. Explain what Backlog items have been done and what has not been done:This describes the Sprint Review, where the team discusses completed and incomplete Product Backlog Items with stakeholders.

D. Identify Developers who did not perform well in the Sprint:Scrum encourages collaboration, respect, and continuous improvement, not blaming individuals for shortcomings.

When the Scrum Team does not understand the goal, scope, or product domain, theScrum Master should facilitate a discussion between the Stakeholders, Product Owner, and Developers. This ensures clarity and shared understanding, enabling the team to move forward effectively.

According to the2020 Scrum Guide, the Scrum Master serves the team by:

Facilitating stakeholder collaborationas needed.

Ensuring that the Product Backlog is understoodby the Scrum Team.

Removing any barriers that hinder the team's ability to achieve the Sprint Goal.

Why the other options are incorrect:

A. Direct the Developers to stop working until the Product Owner improves the acceptance criteria:Stopping work is not productive, and collaboration with the Product Owner and stakeholders is the proper approach to resolving misunderstandings.

B. Cancel the Sprint and schedule a new Planning meeting:Cancelling the Sprint should be an absolute last resort and is typically done only when the Sprint Goal becomes unachievable.

C. Do nothing because this is the responsibility of the Product Owner:While the Product Owner owns the Product Backlog, the Scrum Master is responsible for facilitating collaboration and resolving impediments.

Thethree Scrum artifacts—Product Backlog,Sprint Backlog, andIncrement—providetransparencyinto the work and enable opportunities forinspection and adaptation. These artifacts are essential to ensuring the Scrum Team and stakeholders can inspect progress and adapt plans to maximize value.

According to the2020 Scrum Guide:

Product Backlog: Represents all the work needed to achieve the Product Goal and allows inspection and prioritization of upcoming work.

Sprint Backlog: A real-time plan for the Sprint that provides transparency into what the team is working on and allows inspection and adaptation during the Sprint.

Increment: The outcome of the Sprint that is usable and meets the Definition of Done, enabling stakeholders to inspect progress and provide feedback.

Why the other options are incorrect:

A. Burndown Charts, release plan and Product Backlog:Burndown charts and release plans are complementary tools, but they are not official Scrum artifacts.

C. Definition of Done and Product Backlog:The Definition of Done is not an artifact but a shared understanding of when work is complete.

D. Definition of Done, Sprint Backlog and Product Backlog:While the Sprint Backlog and Product Backlog are artifacts, the Definition of Done is not.

TheScrum Mastershouldcoach the Scrum Teamto understand the importance of theSprint Retrospective. This event is essential for inspecting and adapting processes, tools, and team dynamics, enabling continuous improvement in future Sprints.

According to the2020 Scrum Guide:

TheSprint Retrospectiveis a key event where the Scrum Team reflects on their performance and identifies actionable improvements.

It promotes collaboration, accountability, and self-management, all of which are crucial in Scrum.

Why the other options are incorrect:

B. Let the Developers decide:The Sprint Retrospective is a mandatory event for the Scrum Team, and the Developers cannot decide to skip it.

C. Escalate to the Product Owner:The Product Owner is not responsible for team dynamics or facilitating Scrum events. This is the Scrum Master’s responsibility.

D. Exclude those members of the Scrum Team from participating:Excluding team members would undermine team collaboration and the purpose of the event. Instead, the Scrum Master should address the underlying concerns and help the team recognize its value.

Incremental processrefers to building and delivering software in small, usable pieces (Increments). In Scrum, each Increment is a usable part of the product that adds value and meets the Definition of Done.

According to the2020 Scrum Guide:

The Increment isa concrete step toward the Product Goal.

Increments allow for frequent inspection and adaptation while ensuring transparency of progress.

Why the other options are incorrect:

A. An iterative process:While Scrum is iterative, "iterative" describes repeated cycles of planning and improving, whereas "incremental" refers to delivering usable pieces of the product.

C. A lifecycle process:This is a generic term for any process involving software development and does not specifically describe building in pieces.

D. A release process:A release process focuses on deploying software, not the incremental building of usable Increments.

TheSprint Retrospectiveis heldafter the Sprint Review and before the next Sprint Planning. It is the final event in the Sprint, and its purpose is to reflect on the past Sprint and identify areas for improvement. The Scrum Team inspects how they worked during the Sprint in terms of processes, interactions, tools, and the Definition of Done, and then adapts for future Sprints.

According to the2020 Scrum Guide:

The Sprint Retrospective is time-boxed and enables the team to inspect and adapt their working practices.

It helps improve the Scrum Team's effectiveness in subsequent Sprints.

Why the other options are incorrect:

B. At the beginning of the Sprint:The Sprint Retrospective is not held at the start of the Sprint. Sprint Planning occurs at the beginning of the Sprint.

C. In the middle of the Sprint:Mid-Sprint is not a designated time for this meeting; the team is focused on achieving the Sprint Goal.

D. At the end of all the Sprints:The Retrospective is held at the end ofeach Sprint, not at the conclusion of all Sprints.

One of the key services aScrum Master provides to the Product Owneris helping them findeffective Product Backlog management techniques. This ensures that the Product Owner can maximize the value of the product and effectively manage the Product Backlog.

According to the2020 Scrum Guide, the Scrum Master serves the Product Owner by:

Helping the Product Owner find techniques for effective Product Goal definition and Product Backlog management.

Facilitating stakeholder collaboration when needed.

Supporting empirical product planning for complex environments.

Why the other options are incorrect:

A. Assign tasks to the Developers:Tasks are not assigned in Scrum. Developers are self-organizing and responsible for determining how they will complete the work.

B. Write user stories:Writing user stories is a Product Owner responsibility, not the Scrum Master's.

C. Prioritize the backlog:The Product Owner prioritizes the Product Backlog, not the Scrum Master.

TheSprint Backlogis owned solely by theDevelopers, as they are responsible for planning, managing, and executing the work required to meet the Sprint Goal. The Sprint Backlog is ahighly visible, real-time planfor delivering the Increment. It includes:

TheSprint Goal.

The set of Product Backlog items selected for the Sprint.

A plan for delivering the Increment.

According to the2020 Scrum Guide, the Developers:

Have full ownership and accountability over the Sprint Backlog.

Decide how to adapt their work plan daily to achieve the Sprint Goal.

Why the other options are incorrect:

A. Scrum Master:The Scrum Master facilitates the Scrum process but does not own the Sprint Backlog.

C. Product Owner:The Product Owner manages the Product Backlog, not the Sprint Backlog.

D. Scrum Team:While the Sprint Goal is owned by the entire Scrum Team, the Sprint Backlog is specifically managed and executed by the Developers.

One of the primary services a Scrum Master provides to the Scrum Team isremoving impedimentsto the team’s progress. By doing so, the Scrum Master ensures that the team can work without unnecessary disruptions and remain focused on achieving the Sprint Goal.

According to the2020 Scrum Guide, the Scrum Master serves the Scrum Team in several ways, including:

Coaching the team in self-management and cross-functionality.

Helping the team focus on creating high-value Increments.

Removing impediments to the team’s progress.

Why the other options are incorrect:

A. Prioritize the Sprint Backlog:This is the Product Owner's responsibility as part of Product Backlog management.

B. Develop a release plan:Scrum does not require a release plan, and if it is needed, the Product Owner leads this activity with input from the Developers.

C. Manage the Product Backlog:Managing the Product Backlog is the Product Owner's accountability, not the Scrum Master's.