HeroApply
Auto Apply to hundreds of jobs in a few hours
English (US)EspañolItalianoPortuguêsFrançaisDeutsch日本語한국어
Sign up

Scrum Master interview questions and how to answer them

Scrum Master interviews rarely test whether you can recite the Scrum Guide. They test whether you'll hold your ground with a pushy stakeholder, coach a team without bossing it, and tell the difference between Scrum on paper and Scrum that works. Expect scenarios, and bring real stories from teams you've worked with.

11 questions7 minute read

Part 1

1.The product owner keeps adding work in the middle of the sprint. What do you do?

Why they ask

This happens on almost every team, and it tests whether you protect the sprint goal without picking a fight with the person who owns the backlog.

How to answer

  • Talk to the product owner privately first, and find out what's driving the changes
  • Make the trade-off visible: what drops out of the sprint if this comes in
  • Point to the sprint goal as the shared agreement, not your personal rule
  • If it keeps happening, raise it in the retro as a pattern and look at shorter sprints or better refinement

2.Walk us through how you'd run a retrospective for a team that's stopped taking them seriously.

Why they ask

Stale retros are the most common complaint about Scrum. They want to see that you can revive the meeting instead of blaming the team.

How to answer

  • Check whether past action items were ever done, since ignored actions kill retros fast
  • Change the format, such as a timeline, a sailboat board or a focused retro on one problem
  • Limit the outcome to one or two actions with named owners
  • Open the next retro by reviewing what happened to those actions

3.Leadership wants a velocity report to compare teams. How do you respond?

Why they ask

Velocity abuse is a classic trap. The answer shows whether you understand what story points measure and whether you'll push back on a manager.

How to answer

  • Explain that points are relative to each team, so comparing them rewards inflation
  • Ask what leadership actually wants to know, such as predictability or delivery dates
  • Offer better measures, like cycle time, throughput or a burnup chart toward a release
  • Keep the conversation friendly and give them something useful rather than just a no
4.A senior developer dominates every standup and refinement session. What would you do?

Why they ask

They want to see coaching skill with a real person, not a framework answer.

How to answer

  • Talk to the developer one on one and assume good intent, since they often just care a lot
  • Use facilitation tools in the meeting, such as round-robin updates or silent estimation with planning poker
  • Ask quieter team members directly for their view on specific tickets
  • Watch whether the change sticks and follow up
5.How do you know whether a team is actually getting better?

Why they ask

Scrum Masters are hard to evaluate, so hiring managers want to know you judge yourself on something real.

How to answer

  • Name concrete signals, like fewer carried-over stories or more sprint goals met
  • Mention flow measures such as cycle time and how long work sits in review
  • Include softer signals, like the team raising problems before standup instead of after the sprint
  • Give an example from a team you've worked with

Part 2

6.What does a good Definition of Done look like, and who owns it?

Why they ask

It checks Scrum knowledge in a practical way and shows whether you've seen quality problems up close.

How to answer

  • The whole Scrum team agrees on it, and the developers hold themselves to it
  • It covers things like code review, automated tests passing, documentation and deploy to a staging environment
  • It's different from acceptance criteria, which apply to one story
  • It gets stricter over time as the team's practices improve
7.Your team depends on another team that keeps missing its commitments. What do you do?

Why they ask

Cross-team blockers are where Scrum Masters earn their keep, and the answer shows how you work outside your own team.

How to answer

  • Meet that team's Scrum Master or lead to understand their constraints
  • Make the dependency visible on both boards so it isn't forgotten
  • Suggest a regular sync or a shared planning session if the dependency is ongoing
  • Help your product owner re-plan around it rather than letting the team sit idle
8.Which tools have you used to run Scrum, and how did you set them up?

Why they ask

Teams want someone who can own the board without making it a chore.

How to answer

  • Name the tools, such as Jira, Azure DevOps or Trello, plus Miro or Mural for retros
  • Describe a board setup you chose and why, such as a column for code review
  • Mention a report you actually used, like a sprint burndown or a control chart
  • Say what you stripped out to keep the tool light
9.Tell us about a time a sprint failed. What happened next?

Why they ask

They want honesty, and they want to see what you learn from a bad sprint.

How to answer

  • Pick a real failure, such as a missed sprint goal or a release that slipped
  • Explain the cause without blaming one person
  • Describe what the team changed afterward
  • Say what you personally would do differently
10.How would you introduce Scrum to a team that's never used it and doesn't want to?

Why they ask

Many roles involve a team being moved to Scrum by leadership. They want to know you can win people over.

How to answer

  • Start by learning what the team does now and what hurts
  • Introduce practices that solve a pain they already feel, rather than everything at once
  • Be flexible on the details and firm on the few things that matter, like a clear sprint goal
  • Check in after a few sprints and adjust

Part 3

11.Why do you want to be a Scrum Master rather than a project manager or product owner?

Why they ask

They're checking that you understand the role and aren't using it as a stepping stone you'll resent.

How to answer

  • Say what you enjoy about the work, such as helping a team get faster at solving its own problems
  • Show you know the difference in authority between the roles
  • Connect it to something you've done, like running retros for your own team

Questions to ask them

Ask at least two. It shows you're picking them too.

  • How many teams would I support, and do they share a product owner?
  • What does leadership look at to judge whether a team is doing well?
  • What's the last change a retro led to, and did it stick?
  • Who handles release planning and roadmap dates, and how much of that lands on the Scrum Master?
  • Are the teams using Scrum by choice, or was it decided for them?

Related interview guides

Product Owner