Scrum Master interview questions (2026): 20 answers that actually land

What does a Scrum Master actually do day to day?

A Scrum Master is accountable for the team's effectiveness. In practice that means removing impediments the team cannot remove alone, coaching Developers and the Product Owner toward self-management, and protecting the Sprint Goal from mid-Sprint change.

Interviewers use this to filter out candidates who memorised the Scrum Guide but never held the role. Good answers describe a rhythm: pairing with the Product Owner on refinement, unblocking one thing per day, and running Retrospectives that change behaviour instead of producing a list of grievances.

What is the difference between a Scrum Master and a project manager?

A project manager owns scope, schedule, and staffing. A Scrum Master owns none of these. They own the effectiveness of the team and the organisation's understanding of Scrum. If your answer includes 'assigning tasks' or 'chasing dates', you are describing a project manager.

How do you introduce Scrum to a team new to it?

Start with the empirical loop, inspect and adapt, not the ceremonies. Teach the events as the thing that makes the loop happen. If a team runs the ceremonies without understanding the loop, they end up doing Scrum theatre.

How do you handle a stakeholder who tries to add scope mid-Sprint?

Redirect the request to the Product Owner and reinforce that only the PO changes the Sprint Backlog, and only if it does not endanger the Sprint Goal. If the change is important, it belongs in refinement for a future Sprint.

How do you deal with a Product Owner who will not order the backlog?

Coach them on why ordering is theirs alone, and make the cost of not ordering visible. If refinement stalls without an ordered backlog, do not fill the gap by ordering it yourself. Let the impact land, then help them see it.

What is a Sprint Goal and how do you help write one?

It is the single focus the increment must achieve. Help the PO frame it in one line that answers 'why bother with this Sprint at all'. If the team cannot recite it on day three of the Sprint, it was not a Sprint Goal, it was a wish list.

A Developer asks you for the technical solution. What do you do?

Ask questions that help them find it themselves. The Scrum Master's job is to grow the team's capability, not to be the answer key. If you solve their problem you make them dependent on you and weaker for the next one.

The team keeps missing the Sprint Goal. What is your first move?

Take it into the Retrospective, not the Daily. Look for a pattern: is the goal being written too late, is refinement thin, is capacity being overrun by unplanned work. Fix the upstream cause; do not just push the team to work harder.

How do you handle conflict between two Developers?

Facilitate a conversation between them, do not adjudicate. Coach the team on healthy disagreement being a sign of engagement, and use the Retrospective to build a working agreement that handles the next one better.

How do you handle a team that is not self-managing?

Identify what they are avoiding. Self-management usually stalls on one of three things: unclear ownership, missing skill, or fear of consequences. Address the specific one; do not lecture the whole team on autonomy.

Your team says the Daily Scrum is a waste of time. What do you say?

Ask what they would do instead to inspect progress toward the Sprint Goal daily and adapt the plan. If the Daily has drifted into a status meeting, that is a facilitation issue, not a problem with the event.

What is the Definition of Done and why does it matter?

It is the shared checklist that makes an increment releasable. Without it, 'Done' means different things to different people and quality erodes Sprint over Sprint. The Scrum Master coaches the team to make it explicit and to raise the bar over time.

What do you do in Sprint Planning?

Facilitate the team through three questions: why is this Sprint valuable (the Sprint Goal), what can we Done, and how will we do it. Your job is timekeeping and clarity, not deciding the plan.

How do you run a Retrospective people actually want to attend?

Rotate the format, focus on one outcome instead of a list, and make sure the last action item was actually done before you propose a new one. Nothing kills a Retrospective faster than watching last Sprint's improvements evaporate.

Should the Scrum Master attend the Sprint Review?

Yes, as a participant. They help facilitate the collaboration between stakeholders and the team, but the Product Owner leads it. The Scrum Master's presence is not optional; the event is part of the empirical loop.

How do you know your Scrum team is doing well?

Three signals: they meet the Sprint Goal most Sprints, the increment is truly Done every Sprint, and their Retrospective produces one concrete change they actually adopt. Velocity is not a measure of team health.

How do you measure your own impact as a Scrum Master?

Track whether the team needs you less over time. A great Scrum Master makes themselves increasingly unnecessary to daily operations and increasingly valuable at the system level, coaching PO relationships, unblocking cross-team dependencies, growing engineering practices.

How do you scale Scrum across multiple teams?

Start with the smallest framework that makes the dependencies visible, Nexus or LeSS, and only add coordination structure when a real problem demands it. Adopting SAFe on day one is usually a symptom that the organisation wanted a project plan, not Scrum.

Tell me about a time you removed a real impediment.

Pick a story where you removed something structural, a broken CI pipeline, a permission bottleneck, a stakeholder who kept interrupting, not a task you did for a Developer. Show the diagnosis, the action, and the sustained effect.

What is your biggest weakness as a Scrum Master?

Pick a real one that you are actively working on: solving problems for teams instead of coaching, over-facilitating, avoiding hard conversations with stakeholders. Show the reps you take against it, not a rehearsed strength in disguise.