Home Scrum Master Interview questions
Scrum Master interview questions
The questions people actually get asked for this role, and what each one is really testing.
What to expect
Scrum Master interviews mix questions about how you've actually run ceremonies with scenario questions that test judgement when a team or stakeholder pushes against the process. Expect the panel to probe whether you coach teams toward self-management or default to directing tasks, since that distinction is central to the role.
- Behavioural: Past experience questions about handling blockers, difficult team dynamics or process change, usually answered with STAR.
- Scenario/judgement: Hypothetical situations, such as scope creep mid-sprint or a disengaged team, testing how you'd apply Agile principles under pressure.
- Process walkthrough: Questions asking you to describe step by step how you'd run a ceremony, set up a board, or introduce metrics to a new team.
- Coaching/stakeholder: Questions about influencing product owners, developers or senior stakeholders who aren't following Agile practices well.
- Conceptual/technical: Questions checking your grasp of Scrum theory and how the role differs from adjacent roles like project manager.
Interviews typically open with background and how you came to Scrum Master work, move into two or three scenario or behavioural questions on team dynamics and blockers, then a process walkthrough on ceremonies or metrics. Larger organisations may include a second-round panel with a product owner or delivery lead focused on stakeholder handling and Agile maturity, before finishing with your questions for them.
- 1
Tell me about a time you helped a team resolve a persistent blocker that other approaches hadn't fixed.
Why they ask: Tests whether you actually remove impediments rather than just log them, which is the core servant-leader function of the role.
How to structure your answer: Use STAR: describe the situation and why earlier attempts hadn't worked, your specific actions to diagnose and escalate the blocker, and the outcome once it was resolved.
Example answer
“One team I supported had a recurring blocker where code reviews were sitting untouched for days because reviewers were spread across other projects. Standups kept surfacing it but nothing changed. I raised it directly with the team's manager outside the ceremony, proposed a rotating review roster with a same-day target, and tracked review turnaround as a visible metric on the board for a few sprints. Review wait time dropped noticeably and the team stopped raising it as a daily blocker.”
- 2
How would you run a sprint retrospective for a team that's grown cynical about retros feeling pointless?
Why they ask: Checks your facilitation skill and whether you can rebuild engagement in a ceremony rather than just running through the motions.
How to structure your answer: Walk through your plan step by step: how you'd diagnose why engagement dropped, what format changes you'd make, and how you'd close the loop on action items.
Example answer
“I'd start by asking the team privately what specifically felt pointless, usually it's that issues get raised but nothing changes. I'd shrink the retro's scope to two or three items maximum, assign an owner and a date to each, and open the next retro by reviewing what happened to last sprint's actions before raising anything new. Making the follow-through visible is usually what rebuilds trust in the format faster than changing the exercise itself.”
- 3
Walk me through how you'd set up sprint metrics like velocity and burndown for a team that's never tracked them before.
Why they ask: A direct process question testing practical Jira/Azure DevOps competence and understanding of what these metrics are actually for.
How to structure your answer: Give a step-by-step walkthrough: initial setup, what you'd explain to the team about purpose, and how you'd avoid the metrics being misused.
Example answer
“I'd start by getting stories properly estimated and sized in Jira so velocity has a consistent baseline, then set up a burndown chart against the sprint backlog. Before relying on either, I'd explain to the team that velocity is for our own planning, not a performance target, since teams that feel judged on it tend to inflate estimates. After two or three sprints we'd have a trend worth discussing rather than a single noisy number.”
- 4
A senior stakeholder asks you to add new scope to the current sprint halfway through. How do you handle it?
Why they ask: Tests whether you protect the sprint commitment and can push back on seniority without damaging the relationship.
How to structure your answer: Frame as judgement under pressure: state the principle you're protecting, how you'd communicate it to the stakeholder, and what alternative you'd offer.
Example answer
“I'd explain that adding scope mid-sprint puts the existing commitment at risk and ask what's driving the urgency. If it's urgent, I'd work with the product owner on what could be descoped to make room, rather than just piling it on top. Usually once a stakeholder sees the trade-off made explicit, they're willing to wait for the next sprint or accept a swap.”
- 5
How would you coach a product owner who keeps bringing vague or oversized user stories to sprint planning?
Why they ask: Probes your coaching approach with a peer rather than a direct report, and whether you address root causes instead of just flagging the symptom each time.
How to structure your answer: Describe your coaching approach: how you'd raise it constructively, what practical support you'd offer, and how you'd measure improvement.
Example answer
“I'd raise it one-on-one rather than in planning itself, and suggest we work through the backlog together before the next session using a simple template for acceptance criteria and splitting large stories. I'd keep offering that support for a few sprints rather than expecting it to stick after one conversation, and I'd know it was working once planning sessions stopped running long because of story ambiguity.”
- 6
How do you see the Scrum Master role differing from a project manager's?
Why they ask: Checks your grasp of Agile theory and whether you understand the servant-leader model rather than defaulting to a command-and-control style.
How to structure your answer: Answer as a direct conceptual explanation with a concrete example distinguishing the two.
Example answer
“A project manager typically owns the plan and directs tasks to hit deadlines, where a Scrum Master's job is to help the team own its own process and remove what's getting in the way of that. In practice that means I don't assign work in sprint planning, the team pulls it, but I will step in hard on removing a blocker or protecting the sprint boundary. The authority comes from the framework, not from me managing people directly.”