In every Daily Scrum the Developers stand in a circle and each one reports yesterday, today and blockers to the Scrum Master, who writes the blockers down and answers questions. Nobody has mentioned the Sprint Goal in a fortnight. What should the Scrum Master do?

Professional Scrum Master I, objective 2. Developing people and teams medium

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 Keep the three questions but ask the Developers to address them to each other instead

Wrong, though it is the closest miss here: changing who people face does not change what the event produces. The problem is not the seating, it is that nobody is inspecting progress toward the Sprint Goal or replanning the day.

Correct Step out of the centre and coach the Developers to run the event around progress toward the Sprint Goal and the next day's plan

Correct. The Daily Scrum belongs to the Developers, who may choose whatever structure they like provided it focuses on progress toward the Sprint Goal and produces an actionable plan for the next day. A Scrum Master receiving reports has quietly become the audience the event is performed for.

Not correct Hand the facilitation to the Product Owner, who can then relay progress to stakeholders

Wrong. That swaps one audience for another and gives the Developers' planning event to someone else. The Product Owner attends the Daily Scrum as a Developer only when actively working on Sprint Backlog items.

Not correct Replace the Daily Scrum with a shared board the Scrum Master reviews each morning

Wrong. Removing an event is not a fix for running it badly, and a board tells you where work sits, not what the Developers now intend to do about the Sprint Goal today.

Why

The Daily Scrum has one purpose — inspect progress toward the Sprint Goal and adapt the Sprint Backlog — and Scrum deliberately leaves its format open so that purpose, not a script, drives it. The status-report failure is diagnosable by asking one question: if the Scrum Master left the room, would the event still be worth holding? If the answer is no, the Developers are not self-managing their day, they are reporting on it, and the Scrum Master's service is to coach that back rather than to preside over it.

Where this comes from

Cited
Scrum Guide section Daily Scrum
What it says
The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.

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

All questions on Developing people and teams