A Scrum Team's Daily Scrum floats: some days at 9:15 in a meeting room, some days at 11:00 on a video call, twice last week not at all because "the calendar was full". A Developer asks the Scrum Master why this matters. What is the best answer?
Professional Scrum Master I, objective 2. Developing people and teams easy
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
The options
Not correct It does not matter where or when, as long as fifteen minutes are spent on it on most days
Wrong on both counts. The event is held every working day of the Sprint, and the fixed time and place are part of how Scrum keeps it cheap to hold.
Not correct It matters only because the Scrum Master needs a predictable slot to collect impediments
Wrong. The event exists for the Developers to inspect progress toward the Sprint Goal and replan their day; a Scrum Master's convenience is not the reason for its regularity.
Correct The Daily Scrum is held at the same time and place every working day of the Sprint, precisely to reduce the complexity of arranging it
Correct. Fixing the time and place removes a daily negotiation and makes the event something the day is built around rather than something that competes with the calendar.
Not correct It matters because stakeholders need to know when they can join and ask questions
Wrong, and it is tempting because predictability does help outsiders. But the Daily Scrum is a fifteen-minute event for the Developers, and stakeholder questions have the Sprint Review.
Why
Scrum's events are deliberately boring in their logistics — same time, same place, ideally all of them so — because every minute spent deciding when to meet is a minute not spent inspecting or adapting. A floating Daily Scrum costs far more than the slot it saves: attendance becomes a decision, absence becomes normal, and the inspection point the Sprint Goal depends on quietly stops being daily.
Where this comes from
- Cited
- Scrum Guide section Daily Scrum
- What it says
- To reduce complexity, it is held at the same time and place every working day of the Sprint.
Practise this
Reading one question is not practice. The trainer will draw a set from objective 2 and space the ones you get wrong.
Practise Professional Scrum Master I
More questions on this objective
- A team lead who sits outside the Scrum Team has taken to opening the board every Monday and assigning each Sprint Backlog item to a named Developer for the week. The Developers say the assignments rarely match who is best placed to pick the work up. Who decides which Developer works on which item? machine-checked
- On day four of a two-week Sprint, a department head tells one of the five Developers to spend the rest of the week on a customer escalation for another product. The Sprint Goal depends on that Developer's work. What should the Scrum Master do? machine-checked
- During Sprint Planning, a solution architect who is not on the Scrum Team hands the Developers a task breakdown for each selected Product Backlog item and asks them to follow it. The Developers had planned to decompose the work differently. What does Scrum say about this? machine-checked
- A Scrum Team is reworking its Daily Scrum. They are tired of three questions each and want to try walking the board right to left instead, and they also want to know how much else about the event they are free to change. Which two of the following are genuinely theirs to decide? (Choose two.) machine-checked
- A Scrum Team has stopped keeping its Sprint Backlog current, and when a stakeholder asks how the Sprint is going the Developers reply that they are self-managing and will show the result at the Sprint Review. Two Sprints in a row have then missed the Sprint Goal. What is wrong here? machine-checked
- With three days of the Sprint left, the Developers agree among themselves to skip the security review and the automated regression suite, both of which are in the Definition of Done, so that two more items can be finished. They argue that as a self-managing team it is their call. Is it? machine-checked