CSM Scrum Events Practice Question
A Scrum Team's Daily Scrum has become a 30-minute problem-solving session where Developers dive into technical design debates. The Scrum Master wants to refocus the event on its intended purpose. What should the Scrum Master do?
⚠ Common exam trap
It's easy for candidates to confuse the Daily Scrum's inspect-and-adapt purpose with a general team meeting where any topic can be discussed at length.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Teach the Developers that the Daily Scrum is a 15-minute event for inspecting progress toward the Sprint Goal and adapting the Sprint Backlog as needed.
The Daily Scrum exists for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is timeboxed to 15 minutes and is not a status report or a design workshop. The Scrum Master serves the team by coaching them on this purpose, helping them keep the event focused, and encouraging detailed discussions to happen outside the timebox.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Have the Scrum Master facilitate the Daily Scrum and assign each Developer a turn to report status to keep the meeting on track.
Why it's wrong here
The Daily Scrum is for the Developers and they own it; the Scrum Master does not facilitate it as a status meeting. Turning it into a round-robin status report directed at the Scrum Master undermines self-management. The Scrum Master should teach the purpose and let the Developers decide how to conduct the event.
- ✓
Teach the Developers that the Daily Scrum is a 15-minute event for inspecting progress toward the Sprint Goal and adapting the Sprint Backlog as needed.
Why this is correct
The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a problem-solving session. By coaching the team on this purpose and timebox, the Scrum Master helps them keep the event focused and use separate conversations for detailed technical discussions.
- ✗
Extend the Daily Scrum to 30 minutes to accommodate the technical discussions so the team does not lose valuable problem-solving time.
Why it's wrong here
Extending the Daily Scrum beyond 15 minutes violates the Scrum Guide's timebox and reinforces the wrong behavior. The Daily Scrum is designed to be short and focused. Technical problem-solving should happen immediately after or at another time, not by expanding the event itself, which would erode its purpose and efficiency.
- ✗
Cancel the Daily Scrum and replace it with a weekly technical design meeting, since the Developers already communicate continuously.
Why it's wrong here
Canceling the Daily Scrum removes a key inspect-and-adapt opportunity and is not permitted; the event is required. Replacing it with a weekly meeting would reduce daily transparency and coordination. The Scrum Master should instead help the team refocus the existing Daily Scrum on the Sprint Goal and keep it within its timebox.
About these practice questions
This CSM question is part of Courseiva's 312-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scrum Alliance exam blueprint
This CSM practice question is part of Courseiva's free Scrum Alliance certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CSM exam.