Scrum Master Interview Questions and Answers

What Scrum Master interviewers assess

This is the real work sitting behind the questions. They are checking whether you have actually done it, not whether you can describe it.

• Scrum and Agile fundamentals: The Scrum Guide, roles, events, artifacts, and where mechanical Scrum stops and an actual Agile mindset starts.
• Team coaching and facilitation: Running ceremonies people do not dread, naming the dysfunction in the room, and coaching a team toward self-management.
• Impediment removal: Spotting the organisational blockers, escalating with data, and unblocking the team without becoming their assistant.
• Metrics and predictability: Velocity, throughput, cycle time, predictability, and never letting a metric get turned into a weapon against your team.
• Scaling Agile: Working across multiple teams, frameworks like SAFe or LeSS, and the practical patterns for cross-team coordination.
• Continuous improvement: Retrospectives that actually change something, small experiments, and a team that owns its own improvement.

Common Scrum Master interview questions with answer guidance

1. How do you describe the role of a scrum master in your own words?

Servant leader for the team, coach for the product owner, change agent for the organisation. You protect the team, surface impediments, and grow self-management. Do not recite the Scrum Guide. Bring your own framing, tied to a real team you served, and keep it under 60 seconds.

2. A sprint is going off the rails halfway through. What do you do?

Diagnose it with the team: capacity, a dependency, an unclear story, or scope creep. Then decide whether to re-plan, cut scope, or push through with your eyes open. Tell the product owner the truth early. Resist the hero-rescue reflex. Treat the moment as a coaching opportunity, not just a recovery job.

3. How do you handle a team that does not want to do retrospectives?

Find the root cause first: too long, no follow-through, blame culture, calendar fatigue. Shorten it and change the format. Make actions visible and follow up on them. Bring a story where a retro changed a real outcome. Do not moralise about Agile. Make retros worth attending and the attendance sorts itself out.

4. How do you measure team health?

Use a mix of leading indicators: predictability, cycle time, defect escape rate, plus qualitative reads like a Squad Health Check or the mood in your 1:1s. Say out loud that no single metric tells the truth. Treat metrics as conversation starters, not management tools, and steer clear of the velocity-as-productivity fallacy.

5. Velocity has been flat for three sprints. What do you investigate?

Look at scope clarity, story sizing, dependency wait time, and changes in team composition. Separate flat-and-fine from flat-and-stuck. Take the data into retro and let the team own the fix. Do not run to leadership with raw numbers. Velocity is a team artifact, not a performance metric, and you should say so.

6. Tell me about a team you coached from low to high performance.

Pick a real team. Describe the starting state honestly: symptoms, metrics, morale. Walk through what you changed, from ceremony design to working agreements, dependency negotiation and coaching individuals. Put a number on the outcome. Own the dead ends. Interviewers are listening for substance, not Agile vocabulary.

7. How do you work with a difficult product owner?

Build the relationship before you try to fix anything. Coach with empathy on backlog refinement, prioritisation and stakeholder management. Bring data on what mid-sprint changes cost. Involve their manager only after coaching has genuinely failed. Never correct them in public. The PO is your partner, not your opponent.

8. A manager wants to use velocity to compare teams. What do you say?

Push back firmly and give your reasoning: velocity is a team-relative planning tool, not a productivity metric. Offer better cross-team measures instead, like predictability, customer outcomes and cycle time. Bring a story where that comparison caused bad behaviour. Do not preach. Protect the team without becoming an obstacle.

9. How do you scale Agile across multiple teams?

Start with the problem, not the framework. Try lightweight patterns first, like communities of practice or scrum of scrums, before you adopt SAFe or LeSS wholesale. Match cadence and interfaces between teams. Say the quiet part out loud: scaling frameworks cost something. Pragmatism beats dogma here.

10. How do you remove an impediment that requires leadership action?

Escalate with data and a proposed solution, never a complaint. Translate the cost into delivery terms they care about. Track impediments where everyone can see them and follow up. Say that escalation is a tool, not your default. You build credibility first so leadership trusts the ask when it comes.

11. How do you avoid becoming the team secretary?

Refuse to own the board, the notes and the meeting bookings by default. Coach the team to self-manage and time-box your own facilitation. Name specific habits: a rotating retro facilitator, working agreements the team wrote themselves. Your goal is that the team needs you less over time, not more.

12. Why scrum master rather than project manager or engineering manager?

Talk about why you like coaching, how much changes when a team’s behaviour shifts, and the pleasure of a healthy team shipping predictably. Admit the overlap with the other roles. Tie it to one team where this work clicked. Do not frame it as the softer option. Show conviction in the craft.

How to prepare

Say each answer out loud, keep it short, and swap in an example from the job you are actually chasing.

• Have one team transformation story ready, with metrics and the dead ends you hit.
• Know how you will defend your stance on velocity comparisons before someone pushes.
• Practise designing a quick retro out loud: format, time-box, follow-through.
• Ask how the company supports scrum masters and Agile coaching at scale.
• Run a Voxxhire mock interview out loud. Coaching language sounds very different in your mouth than in your head.