Scrum Master Interview Questions: 30 Questions and 5 Sample Answers (2026)

Scrum master interview questions test three things: whether you know the Scrum framework as the Scrum Guide defines it, whether you can coach a team and its stakeholders without ordering anyone around, and whether you can handle the messy situations no guide covers. The three questions you are most likely to get are "What does a Scrum Master actually do?", "How do you run a retrospective that leads to change?" and "What would you do if the Product Owner keeps adding work mid-Sprint?"

This guide gives you 30 questions grouped by skill, one line on what a strong answer shows for each, five full sample answers we wrote, and the Scrum Guide facts interviewers check, verified on scrumguides.org as of October 2026.

How a Scrum Master interview usually runs

Stages vary by employer, so treat this as a common shape rather than a rule:

1. Recruiter screen (20–30 minutes). Your background, why Scrum Master, certification if the posting asks for one, and logistics.
2. Hiring manager interview. Often an agile coach, delivery lead or engineering manager. Expect framework questions and "tell me about a team you coached."
3. Scenario or panel round. A Product Owner, a developer and sometimes a stakeholder each bring a situation: a broken Daily Scrum, a team that misses every Sprint Goal, a manager who wants velocity reports.
4. Facilitation exercise (some employers). You run a short mock retrospective or Sprint Planning with the panel playing the team.
5. Final conversation. Values, how you handle conflict, and your questions for them.

Some companies fold these into two rounds; larger ones may add a separate culture or values interview. Ask the recruiter what each round covers. Most of it is behavioral, so a working knowledge of the STAR method pays off.

Scrum Guide facts interviewers check (as of October 2026)

The current Scrum Guide is the November 2020 version. Interviewers often test whether you know it precisely, especially the parts that changed from 2017. Get these right:

The 2017-to-2020 revision notes also list what changed: the Product Goal was added, each artifact got a commitment, "self-organizing" became "self-managing", Sprint Planning gained a "why" topic, and prescriptive items such as the three Daily Scrum questions were removed. If an interviewer asks "What are the three Daily Scrum questions?", the precise answer is that the 2020 guide no longer prescribes them; the Developers choose any structure that inspects progress toward the Sprint Goal.

30 Scrum Master interview questions, grouped by skill

Framework knowledge

• What is the role of a Scrum Master? A strong answer shows you serve the team, the Product Owner and the organization, and that you measure yourself by the team's effectiveness, not by meetings run.
• What are the Scrum events and why does each exist? Shows you know each event is an inspect-and-adapt point, not a ritual.
• What is the difference between the Sprint Goal and the Sprint Backlog? Shows you see the goal as the commitment and the backlog as the plan that can change.
• Who owns the Product Backlog? Shows you know the Product Owner is accountable, even when others help refine it.
• What is a Definition of Done, and who creates it? Shows you treat Done as a quality bar that makes the Increment usable, and know the Scrum Team creates it if the organization has no standard.
• Can a Sprint be cancelled? By whom? Shows precision: only the Product Owner, when the Sprint Goal becomes obsolete.
• What changed in the 2020 Scrum Guide? Shows you keep current: Product Goal, commitments, self-managing, one team.
• How is Scrum different from Kanban? Shows you can compare fixed-length Sprints with continuous flow and WIP limits without dismissing either.

Facilitation and coaching

• How do you run a retrospective that leads to real change? Shows you pick one or two improvements, give them owners, and check them at the next retro.
• The Daily Scrum has turned into a status report to you. What do you do? Shows you step back so the Developers own it and talk to each other about the Sprint Goal.
• How do you help a new Product Owner write a good Product Backlog? Shows coaching on outcomes, ordering and refinement, not writing the backlog for them.
• How do you facilitate Sprint Planning for a team that always overcommits? Shows you use past performance, capacity and a clear Sprint Goal rather than pressure.
• How do you coach a team toward self-management? Shows you deliberately hand over decisions and accept some short-term mess.
• What metrics do you use, and which do you avoid? Shows you use flow and outcome signals for the team's own learning and refuse to turn velocity into a cross-team scorecard.

