Daily Scrum runs over 15 minutes; what facilitation techniques realign it?

WHAT THIS TESTS: The interviewer is checking whether you understand that the Daily Scrum is a formal event for inspection and adaptation, not a status meeting for stakeholders. They want to see that you know the Scrum Master fosters an environment where the team self-manages, and that specific facilitation tactics are context-sensitive tools outside the Scrum Guide. The question separates candidates who know mechanics from those who understand empirical process control.

A GOOD ANSWER COVERS: First, reframe the purpose by reminding the team that the event exists to inspect progress toward the Sprint Goal and adapt the upcoming plan, which aligns with Scrum theory. Second, introduce a parking lot or follow-up list so that problem-solving topics are captured but deferred until after the timebox, preserving the focus on adaptation. Third, coach the developers to self-manage the timebox rather than having the Scrum Master police it, perhaps by making the timer visible or rotating facilitation. Fourth, shift the conversation pattern from reporting to each other to talking about the work itself, such as walking the board and discussing only items that need team adaptation.

COMMON WRONG ANSWERS: A major red flag is suggesting the Scrum Master extend the 15-minute limit because complex work needs more discussion; this masks dysfunction and reduces transparency. Another is proposing that the Scrum Master control speaking order or cut people off unilaterally, which replaces self-management with command and control. A third is inviting stakeholders to attend and turning the event into a review or planning session, which violates the event's purpose.

LIKELY FOLLOW-UPS: The interviewer may ask how you would handle a senior leader who attends and turns the Daily Scrum into a status report. They might ask what you do if the team ignores the parking lot and continues long conversations. They could also ask how your facilitation changes for a distributed team or whether you would cancel the Daily Scrum if the team finds it redundant.

ONE CONCRETE EXAMPLE: A Scrum Master noticed a team of seven developers consistently ran 30 minutes because they debated implementation details during the Daily Scrum. She introduced a visible parking lot on a whiteboard and asked the team to agree that only topics requiring same-day adaptation belonged in the event. When a developer raised a design question, she asked whether it blocked the Sprint Goal today; if not, it moved to the parking lot. She also suggested the team walk the board instead of person-by-person updates. Within three Sprints, the team averaged 10 minutes and voluntarily scheduled a 20-minute huddle after for parked items, improving both focus and collaboration.