Scrum master interview questions: 23 questions and a scorecard for interviewers
The short answer
Good Scrum master interview questions test how a candidate facilitates Scrum events, coaches the team and Product Owner, removes impediments, leads by serving rather than directing, uses metrics to help a team improve, and handles conflict and resistance to change. Ask for real examples, such as a retrospective that changed how a team worked or an impediment they escalated, and listen for what the team did differently afterwards, not only what the Scrum Master did. A recruiter screen should also confirm how long they have worked as a dedicated Scrum Master, the teams and tools they worked with, any certification the client asks for, work arrangement, right to work and start date. Score every candidate against the same five criteria so the decision rests on evidence.
All 23 questions with why you ask each one, what a strong answer shows and follow-ups, plus the scrum master scorecard and rating guide. Free to download and adapt; no sign-up needed.
When to use these questions
A Scrum Master is not a project manager under another name. The Scrum Guide makes the Scrum Master accountable for establishing Scrum and for the Scrum Team’s effectiveness, and describes Scrum Teams as self-managing, deciding internally who does what, when and how, so the job is facilitation, coaching and removing obstacles rather than assigning tasks or owning the plan, which the Developers create for each Sprint. An interview needs to show how someone has helped a real team improve, with evidence of what changed.
For agency recruiters, the screen before the client’s interviews is where to confirm the essentials: how long the candidate has worked as a dedicated Scrum Master rather than alongside another role, how many teams they served at once and what kind of work those teams did, any certification the client asks for, such as Scrum.org’s PSM I or Scrum Alliance’s CSM, and work arrangement, start date and pay expectations. Listen for how they talk about the team: strong candidates describe what the team learned and decided, while weaker ones describe themselves running the meetings.
23 scrum master interview questions
Grouped by what they test. Pick the questions that match the role, ask every candidate the same ones in the same order, and score each answer against the scorecard below.
Facilitating Scrum events
Ask how they run the events with a real team. Good facilitation shows in what the team decided, not in how busy the Scrum Master was.
Question 1: Tell me about a team that kept taking on more in Sprint Planning than it could finish. How did you help them change that?
- Why ask it:
- Tests whether they can improve planning without taking it over.
- A strong answer shows:
- Using the team’s recent history as a guide, focusing planning on a clear Sprint Goal, and helping the Developers own their forecast rather than setting it for them.
Question 2: Your team’s Daily Scrum has turned into a thirty-minute status report to their manager. What do you do?
- Why ask it:
- Shows whether they understand the purpose of the event and can change a habit tactfully.
- A strong answer shows:
- Reconnecting the event to its purpose, the Developers inspecting progress toward the Sprint Goal and adapting their plan, coaching the team to run it, and a private conversation with the manager about other ways to stay informed.
Question 3: Tell me about a retrospective that led to a real change in how the team worked. How did you run it, and how did you make sure the change actually happened?
- Why ask it:
- Tests whether retrospectives produce improvement rather than just conversation.
- A strong answer shows:
- A format suited to the team, a setting where people spoke honestly, a small number of improvements with owners, and follow-up in the next Sprint.
- Follow-up:
- What do you do when retrospectives keep surfacing the same complaints?
Question 4: How do you run a Sprint Review so that stakeholders give useful feedback instead of just watching a demo?
- Why ask it:
- Shows whether they treat the review as a working session.
- A strong answer shows:
- Inviting the right stakeholders, inspecting a working Increment, discussing what to do next with the Product Owner, and adapting the Product Backlog as a result.
Question 5: In a session you are facilitating, one person dominates and others stay quiet. What do you do?
- Why ask it:
- Tests a practical facilitation skill that a recruiter can probe with follow-up questions.
- A strong answer shows:
- Specific techniques such as silent writing, round-robin input, timeboxes and direct invitations, plus a private word with the dominant person if it continues.
Coaching the team and the Product Owner
Look for coaching that builds the team’s independence, not a Scrum Master who becomes the team’s decision maker.
Question 6: How have you helped a team that waited to be told what to do become more self-managing?
- Why ask it:
- Self-management is central to Scrum and hard to build.
- A strong answer shows:
- Gradually handing decisions to the team, asking questions instead of giving answers, making work visible and backing the team’s decisions, with an example of what changed.
Question 7: How do you support a Product Owner whose backlog is unclear or keeps changing?
- Why ask it:
- Tests coaching of the Product Owner without taking over their accountability.
- A strong answer shows:
- Helping them define a Product Goal, refine and split items with the team and involve stakeholders, while the Product Owner keeps the final say on ordering.
Question 8: Tell me about a time you coached someone through a problem instead of solving it for them. What did you do, and how did it turn out?
- Why ask it:
- Shows whether they can hold back and build other people’s capability.
- A strong answer shows:
- Open questions, patience while the person found their own answer, and evidence they handled similar problems alone afterwards.
Question 9: How have you helped a team strengthen its Definition of Done, and what difference did it make?
- Why ask it:
- Tests attention to quality and transparency, not just the events.
- A strong answer shows:
- A shared, explicit quality standard the team improved over time, and fewer surprises such as untested or half-finished work.
Impediments and servant leadership
These questions separate a Scrum Master who serves the team from one who manages it.
Question 10: Tell me about an impediment the team couldn’t remove on its own. What did you do, and how long did it take to resolve?
- Why ask it:
- Tests persistence and influence across the organization.
- A strong answer shows:
- Telling team-level problems from organizational ones, escalating with evidence to the person who could act, following through and keeping the team informed.
- Follow-up:
- Which impediments do you leave for the team to solve, and why?
Question 11: What is the difference between serving a team as a Scrum Master and managing it? Give me an example from your own work.
- Why ask it:
- Directly tests the servant leadership the role depends on.
- A strong answer shows:
- A concrete example of improving the team’s environment or skills without assigning tasks or deciding how the work is done.
Question 12: A senior manager asks you for each developer’s individual productivity figures. How do you respond?
- Why ask it:
- Shows how they protect team trust while respecting a manager’s need for information.
- A strong answer shows:
- Explaining why individual figures distort team-based work, offering team-level outcomes and progress instead, and taking the manager’s underlying concern seriously.
Question 13: Work keeps arriving mid-Sprint from people who bypass the Product Owner. What do you do?
- Why ask it:
- Tests whether they protect the team’s focus through the right channels.
- A strong answer shows:
- Redirecting requests to the Product Owner, making interruptions visible to stakeholders, and handling genuine emergencies openly rather than quietly absorbing them.
Metrics, scaling, conflict and change
Ask how they use data, work across teams and handle the people side of change.
Question 14: Which measures have you used to help a team improve, and when have you seen a metric such as velocity do more harm than good?
- Why ask it:
- Tests whether they use metrics for learning rather than control.
- A strong answer shows:
- Measures such as Sprint Goal success, cycle time and escaped defects used for the team’s own learning, and an example of velocity misused as a target or to compare teams.
Question 15: Have you worked with several teams building one product? How did they coordinate and bring their work together each Sprint?
- Why ask it:
- Checks experience of scaling beyond a single team.
- A strong answer shows:
- Shared product ownership and backlog, cross-team refinement and integration every Sprint, and any scaling framework named only alongside what they actually did with it.
Question 16: Two people on your team have an ongoing conflict that is affecting everyone else. What do you do?
- Why ask it:
- Tests conflict handling, which has a large effect on team effectiveness.
- A strong answer shows:
- Talking to each person privately, facilitating a conversation focused on behavior and team agreements, and involving their line manager only if it doesn’t improve.
Question 17: Tell me about a team or department that resisted moving to agile ways of working. What did you do, and what changed?
- Why ask it:
- Shows how they handle resistance without preaching.
- A strong answer shows:
- Understanding the reasons for the resistance, starting small, showing results, and involving skeptics in shaping the change.
Must-haves and logistics
Ask these of every candidate before the client’s interviews, and check the answers against the resume.
Question 18: How long have you worked as a dedicated Scrum Master rather than alongside another role, how many teams did you serve at once, and what kind of work did they do?
- Why ask it:
- Confirms relevant, recent experience at the load the client expects.
- A strong answer shows:
- Clear dates, the number of teams, and the type of work, such as software, data or business teams, with team sizes.
Question 19: Which agile frameworks and tools have you used day to day, such as Scrum, Kanban, Jira or Azure Boards?
- Why ask it:
- Checks fit with the client’s ways of working and tools.
- A strong answer shows:
- Specific practices and tools tied to recent teams, and how they used them to make work visible.
Question 20: Do you hold a Scrum certification the client has asked for, such as Scrum.org’s Professional Scrum Master I (PSM I) or Scrum Alliance’s Certified ScrumMaster (CSM)?
- Why ask it:
- Some clients list one of these certifications as a requirement.
- A strong answer shows:
- The exact certification and when it was earned, with details you can check in the issuer’s online search.
Question 21: The role is [number of teams, remote, hybrid or on-site, location and the time zones the teams work in]. Does that work, and when could you start?
- Why ask it:
- Rules out arrangement and time zone mismatches early.
- A strong answer shows:
- A clear yes, or the specific constraint, and a firm start date or notice period.
Question 22: Are you legally authorized to work in [country] for this employer, and will you need visa sponsorship now or in the future?
- Why ask it:
- Confirms eligibility; ask every candidate the same question in the same way.
- A strong answer shows:
- A direct answer, recorded the same way for every candidate.
Question 23: What pay range are you looking for in this role?
- Why ask it:
- Checks fit with the client’s budget without asking about pay history.
- A strong answer shows:
- A realistic range you can compare with the client’s budget.
Scrum master interview scorecard
Five criteria for this role, with what a score of 1, 3 and 5 looks like. Scores of 2 and 4 sit between them.
| Criterion | What it means | Score 1 looks like | Score 3 looks like | Score 5 looks like |
|---|---|---|---|---|
| Facilitation | Runs Scrum events and team sessions that lead to decisions and improvements. | Describes events as meetings they run, with no example of an outcome. | Runs events with a clear purpose and gives an example of a useful retrospective. | Adapts facilitation to the team, draws out quiet voices and turns events into lasting change. |
| Coaching and team development | Builds the capability and self-management of the team and the Product Owner. | Solves problems for the team or makes its decisions. | Gives an example of coaching someone to solve a problem themselves. | Shows a team that became more self-managing over time and a Product Owner who grew in the role. |
| Impediment removal and influence | Removes obstacles, including organizational ones, by working through the right people. | Waits for others to fix impediments, or only logs them. | Escalates impediments with evidence and follows through. | Changes organizational practices that slowed teams down and builds the relationships to do it. |
| Servant leadership | Leads by serving the team rather than directing it. | Assigns tasks, chases individuals or reports on them to managers. | Explains the difference between serving and managing with a real example. | Protects the team’s focus and trust while keeping managers and stakeholders informed and on side. |
| Empiricism and use of metrics | Uses evidence to help the team inspect and adapt. | Treats velocity as a target, or uses metrics to compare people or teams. | Uses a few sensible measures for the team’s own learning. | Helps the team and stakeholders decide from evidence, and spots when a metric is distorting behavior. |
The 1–5 rating scale
The same scale for every criterion and every candidate.
| Score | Level | What it means |
|---|---|---|
| 1 | Well below requirement | No relevant evidence, or an answer that contradicts the requirement. |
| 2 | Below requirement | Partial evidence with important gaps. |
| 3 | Meets requirement | Clear, relevant evidence at the level the role needs. |
| 4 | Above requirement | Strong, specific evidence beyond the expected level. |
| 5 | Exceptional | Repeated high-quality evidence with clear impact. |
How to run the interview with these scrum master interview questions
- 01
Step 01
Agree the must-haves first
Confirm the essential credentials, experience and availability with the hiring manager or client before any interviews. - 02
Step 02
Pick 8 to 12 questions
Take the must-have questions, then the questions that test what this role needs most. Use the same set, in the same order, for every candidate. - 03
Step 03
Ask for real examples
When you hear “we” or “I would”, ask what the candidate personally did, and what happened in the end. - 04
Step 04
Score before you discuss
Rate each criterion on the scorecard with the evidence behind it, then compare with other interviewers. - 05
Step 05
Verify before you submit
Check licenses, certifications and right to work against the original source before you put the candidate forward.
Red flags, and questions not to ask
- Describes assigning tasks to developers, running the Daily Scrum as a status meeting for a manager, or reporting on individuals’ performance.
- Can list Scrum’s events and artifacts but has no example of a team improving because of their work.
- Treats velocity as a target, or uses it to compare teams or people.
- Makes backlog ordering decisions that belong to the Product Owner.
- Blames the team, the Product Owner or management for every failed adoption, with no reflection on their own part.
- Age, marital or family status, pregnancy or plans for children, religion, ethnicity or national origin, sexual orientation or gender identity. These are protected characteristics under the UK Equality Act 2010 and US federal law, and they say nothing about whether someone can do the job.
- Health, sickness absence or disability before an offer. You can ask whether the candidate needs any adjustments for the interview, and whether they can do the essential tasks of the job.
Screen scrum master applicants before the first call
Add these questions to a Beatview AI interview and every applicant answers them on video or audio, with the same time limit. Beatview scores each answer against your criteria and shows the reasoning, and you can share the shortlist with your client through a password-protected link. AI interviews are on the Pro plan; the Free plan screens resumes for one active job.
Scrum master interview questions: frequently asked questions
Still deciding?
Bring a live vacancy and we’ll walk through where automation ends and recruiter review begins.
Ask for real examples that test facilitation, coaching the team and Product Owner, removing impediments, servant leadership, use of metrics, and handling conflict and resistance to change, such as a retrospective that changed how a team worked or a manager who asked for individual productivity figures. Add must-have questions on dedicated Scrum Master experience, the teams and tools they worked with, any certification the client asks for, work arrangement, right to work and start date, and ask every candidate the same questions in the same order.
Scrum.org’s Professional Scrum Master I (PSM I) and Scrum Alliance’s Certified ScrumMaster (CSM) are earned differently. PSM I is a test that doesn’t require a course and is a lifetime certification; CSM requires completing a course taught by a Certified Scrum Trainer before the test, and is renewed every two years with Scrum Education Units. Check PSM holders in Scrum.org’s certification holder search and CSM holders in Scrum Alliance’s member search, which lists active members only. Neither certification shows how well someone serves a real team, so weigh it below the examples they give in the interview.
Agree it with the client in advance and keep it close to the job, such as facilitating a short retrospective with two or three interviewers playing team members, or talking through a written scenario about a struggling team. Give every candidate the same brief, timing and scoring guide, tell them the format beforehand, and score how they listen, ask questions and help the group reach its own decisions rather than how polished they sound. Make adjustments if a candidate asks for them.
A project manager usually owns the plan, schedule, budget and scope and directs the work needed to deliver them. In Scrum, the Developers create the plan for each Sprint and the Product Owner orders the Product Backlog, while the Scrum Master is accountable for establishing Scrum and for the Scrum Team’s effectiveness, through coaching, facilitation and removing impediments. Screen for that difference: a candidate who mainly describes assigning tasks and chasing deadlines may be a strong project manager but is unlikely to suit a Scrum Master role.
Get the scrum master interview questions template
All 23 questions with why you ask each one, what a strong answer shows and follow-ups, plus the scrum master scorecard and rating guide.
Opens in Excel, Google Sheets or Numbers. Version 2 October 2026.
Sources: The Scrum Guide (2020); Scrum.org: Professional Scrum Master I (PSM I) certification; Scrum.org: Certification holder search; Scrum Alliance: Certified ScrumMaster (CSM); Scrum Alliance: How to verify a member’s certification. This template is general guidance, not legal advice.