Interview questionsUpdated 12 Oct 2026 · Team InterviewPlan

Scrum Master Interview Questions and Answers

Scrum master interviews test whether you understand Scrum deeply enough to coach it, not just run meetings. Panels want servant leadership, facilitation skill and practical ways to remove impediments. These questions are what Scrum master candidates face in 2026 at enterprises, services firms and product teams.

What interviewers test in a scrum master interview

Interviewers check three layers: knowledge of the Scrum Guide, facilitation and coaching skill, and your ability to influence an organisation that may not be fully Agile. Many questions are scenarios, such as a product owner who keeps adding work mid-sprint or a team that skips retrospectives.

A common trap is answering like a project manager who assigns work. Show that you help the team self-manage and that you measure success by team outcomes, not by your own control.

  • Scrum theory: empiricism, pillars, values and accountabilities
  • Events: sprint planning, daily scrum, review, retrospective and the sprint itself
  • Artifacts and commitments: product goal, sprint goal and definition of done
  • Coaching: conflict, psychological safety and team maturity
  • Organisation: stakeholder education and scaling frameworks

Topics and tools to revise

Re-read the current Scrum Guide before the interview. Many candidates still describe outdated ideas such as the development team or mandatory three questions at the daily scrum.

  • The 2020 Scrum Guide changes: developers, product goal, self-managing teams
  • Velocity, burndown and burn-up charts and why velocity is not a productivity target
  • Flow metrics: cycle time, throughput and work item age from Kanban
  • Retrospective formats: Start Stop Continue, 4Ls, sailboat and timeline
  • Jira boards, sprint reports and dashboards
  • SAFe basics: ART, PI planning, RTE and system demo
  • Estimation techniques: planning poker and relative sizing

How to structure your answers

Use STAR, and in the action part show coaching rather than commanding: the questions you asked, the experiment you proposed, how the team decided. In the result, use a team metric such as predictability, cycle time or carry-over work.

When asked a theory question, give the Scrum Guide view first, then add how you apply it in practice. This shows both accuracy and real experience.

How InterviewPlan AI helps you prepare

The Behavioral Coach is built for scrum master preparation: it helps you shape stories about conflict, resistance to change and coaching moments, and checks they follow STAR. Mock interviews add scenario questions and feedback on whether you sound like a coach or a manager.

Interview Copilot supports live interviews on Zoom, Teams, Meet and Webex with speaker-labelled transcription and STAR drafts from your resume. Scrum Master Job Support then helps you in your first 90 days with ceremonies and team challenges. Copilot and Job Support are $5 per hour, taxes included.

Questions and model answers

