CSM Exam Dumps : Certified ScrumMaster Exam

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.

Product Backlog management is primarily the responsibility of theProduct Owner. One of their key activities is toclearly express Product Backlog items, ensuring they are transparent and understandable for the Developers. This helps the Scrum Team deliver valuable Increments.

According to the2020 Scrum Guide, Product Backlog management includes:

Clearly expressing Product Backlog items.

Ordering the items to maximize value.

Ensuring the Product Backlog is transparent, visible, and understood.

Why the other options are incorrect:

B. Creating Sprint tasks:Sprint tasks are part of the Developers’ detailed planning during the Sprint and are not part of Product Backlog management.

C. Facilitating the Daily Scrum:This is a responsibility of the Developers, and the Scrum Master may only facilitate if explicitly requested.

D. Planning the Sprint Backlog:The Sprint Backlog is planned during Sprint Planning and is primarily the Developers' responsibility, not part of Product Backlog management.

TheScrum Mastershould coach the Developers byexplaining the intent of the Daily Scrum, which is toinspect progress toward the Sprint Goaland adapt the plan as needed. The Daily Scrum is not a status update meeting—it is a collaborative event for the Developers to synchronize their efforts, share progress, and discuss any impediments.

According to the2020 Scrum Guide:

The Daily Scrum is a15-minute eventwhere the Developers inspect their progress and adapt their plan to achieve the Sprint Goal.

The event belongs to the Developers, and they decide how to structure it, but its purpose must align with the framework’s guidance.

Why the other options are incorrect:

B. Cancel the Daily Scrum and have status update meetings instead:Status update meetings go against Scrum principles, which emphasize team ownership and collaboration.

C. Reduce the occurrence for this meeting to once a week:The Daily Scrum is adailyevent for inspection and adaptation; reducing its frequency would hinder the team’s ability to remain aligned.

D. Make Daily Scrum an optional meeting for the Developers to attend:The Daily Scrum is mandatory for the Developers to inspect and adapt their plan, and making it optional undermines its importance.