Removing impediments and working with the organization

• Tell me about an impediment you removed that was outside the team. Shows you can work across departments, not only inside the team room.
• A manager asks you for each developer's individual velocity. How do you respond? Shows you redirect to team-level outcomes and explain why individual numbers distort behavior.
• How do you handle a stakeholder who goes straight to developers with requests? Shows you route work through the Product Owner while keeping the stakeholder on side.
• How would you introduce Scrum to a team that has never used it? Shows you start from the team's problems, teach the minimum, and adapt.
• How do you coordinate several Scrum Teams working on one product? Shows you keep one Product Backlog and one Product Owner, and add only the coordination that the teams need.
• Leadership wants Scrum but keeps fixed scope and fixed dates. What do you do? Shows you make the trade-offs visible and negotiate, rather than pretending all three can be fixed.

Behavioral

• Tell me about a conflict inside a team you supported. Shows you facilitate the conflict between the people involved instead of deciding for them. See our conflict answer guide.
• Describe a time a team failed to meet its Sprint Goal. Shows you treat it as learning, not blame. Our failure answer guide covers the structure.
• Tell me about a time you disagreed with a Product Owner. Shows respect for their accountability while still raising the risk.
• Describe a change you led that people resisted. Shows patience, evidence and small experiments.
• What is the hardest feedback you have given a team member? Shows you can be direct and kind at once.
• Why do you want to be a Scrum Master rather than a project manager? Shows you understand the difference between serving a self-managing team and directing a plan.

Situational

• The Product Owner adds work mid-Sprint. What do you do? Shows you check it against the Sprint Goal and help the PO and Developers negotiate scope.
• A senior developer dominates every discussion. How do you handle it? Shows facilitation techniques such as silent writing first, rounds, and a private conversation.
• The team says retrospectives are pointless. What now? Shows you change the format, shrink the scope and prove one improvement lands.
• A critical bug appears in production in the middle of a Sprint. What happens? Shows you let the Product Owner and Developers decide how it affects the Sprint Goal, and make the trade-off visible.

Five sample answers (examples we wrote)

Use these as models for structure and length, not scripts. Swap in your own teams, numbers and outcomes.

"What does a Scrum Master actually do?"

Example (experienced Scrum Master): "I am accountable for the Scrum Team's effectiveness. Day to day that means three things. For the Developers, I coach self-management and make sure our events produce decisions, not just meetings. For the Product Owner, I help with backlog techniques and keeping the Product Goal clear. For the wider organization, I remove impediments the team can't remove itself. At my last company, the biggest one was a release approval that took a week; I worked with the change board to approve low-risk changes in a day. I judge my work by whether the team needs me less over time."

"How do you run a retrospective that leads to change?"

Example: "I start by reviewing last retro's action, so the team sees retros produce results. Then I vary the format so it doesn't go stale, and I use silent writing first so quieter people contribute. We dot-vote, pick one improvement, and phrase it as an experiment with an owner and a date, for example 'For the next Sprint, we pair on every story touching the payments module.' In one team I supported, we had six open retro actions and none done. We cut to one per Sprint, and the team actually closed them."

"The Product Owner keeps adding work mid-Sprint. What do you do?"

Example: "First I'd find out why. Often it's stakeholder pressure the PO can't push back on. In the moment, I'd ask whether the new item supports the Sprint Goal. If it does, the PO and Developers can renegotiate scope, because the Sprint Backlog can change while the goal stays. If it doesn't, I'd help the PO see the cost and either hold it for the next Sprint or, if the goal is truly obsolete, consider cancelling, which is the PO's call. Afterwards I'd coach the PO on shorter feedback loops with stakeholders so urgent asks surface in refinement."

