How to fix a Daily Scrum that runs over its timebox?

WHAT THIS TESTS: This question tests your understanding of the Daily Scrum's core purpose as defined by the Scrum Guide: it's a planning event for the Developers, not a status report for managers or a problem-solving session. The interviewer wants to see if you can diagnose the anti-pattern and apply facilitation techniques to guide the team back to correct principles, rather than just enforcing a rule. It's about coaching, not commanding.

A GOOD ANSWER COVERS: A strong answer outlines a multi-step approach. First, re-state the purpose. Start by reminding the team that the Daily Scrum is for inspecting progress toward the Sprint Goal and creating a plan for the next 24 hours, not for solving the problems themselves. Second, introduce a specific facilitation technique. The 'parking lot' is a classic. When a deep discussion starts, acknowledge its importance and say, 'That's a great point. Let's put it in the parking lot and circle back right after the Daily Scrum with the right people.' This respects the issue without derailing the event. Third, actively manage the timebox. As Scrum Master, you can say, 'We have 5 minutes left, let's make sure everyone has a chance to sync up.' Fourth, address the root cause. The need for problem-solving is real. A good answer includes scheduling a separate, optional follow-up meeting immediately after the Daily Scrum for those involved in the 'parking lot' items. This ensures problems are actually solved, just not during the Daily Scrum.

COMMON WRONG ANSWERS: A common red flag is focusing on rules over team effectiveness. Simply cutting people off with 'Time's up, meeting over' without providing an outlet for the discussion frustrates the team. Blaming individuals by calling out specific people for talking too long damages psychological safety. Another mistake is suggesting everyone just answer the old 'three questions' (what I did, what I'll do, any blockers) without focusing on the plan to meet the Sprint Goal. The worst answer is suggesting you extend the timebox to 30 minutes, which directly violates a core Scrum rule and indicates a misunderstanding of the event's purpose.

LIKELY FOLLOW-UPS: Expect questions that probe deeper. For example, 'What if the same people keep derailing the conversation every day?' which tests your ability to handle persistent issues through 1-on-1 coaching. Or, 'What if the parking lot follow-up meetings start taking an hour every day?' which tests your ability to identify systemic problems like poor refinement or technical debt. You might also be asked, 'The Scrum Guide says the Daily Scrum is for the Developers. What is your role as Scrum Master in this meeting?' The answer is to facilitate: ensure the event happens, is positive, productive, and kept within the timebox.

ONE CONCRETE EXAMPLE: 'On a previous team, our Daily Scrum regularly hit 25-30 minutes. I raised it in a Retrospective to get the team's perspective. We agreed the problem-solving was valuable, but the timing was wrong. I introduced a physical 'parking lot' on the whiteboard. When a deep dive began, I'd walk to the board, write down the topic and the people involved, and say, 'Great topic for an offline sync. Let's park it and tackle it right after this.' Within a week, the Daily Scrum was back to 15 minutes, and the problem-solving was more focused because only the necessary people attended the follow-up.'