CSM Exam Dumps - Scrum Alliance Scrum Master Questions and Answers

When Developers ask for help or admit they do not know something, they demonstrateCourage, one of the five Scrum Values. It takes courage to be open about challenges or limitations and seek assistance, as it fosters collaboration, transparency, and trust within the team.

According to the2020 Scrum Guide, the Scrum Values include:

Commitment: Dedicated to the team’s goals and delivering value.

Focus: Concentrating on the Sprint Goal and avoiding distractions.

Openness: Transparent about work and progress.

Respect: Valuing each other's contributions and perspectives.

Courage: Taking risks, speaking up, and tackling challenges.

Why the other options are incorrect:

A. Respect:Respect is about valuing team members' contributions, but asking for help reflects personal courage.

C. Commitment:Commitment relates to dedication to achieving goals, not specifically asking for help.

D. Focus:Focus involves prioritizing and working toward the Sprint Goal, not addressing knowledge gaps or challenges.

The Product Owner is accountable forcreating and ordering Product Backlog itemsto maximize the value of the product. This includes clearly expressing Product Backlog items, ordering them to maximize value, and ensuring that the Product Backlog is transparent and understood.

According to the2020 Scrum Guide, the Product Owner is accountable for:

Maximizing the value of the product resulting from the work of the Scrum Team.

Effectively managing the Product Backlog by ensuring it is prioritized and transparent.

Creating Product Backlog items in collaboration with stakeholders and the Scrum Team.

Why the other options are incorrect:

A. Describe the solution:The Product Owner defines the "what" (desired outcomes), not the technical "solution," which is determined by the Developers.

B. Manage the Developers:The Product Owner does not manage the Developers. Developers are self-managing and self-organizing.

D. Recognize titles:Titles have no significance in Scrum, and this is not a responsibility of any Scrum role.

TheDaily Scrumis a short, time-boxed event (15 minutes) where Developers inspect progress toward the Sprint Goal and adapt their plan for the day. It is not intended to solve problems or deep-dive into discussions. If a major technical issue is identified during the Daily Scrum, the team should note it and arrange to discuss and solve itoutside of the Daily Scrum.

According to the2020 Scrum Guide:

The Daily Scrum is focused on progress toward the Sprint Goal, and issues that require detailed discussion or resolution should be handled separately.

The Scrum Master may help facilitate these follow-up discussions if needed.

Why the other options are incorrect:

B. Interrupt the Daily Scrum and solve the problem immediately:The Daily Scrum is not a problem-solving session. Interrupting it for detailed discussions disrupts its purpose and timebox.

C. Escalate it to the Product Owner:Technical issues are typically handled by the Developers, not the Product Owner, who is responsible for managing the Product Backlog and ensuring value delivery.

D. Discuss it during the Sprint Review:Waiting until the Sprint Review to discuss atechnical issue would delay resolution and risk jeopardizing the Sprint Goal.

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.

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.

TheProduct Ownerhas the final authority toorder the Product Backlogto maximize value. They are responsible for ensuring that the most valuable and important work is prioritized so that the Scrum Team delivers maximum value in each Sprint.

According to the2020 Scrum Guide:

The Product Owner is accountable formanaging the Product Backlog, which includes ordering items to best achieve the Product Goal.

While the Developers may provide input, the final decision on ordering lies with the Product Owner.

Why the other options are incorrect:

A. Lead Developer:Scrum does not have a "Lead Developer" role or accountability.

B. Scrum Master:The Scrum Master facilitates and coaches but does not manage or order the Product Backlog.

D. Developers:While Developers provide input during refinement and Sprint Planning, they do not have the authority to order the Product Backlog.

TheScrum Masteris responsible for leading and coaching the organization in its Scrum adoption. They play a critical role in helping the organization understand and implement Scrum practices, fostering an environment of empiricism and continuous improvement.

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

Leading, training, and coaching the organization in Scrum adoption.

Helping employees and stakeholders understand and enact an empirical approach to work.

Removing barriers between stakeholders and Scrum Teams.

Why the other options are incorrect:

A. Customer:Customers provide requirements and feedback but do not lead or coach the organization in Scrum adoption.

B. Product Owner:The Product Owner manages the Product Backlog and focuses on delivering value but is not responsible for organizational Scrum adoption.

C. Developers:Developers are responsible for delivering the Increment and are not accountable for coaching the organization.

TheDaily Scrumis the event where impediments to achieving the Sprint Goal are shared. It is a time-boxed event (15 minutes) held every day during the Sprint. During this event, the Developers inspect their progress toward the Sprint Goal and identify any blockers or impediments that need to be addressed.

According to the2020 Scrum Guide:

The Developers use the Daily Scrum to inspect progress andadapt their planto achieve the Sprint Goal.

Impediments are raised and addressed by the Scrum Master if they cannot be resolved by the team.

Why the other options are incorrect:

B. Sprint Planning:Sprint Planning is focused on creating the Sprint Goal and selecting Product Backlog items for the Sprint, not sharing impediments.

C. Sprint Retrospective:The Retrospective focuses on process improvements and team dynamics, not day-to-day impediments during the Sprint.

D. Sprint Review:The Sprint Review is about presenting the Increment and gathering feedback, not resolving impediments.

DuringSprint Planning, the Scrum Team plans the work to be performed in the upcoming Sprint. The event is time-boxed and is attended by the entire Scrum Team. The main outcomes of Sprint Planning are:

A Sprint Goalthat defines the purpose of the Sprint.

Selected Product Backlog itemsthat are forecasted to be delivered during the Sprint.

A plan for how the work will be completed, which is created by the Developers.

Why the other options are incorrect:

B. Demo of the previous increment is done:Demonstrations and feedback occur during the Sprint Review, not Sprint Planning.

C. Customers will share the feedback:Feedback from customers is gathered during the Sprint Review, not Sprint Planning.

D. The Product Backlog is refined:Product Backlog refinement is an ongoing activity, not a specific focus of Sprint Planning.

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.