"A manager wants each developer's velocity. How do you respond?"

Example: "I'd ask what problem they are trying to solve. Usually it's predictability or a performance concern. I'd explain that velocity is a planning aid for the team, and individual velocity pushes people to inflate estimates and avoid helping each other. Then I'd offer what answers the real question: the Sprint Goal hit rate, cycle time trends, and the Sprint Review where they can see the actual Increment. If there's a performance concern about one person, that belongs with their line manager, not in Scrum data."

"Tell me about a team that wasn't improving."

Example (Situation, Task, Action, Result): "A team I joined had missed its Sprint Goal for five Sprints in a row. My task was to find out why without blaming anyone. I looked at the data and found most stories were too big to finish in a Sprint. I ran a refinement workshop on splitting stories by workflow step, and we agreed nothing entered a Sprint unless the Developers thought it could be done in three days. Over the next four Sprints the team met its goal three times, and refinement became something they ran without me."

What interviewers are listening for

Mistakes that cost Scrum Master candidates

• Describing yourself as the team's manager. "I assign tasks" is a red flag. Developers decide how to do the work.
• Using pre-2020 terms as current. Saying "the Development Team" or listing the three Daily Scrum questions as required suggests you haven't read the current guide.
• Answering every scenario with "I'd escalate." Interviewers want to hear what you would try first.
• All theory, no stories. Every framework answer gets stronger with one sentence of "on my last team, we…".
• Treating certification as proof of skill. Mention it if you have it, then move straight to what you did with a team.

Questions to ask the interviewer

• "How many teams would I support, and does each have a dedicated Product Owner?"
• "What is the biggest impediment your teams face that they can't fix themselves?"
• "How does leadership use Sprint data today, and what would you like to change?"
• "What would make you say this hire was a success after six months?"

For more ideas by round, see our list of questions to ask the interviewer.

How to practice for a Scrum Master interview

Scenario answers fall apart when you first say them out loud. Practice by speaking:

1. Pick five questions above, one from each group, and answer each in under two minutes.
2. Write three STAR stories (a team you coached, a conflict, a change people resisted) and reuse them across questions.
3. Reread the Scrum Guide once; it is short, and precision is easy points.
4. Run a mock. In CoPilot Interview's Mock Interview you add your résumé and the job description, pick 3, 5 or 8 questions and the behavioral mix; it reads each question aloud, scores your spoken answer out of 10 with what to fix and a model answer, and gives a report card at the end. The free plan includes 15 minutes a day. If you'd rather not install anything, the browser mock at /ai-mock-interview has a behavioral track.

If the role sits close to delivery management, our project manager interview questions and teamwork interview questions guides cover the overlap.

FAQ

What are the most common Scrum Master interview questions?

Expect "What does a Scrum Master do?", "How do you run a retrospective that leads to change?", "What would you do if the Product Owner adds work mid-Sprint?", "How do you handle a manager who wants individual velocity?" and a behavioral question about a team you coached.

Which version of the Scrum Guide should I study?

The November 2020 Scrum Guide, which is the current version on scrumguides.org as of October 2026. It introduced the Product Goal, a commitment for each artifact and the term self-managing.

What are the three Daily Scrum questions?

The 2020 Scrum Guide no longer prescribes them. The Daily Scrum is a 15-minute event for the Developers, who can use any structure that inspects progress toward the Sprint Goal.

Do I need a certification to get a Scrum Master job?

It depends on the employer. Some postings require one and many list it as preferred. Mention yours if you have it, but interviewers decide mostly on how you handle scenarios and what you did with real teams.

How should I answer scenario questions in a Scrum Master interview?

Say what you would try first, tie it to a Scrum principle such as the Sprint Goal or Product Owner accountability, explain how you would involve the team, and say how you would know it worked.

How long should my answers be?

Aim for one to two minutes. Framework questions can be shorter; behavioral stories need enough detail for a clear situation, action and measurable result.