Scrum Master Interview Questions

Prepare for your scrum master interview with 10 expert-curated questions and sample answers covering facilitation, coaching, metrics, and conflict resolution.

behavioral Questions

What's the difference between a scrum master and a project manager?

behavioralbeginner

Sample Answer

A project manager owns delivery outcomes and directs work; a scrum master owns the team's process health and coaches the team to own delivery themselves. I don't assign tasks or report status upward as my core job — I remove impediments, improve flow, and grow the team's self-management until they barely need me. The success metric is the team's capability, not my control.

Tip: The servant-leadership distinction is the point — any whiff of command-and-control fails this question.

Tell me about a team you transitioned between agile frameworks. Why and how?

behavioralintermediate

Sample Answer

A platform team's work was 70% unplannable — support escalations and operational tasks — making sprint commitments theater. We transitioned from Scrum to Kanban deliberately: mapped the workflow, set WIP limits, kept retros and a weekly replenishment meeting, and replaced velocity with cycle time SLAs. Stakeholder satisfaction rose because forecasts became honest. The lesson: fit the framework to the work's nature, not the organization's habit.

Tip: Framework-agnostic judgment — Scrum and Kanban as tools, not religions — is what this probes.

How do you onboard yourself with a new team as their scrum master?

behavioralbeginner

Sample Answer

First two weeks: observe more than act. One-on-ones with every team member, the PO, and key stakeholders asking what works and what hurts; sit in ceremonies without changing them; read the data — cycle time, predictability, defect trends. Then I share what I heard back to the team and let them prioritize what we improve first. Prescribing changes before earning context is the classic new-SM failure.

Tip: The listen-first-then-mirror approach demonstrates the coaching posture the whole role rests on.

Some companies are cutting scrum master roles. Why should we hire you?

behavioraladvanced

Sample Answer

Because I justify the role in delivery outcomes, not ceremony attendance: teams I've coached improved predictability 30+ points and cut cycle time over a third — that's recovered capacity worth multiples of my cost. The role being cut is the meeting-scheduler version; what I do is flow engineering and team development that compounds. I'd invite you to measure me the same way: give me a team and a baseline, and judge the trend.

Tip: Answer the economic question with economics — confidence plus measurable outcomes, zero defensiveness.

technical Questions

Which metrics do you track, and which do you refuse to use?

technicalintermediate

Sample Answer

I track flow: cycle time, throughput, sprint predictability, and escaped defects — trends, not absolutes. I refuse velocity comparisons across teams and individual output measures like story points per person, because they corrupt estimation and teamwork the moment they become targets. Metrics are for the team's self-improvement conversations first, stakeholder reporting second.

Tip: Citing Goodhart's law dynamics around velocity weaponization is the experienced practitioner's marker.

Walk me through how you run a retrospective that doesn't go stale.

technicalbeginner

Sample Answer

Vary the format — sailboat, start-stop-continue, timeline — but the constant is psychological safety and follow-through. I cap output at three actions with owners and due dates, and open the next retro by reviewing them, because nothing kills retros faster than actions that vanish. When energy drops, I bring data in: cycle time charts or incident trends give the conversation something concrete to bite on. Action completion went from 30% to 85% with that discipline.

Tip: The three-actions-with-owners discipline and reviewing them next retro is the credibility detail.

situational Questions

Your team consistently fails to meet sprint commitments. How do you address it?

situationalintermediate

Sample Answer

Diagnose before prescribing: I'd analyze three sprints of data for patterns — is work underestimated, are stories arriving unclear, is mid-sprint interruption eating capacity, or are dependencies blocking? Each cause has a different fix: refinement quality, interrupt budgets, dependency mapping. At my last team the data showed 30% of capacity went to unplanned support work, so we made it visible with a rotating support role, and predictability rose from 61% to 92%.

Tip: Lead with data diagnosis, not ceremony tweaks — 'try harder at planning' is the answer to avoid.

Two senior engineers on your team are in open conflict. What do you do?

situationaladvanced

Sample Answer

First, separate the technical disagreement from the personal friction — they usually entangle. I'd talk with each privately to understand positions and feelings, then facilitate a structured conversation focused on the decision: criteria, options, trade-offs, often as a written decision doc that depersonalizes the argument. If respect violations continue, that becomes a direct conversation about behavior with escalation if needed. Conflict over ideas is healthy; contempt is not.

Tip: 'Depersonalize via decision criteria' plus knowing where coaching ends and escalation begins shows range.

How do you handle a product owner who keeps changing priorities mid-sprint?

situationalintermediate

Sample Answer

First understand why — chaotic stakeholders above them, weak backlog refinement, or genuine market urgency each need different help. Then make the cost visible: I track mid-sprint scope churn and show its impact on predictability and team morale in numbers. We agree on a working rule — true emergencies swap out equal scope, everything else waits for next sprint. At one team this cut churn 90% in two months.

Tip: Empathy for the PO's pressures plus a data-backed working agreement is the complete answer.

Leadership asks you to make the team 'go faster'. How do you respond?

situationaladvanced

Sample Answer

I translate 'faster' into what they actually need — usually predictability or earlier value, not raw speed. Then I show where time really goes: our cycle time data revealed work waited in review and dependency queues 60% of its life, so the leverage was WIP limits and dependency management, not pressure. Asking people to type faster optimizes the 40%; fixing flow optimizes the 60%. Leadership got a faster team and the team got protection from burnout theater.

Tip: 'Optimize flow, not effort' backed by wait-time data reframes the question the way strong SMs do.

Preparation Tips

1

Bring numbers: predictability, cycle time, and churn improvements from past teams — vague 'improved collaboration' claims sink candidates.

2

Prepare conflict stories at three levels: within team, with product owner, and with leadership.

3

Know Kanban as well as Scrum — framework-fit judgment questions are now standard.

4

Review flow metrics deeply: be ready to explain cycle time, WIP, and throughput relationships on a whiteboard.

5

Have a crisp answer for the 'why does this role still exist' question — it's asked more often than ever.

Practice Scrum Master Interview Questions

Get AI-powered feedback on your answers and ace your next interview.

Start Interview Prep

Related Interview Questions

Project Manager

Ace your project manager interview with 10 curated questions and answers on leadership, Agile, risk management, and stakeholder communication strategies.

Product Manager

Prepare for your product manager interview with 10 questions covering strategy, execution, metrics, and cross-functional leadership with expert answers.

Business Analyst

Prepare for your business analyst interview with 10 expert questions and sample answers on requirements gathering, stakeholder management, and data-driven decisions.