Top 30 Scrum Master Interview Questions and Answers for 2025

Scrum Master interviews in enterprise organisations have evolved significantly. The "what are the 5 Scrum values?" questions still appear, but they are rarely the deciding factor. What separates shortlisted candidates is scenario handling — demonstrating that you know what to actually do when a stakeholder demands a mid-sprint scope change or a team member stops participating in ceremonies. This guide covers the 30 questions that come up most consistently.

Scrum Foundations (Questions 1–8)

Q1: What is the difference between a Scrum Master and a Project Manager?

Strong answer: A Project Manager manages scope, time, and cost — they are the decision authority. A Scrum Master serves the team by removing impediments, coaching on Agile practices, and facilitating events. The SM does not assign work, make delivery decisions, or manage performance. The authority model is fundamentally different: PM is directive, SM is facilitative.

Q2: Can a Scrum Master also be the Product Owner?

Strong answer: The Scrum Guide says these roles should not be combined — they create inherent conflicts of interest. The SM should protect the team from over-commitment; the PO wants maximum scope delivered. These incentives conflict. In practice, many small organisations combine them. If asked to do both, acknowledge the conflict explicitly and establish guardrails.

Q3: What is the Sprint Goal and why does it matter?

Strong answer: The Sprint Goal is the single objective that gives the sprint coherence and provides the team flexibility in how they achieve it. It matters because it allows the team to adapt within the sprint — if an approach to a story isn't working, the Sprint Goal tells them what constraint they're working within. A sprint without a goal is just a list of tasks.

Q4: How do you handle a team member who never participates in the Daily Scrum?

Strong answer: First understand why — is it a time zone issue, a feeling of irrelevance, or resistance to the format? I'd have a private conversation before addressing it in the team. If the Daily Scrum format isn't serving that person, we might need to change the format rather than enforce attendance. The goal is team synchronisation, not a status meeting.

Facilitation Scenarios (Questions 9–16)

Q5: A stakeholder demands we add a high-priority feature mid-sprint. What do you do?

Strong answer: First, I clarify whether this is truly urgent enough to warrant sprint disruption. If yes, I bring it to the Product Owner and team — adding to the sprint means removing something of equivalent size. If the stakeholder insists on adding without removing, the only clean options are to cancel the sprint or to protect the Sprint Goal and add the request to the next sprint backlog. I would not simply add scope to the sprint.

Q6: Two senior developers have a persistent conflict that is affecting team morale. How do you handle it?

Strong answer: I'd start with individual conversations to understand each person's perspective without the other present. Then a joint conversation using a coaching approach — not mediation, but helping them articulate what they need from each other. If the conflict is about technical direction, a team decision-making framework (like a Technical Design Record process) can depersonalise it. If it's interpersonal, I'd involve HR if individual conversations don't progress.

Q7: Your team's velocity has dropped 30% over the last three sprints. What do you do?

Strong answer: First, investigate before drawing conclusions. A velocity drop could mean: new team members being onboarded (expected productivity dip), increased technical debt forcing rework, scope inflation in story estimates, external impediments not being tracked, or team members being pulled into other projects. I'd use the retrospective to surface the root cause rather than treating velocity as a target to recover.

Q8: How do you run a retrospective when the team says "everything is fine"?

Strong answer: "Everything is fine" is usually a psychological safety signal, not an accurate assessment. I'd try a different format — something that doesn't require public vulnerability, like anonymous pre-retro surveys or a Lean Coffee format where the team chooses the agenda. Sometimes changing the room helps. If it's a recurring pattern, I'd address psychological safety directly as a topic rather than trying to surface problems through the retrospective format.

Tools and Technical Questions (Questions 17–22)

Q9: How do you use Jira to manage sprint impediments?

Strong answer: I create a dedicated Impediment issue type (or use the Epic type with a specific label) and maintain a live impediment register visible on the SM dashboard. Each impediment has: description, date raised, owner (me initially), escalation level, and target resolution date. I review the register in Daily Scrum and update status. The register is part of my Sprint Review reporting — stakeholders should know what's blocking delivery and what I'm doing about it.

Q10: What is your experience with scaling frameworks beyond Scrum?

Strong answer: This is where covering all four frameworks in your answer distinguishes you. Briefly cover: SAFe (if they're using it — PI Planning, ARTs, the Lean-Agile principles), LeSS (if they're multi-team with a single product), Nexus (if they want lightweight scaling), Scrum@Scale (if they want fractal Scrum). Demonstrate you can choose a framework based on context, not just name them.

Behavioural Questions (Questions 23–30)

Q11: Tell me about a time you removed a significant impediment.

Strong answer structure: Situation (what was the impediment and what was its impact on delivery?), Action (what specifically did you do — who did you talk to, what escalation path did you take?), Result (quantified impact — sprint velocity recovered, release date maintained, etc.). Avoid vague answers. Specificity signals real experience.

Q12: How do you handle a manager who keeps assigning tasks directly to team members, bypassing the backlog?

Strong answer: This is a common anti-pattern — the manager hasn't transitioned from traditional project management. I'd have a direct conversation with the manager about the impact: task injection creates invisible work, breaks sprint commitments, and creates unfairness in the team. I'd offer an alternative — a fast-track request process where urgent items go to the Product Owner for backlog prioritisation within 24 hours. Making the process visible is more effective than making it a confrontation.