9 questions you are likely to hear.

  1. What is the difference between a scrum master and a project manager?

    Why they ask: This tests whether you understand servant leadership and self-management.

    Sample answer: A project manager typically plans the work, assigns tasks and is accountable for scope, schedule and budget. A scrum master is accountable for the team's effectiveness: helping the team use Scrum well, removing impediments and coaching the organisation, while the developers decide how to do the work and the product owner decides what to build. In my last role, when I moved from PM to scrum master, the hardest change was to stop assigning tickets in stand-ups. Within two sprints the team was pulling work themselves, and sprint goal completion actually improved.

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

    Why they ask: This scenario checks how you protect the sprint goal while respecting the product owner's role.

    Sample answer: I would first understand why, privately and without blame: is it pressure from stakeholders, unclear priorities or a weak backlog? Then I would coach the PO on the sprint goal as a commitment and on the option of negotiating scope with the developers, or cancelling the sprint in a true emergency. With one PO, I helped set up a visible expedite lane limited to one item per sprint and a better refinement routine. Mid-sprint additions dropped from four or five per sprint to roughly one, and stakeholders learned to bring requests to refinement.

  3. How do you run an effective retrospective?

    Why they ask: Retrospectives are where continuous improvement lives, so interviewers want depth here.

    Sample answer: I set the stage with a quick check-in so everyone speaks early, then gather data, generate insights, decide on actions and close. I vary formats every few sprints, such as sailboat or a timeline of the sprint, to avoid fatigue. The most important part is limiting the outcome to one or two concrete, owned actions and reviewing them at the start of the next retro. In one team, actions were never followed up, so I started adding them to the sprint backlog. The team saw changes actually happen, and attendance and honesty in retros improved noticeably.

  4. How do you use velocity, and what are its limitations?

    Why they ask: Interviewers check that you will not misuse velocity as a performance target.

    Sample answer: I use velocity only as a planning aid for that team, averaging the last three to five sprints to forecast what fits in a sprint or a release. Its limitations are that story points are relative and team-specific, so comparing teams is meaningless, and once managers treat it as a target, teams inflate estimates. When a director wanted to rank teams by velocity, I showed how points had drifted upward without any change in delivered value, and proposed tracking cycle time and sprint goal success instead. That shifted the conversation to outcomes.

  5. One senior developer dominates discussions and others stay silent. How do you handle it?

    Why they ask: This tests facilitation and conflict management skills.

    Sample answer: I would speak with the senior developer privately first, recognising their expertise and asking for help in growing others, which often works better than criticism. In meetings I use techniques that balance voices: silent brainstorming on sticky notes before discussion, round-robin input and planning poker where everyone reveals at once. With one team, a tech lead was unintentionally anchoring every estimate. After we switched to simultaneous reveals and I asked him to speak last, junior developers began raising risks he had missed, and estimate accuracy improved over the next few sprints.

  6. What is the purpose of the daily scrum, and what do you do if it turns into a status meeting?

    Why they ask: This checks Scrum Guide knowledge and practical coaching.

    Sample answer: The daily scrum is a 15-minute event for the developers to inspect progress toward the sprint goal and adapt their plan for the next day. It is not a status report to the scrum master or a manager. If it becomes a status meeting, I stop standing at the front, ask the team to talk to each other and walk the board from right to left so the focus is on finishing work. I also move detailed problem solving to an after-party with only the people needed. In one team this cut the meeting from 30 minutes to about 12.

  7. How do you handle an impediment that is outside the team's control?

    Why they ask: Interviewers want to see how you work across the organisation.

    Sample answer: I make the impediment visible on the board, quantify its impact and take it to whoever can actually resolve it. In one project, test environments were shared with three other teams and were down for an average of a day per sprint. I tracked the hours lost over two sprints, brought the data to the infrastructure manager and suggested a booking system plus one dedicated environment. The manager approved it once he saw the numbers. Environment-related carry-over work dropped close to zero, and I shared the fix with the other scrum masters.

  8. How do you introduce Scrum to a team that is resistant to it?

    Why they ask: This tests change management and empathy.

    Sample answer: I start by understanding the resistance, which is usually based on bad past experience such as too many meetings or being micromanaged with story points. I avoid a big-bang rollout. Instead I agree a small experiment with the team, for example two-week sprints with only planning, review and a short retro, and we evaluate it together after three sprints. With a support team at a services company, we started with a Kanban board and WIP limits instead of full Scrum, because their work was interrupt-driven. They adopted retrospectives voluntarily once they saw cycle time improve.

  9. How does PI planning work in SAFe, and what is the scrum master's role?

    Why they ask: Many enterprise roles in 2026 use SAFe, so interviewers check scaled Agile exposure.

    Sample answer: PI planning is a two-day event where all teams in an Agile Release Train plan the next program increment, usually 8 to 12 weeks. Business context and vision are presented first, then teams draft plans, identify dependencies on the program board, and commit to PI objectives after a management review. As scrum master, I help my team prepare a refined backlog and capacity numbers beforehand, facilitate the breakout sessions, make dependencies and risks visible, and run the confidence vote honestly. After the event I track dependencies with the release train engineer in the scrum of scrums.

FAQ

Questions people ask about scrum master.

Which certification is best for scrum master interviews?

PSM I from Scrum.org and CSM from Scrum Alliance are the most recognised. For enterprise roles, SAFe Scrum Master is often listed. Certifications help screening, but interviewers mainly test how you coach real teams through real problems.

Do scrum masters need technical knowledge?

Not deep coding skills, but understanding CI/CD, testing, technical debt and how developers work makes you far more effective and credible. Many interviewers ask how you would handle technical debt or a failing build pipeline.

What metrics should a scrum master track?

Sprint goal success, predictability, cycle time, throughput, escaped defects and team health signals from retrospectives. Avoid presenting velocity as a productivity metric. Interviewers respond well when you explain which metric you chose and why.

How can I practise scrum master scenario questions?

Use mock interviews that ask scenarios such as mid-sprint scope changes or a silent team, and answer out loud with STAR. InterviewPlan AI's Behavioral Coach and mock interviews use AI credits, and the free plan includes 100 credits.

P.S.

Reading helps. Practising out loud helps more.

Start free with 5 live minutes and 100 AI credits for Resume AI, Job Search, Auto-Apply, mock interviews and Behavioral Coach.