The short answer: Scrum Master interviews test whether you know Scrum precisely and can apply it with judgment. Expect fundamentals from the Scrum Guide (accountabilities, events, artifacts, values), questions about the Scrum Master’s role as a coach rather than a project manager, and above all scenarios: a team that keeps missing its Sprint Goal, a stakeholder who changes priorities mid-Sprint, a Daily Scrum that has turned into a status meeting, a manager who wants to compare velocity across teams. Answer scenarios by understanding the cause first, coaching the team toward its own solution, and protecting empiricism, with real examples from teams you’ve served.
Sample answers are illustrations, not quotes from real candidates. Facts about Scrum below come from the November 2020 Scrum Guide.
Scrum fundamentals
“What is Scrum?”
A lightweight framework for solving complex problems through iterative, incremental delivery, based on empiricism (decisions based on what is observed) and lean thinking. Its three pillars are transparency, inspection and adaptation.
“What are the accountabilities in a Scrum Team?”
The Scrum Guide says a Scrum Team “consists of one Scrum Master, one Product Owner, and Developers,” with no sub-teams or hierarchies, typically 10 or fewer people. Teams are cross-functional (they have all the skills to create value each Sprint) and self-managing (they decide who does what, when and how).
“What are the Scrum events and their timeboxes?”
| Event | Purpose | Timebox (for a one-month Sprint) |
|---|---|---|
| Sprint | Container for all other events; turns ideas into value | One month or less, fixed length |
| Sprint Planning | Decide why (Sprint Goal), what and how | Up to 8 hours |
| Daily Scrum | Developers inspect progress toward the Sprint Goal and adapt the plan | 15 minutes |
| Sprint Review | Inspect the outcome with stakeholders and adapt the Product Backlog | Up to 4 hours |
| Sprint Retrospective | Plan ways to increase quality and effectiveness | Up to 3 hours |
For shorter Sprints, the events are usually shorter.
“What are the Scrum artifacts and their commitments?”
- Product Backlog, committed to the Product Goal.
- Sprint Backlog, committed to the Sprint Goal.
- Increment, committed to the Definition of Done.
“What are the Scrum values?”
Commitment, focus, openness, respect and courage. Give an example of one in practice, such as courage to raise an impediment in front of senior stakeholders.
“Are story points, burn-down charts and user stories part of Scrum?”
No. They’re common practices teams may choose, but the Scrum Guide doesn’t require them. This question checks that you know the framework from the practices built around it.
The Scrum Master’s role
“What does a Scrum Master do?”
The Scrum Guide describes Scrum Masters as “true leaders who serve the Scrum Team and the larger organization.” They’re accountable for the team’s effectiveness by:
- Serving the team: coaching self-management and cross-functionality, helping the team focus on high-value Increments that meet the Definition of Done, causing the removal of impediments, and making sure events happen and are positive, productive and kept within the timebox.
- Serving the Product Owner: helping with Product Goal definition and backlog management techniques, and facilitating stakeholder collaboration.
- Serving the organization: leading, training and coaching Scrum adoption and removing barriers between stakeholders and teams.
“How is a Scrum Master different from a project manager?”
“A project manager typically plans and assigns work and is accountable for delivering scope, time and budget. A Scrum Master doesn’t assign work or own delivery: the Developers plan their own work, the Product Owner owns the backlog and value, and I’m accountable for how effectively the team uses Scrum and improves. I coach, facilitate and remove impediments, and I often work on the system around the team, such as dependencies or approval processes that slow it down.”
Scenario questions
1. “The team keeps missing its Sprint Goal.”
“First I’d look at the pattern with the team in a retrospective rather than guess: are goals too big, is work coming in mid-Sprint, are there dependencies, is the Definition of Done unclear? On one team, we found that about a third of capacity went to unplanned production support. We made that visible, agreed with the Product Owner on a support rotation and smaller, more focused Sprint Goals, and the team met its goal in five of the next six Sprints.”
2. “A stakeholder asks a developer to add urgent work mid-Sprint.”
Redirect the request to the Product Owner, who decides priorities. If it’s truly urgent, the Product Owner and Developers discuss the impact on the Sprint Goal; if the Sprint Goal becomes obsolete, only the Product Owner can cancel the Sprint. Then coach the stakeholder on how to bring work in through the Product Backlog.
3. “The Daily Scrum has become a status report to the manager.”
Remind everyone it’s an event for the Developers to plan the next day toward the Sprint Goal, try a different format (walk the board, focus on the goal), coach the manager on why it matters, and ask the team what would make it useful.
4. “Two developers are in conflict.”
Talk to each privately, help them talk to each other with a focus on the work, use team working agreements, and escalate only if it’s beyond coaching (for example, harassment).
5. “Retrospectives produce the same complaints every Sprint.”
Change formats, narrow to one or two improvements, make them concrete with an owner, add them to the next Sprint Backlog, and check them at the next retrospective.
6. “Management wants to compare velocity across teams.”
Explain that velocity is a planning aid for one team, based on that team’s own estimates, so comparing teams invites gaming. Offer outcome measures instead: Sprint Goal success, cycle time, escaped defects, customer outcomes.
7. “The Product Owner is rarely available.”
Discuss the impact with the Product Owner using examples (blocked decisions, rework), agree on availability, and help them with backlog refinement techniques. If it continues, raise it with the people who appointed them.
8. “Technical debt is slowing the team down.”
Make it transparent with data (defects, cycle time), help the Developers and Product Owner discuss it, and include improvement work in the Product Backlog and Definition of Done rather than hiding it.
9. “Your team is fully remote across time zones.”
Agree on overlap hours, keep events short and well-facilitated, use a shared digital board, write decisions down, and rotate inconvenient meeting times fairly.
10. “A team member says Scrum is a waste of time.”
Ask why and listen; often an event isn’t delivering value. Fix that, and connect the events to the problems the team cares about.
Metrics questions
“How do you measure a team’s effectiveness?” Use a few measures the team understands and owns: Sprint Goal success rate, cycle time and throughput, escaped defects, team health surveys, and, most importantly, customer and business outcomes from the Increments. Avoid using metrics to judge individuals.
Scaling and Kanban questions
- “How does Scrum scale?” Several teams working on one product share one Product Goal, Product Backlog and Product Owner. Frameworks such as Nexus, LeSS and SAFe add coordination; be honest about which you’ve used.
- “Scrum vs Kanban?” Scrum uses fixed-length Sprints, defined accountabilities and events; Kanban focuses on visualizing flow and limiting work in progress, without required roles or iterations. Many Scrum teams use Kanban practices within Scrum.
Questions for experienced Scrum Masters
- “How have you helped an organization, not just a team, become more agile?”
- “Tell me about a time you removed an organizational impediment.”
- “How do you coach a new Product Owner?”
- “When would you advise a team not to use Scrum?”
- “How do you know when a team no longer needs you as much?”
Behavioral questions
- “Tell me about a team you helped improve. What changed, and how did you measure it?”
- “Tell me about a time you had to push back on a senior stakeholder.”
- “Tell me about a time a change you introduced didn’t work.”
Use the STAR method and include numbers where you can.
Certifications
Common entry certifications include Scrum.org’s Professional Scrum Master (PSM) and Scrum Alliance’s Certified ScrumMaster (CSM). They show knowledge; interviewers care more about what you’ve done with teams.
Questions to ask the interviewer
- “How many teams would I support, and how mature are they with Scrum?”
- “Who are the Product Owners, and how much time do they have for the team?”
- “What’s the biggest impediment teams face here today?”
- “How does leadership measure success for agile teams?”
Related guides: project manager interview questions, technical program manager interview questions, product manager interview questions and leadership interview questions.
Frequently asked questions
What questions are asked in a Scrum Master interview?
What are the Scrum events and timeboxes?
What is the role of a Scrum Master?
How do you answer "What would you do if the team keeps missing the Sprint Goal?"
What are the three Scrum artifacts?
Sources
- Ken Schwaber and Jeff Sutherland, The 2020 Scrum Guide. Read on 2 October 2026.
