Scrum Master interviews check three things: whether you know the framework (roles, events, artifacts), whether you can coach a real team through problems, and whether you can stay a servant leader instead of acting as a project manager. Expect scenario questions such as a team that misses every sprint or a product owner who changes priorities mid-sprint.
Below are 22 questions with sample answers. The Scrum Guide changes slightly between editions, so mention which one you're using if asked.
Scrum basics
1. What is Scrum?
"A lightweight framework for delivering complex work in short cycles called sprints. A small team works toward a goal, inspects the result, and adapts. It's built on empiricism: transparency, inspection, and adaptation."
2. What are the Scrum roles?
"Developers, who build the product. The Product Owner, who maximizes the value of the product and manages the backlog. The Scrum Master, who helps the team and the organization understand and use Scrum well."
3. What are the Scrum events?
| Event | Purpose |
|---|---|
| Sprint | A time box of one month or less that holds all other events |
| Sprint Planning | Decide what can be done this sprint and how |
| Daily Scrum | A 15-minute check by the developers to plan the next 24 hours |
| Sprint Review | Inspect the increment with stakeholders and adapt the backlog |
| Sprint Retrospective | Inspect how the team worked and agree improvements |
4. What are the Scrum artifacts and their commitments?
"The Product Backlog with the Product Goal, the Sprint Backlog with the Sprint Goal, and the Increment with the Definition of Done. Each artifact has a commitment that makes progress transparent."
5. What's the Definition of Done, and why does it matter?
"A shared description of what must be true for work to count as complete, such as code reviewed, tested, documented, and deployable. Without it, 'done' means different things and quality drifts."
6. What's the difference between a Scrum Master and a project manager?
"A project manager directs work, tracks schedule, and often assigns tasks. A Scrum Master doesn't manage the team. They coach, remove impediments, protect the process, and help the team become self-managing."
Day-to-day work
7. What does a Scrum Master do all day?
"Facilitate events when needed, help the team spot and remove blockers, coach the Product Owner on backlog management, work with other teams and managers on obstacles, and track patterns such as carry-over or bugs to bring to the retrospective."
8. How do you run an effective retrospective?
"I set a safe space and a clear focus, gather data such as the sprint's events, let everyone contribute, group themes, choose one or two improvements with owners, and check them at the next retrospective. I vary the format to keep it fresh, and I avoid retros that only list complaints."
9. How do you handle a team that's bored of the daily Scrum?
"I ask them what they want from it. If it's become a status report to me, I remind them it's for the developers, shift the focus to the sprint goal, and try a different format such as walking the board from the right. The goal is to plan the next day, not to report."
10. How do you help a team estimate?
"I use relative estimation such as story points or t-shirt sizes, with discussion, as in planning poker. The point is shared understanding, not precision. I look at the team's past throughput to forecast, and I don't compare velocity between teams."
11. What is velocity, and how is it misused?
"The amount of work a team completes in a sprint, usually in story points. It helps a team forecast. It's misused as a performance target or to compare teams, which causes people to inflate estimates."
Scenarios
12. The team misses its sprint goal every sprint. What do you do?
"I'd look for causes using data and the team's view. Are stories too large? Is there work added mid-sprint? Are dependencies blocking them? Is the goal unclear? Then bring it to the retrospective and try an experiment, such as smaller stories, a limit on work in progress, or earlier refinement."
13. The Product Owner keeps changing priorities in the middle of the sprint. What do you do?
"I'd talk with them about the effect on the team and the sprint goal. Within a sprint, scope can be clarified with the developers, but the sprint goal is protected. If the change is urgent enough, the sprint may be cancelled by the Product Owner, which is rare. Otherwise it goes into the backlog for the next planning. I'd also help them with backlog refinement so priorities are clearer."
14. A stakeholder keeps going directly to the developers with requests. What do you do?
"I'd explain the cost to the team and the sprint, and point stakeholders to the Product Owner and the Sprint Review as the channels. I'd also coach the developers on how to redirect requests politely."
15. A developer dominates discussions while others stay silent. What do you do?
"In events I'd use techniques that draw everyone in, such as writing ideas silently first, round-robin turns, or breakout pairs. Privately, I'd talk with the dominant person about making room. I'd watch what the quieter members need."
16. A manager wants you to report on individual productivity. What do you say?
"I'd explain that Scrum measures the team's outcomes and that individual metrics reduce collaboration. I'd offer team-level measures such as cycle time, throughput, and quality, and share how the work is going."
17. How do you deal with conflict within the team?
"I bring the issue into the open early, listen to each person separately, and then help them talk directly about the problem and its effect. I focus on the behavior and the goal and not the person, and I agree on an action. If it doesn't resolve, I involve a manager."
18. What would you do if the team isn't following Scrum?
"First ask why. It may be that a practice isn't useful in their context, or no one explained it. I'd coach with the reason behind each practice, suggest an experiment, and review the result. I'd raise organizational blockers, such as managers assigning tasks, with leadership."
Agile and tools
19. What's the difference between Scrum and Kanban?
"Scrum has fixed-length sprints, defined roles, and events. Kanban is a flow system: visualize work, limit work in progress, and manage flow, with no required time boxes. Many teams combine ideas from both."
20. How do you scale Scrum across several teams?
"Start by making dependencies visible and keeping teams cross-functional. Use a shared cadence, a Scrum of Scrums or similar sync, and a common backlog or goals. Frameworks such as Nexus, LeSS, or SAFe exist, but I'd start with the simplest approach that solves the real problem."
21. Which tools do you use?
"Jira or a similar tracker, a digital whiteboard for retrospectives, and the team's own board. I choose tools the team will keep up to date, and use them to make work visible, not for surveillance."
22. Do you have any questions for us?
"How many teams work on this product, and how do they coordinate? How does leadership feel about Scrum, and what has been tried? What's the biggest obstacle your teams face?"
Certifications
Many job postings ask for a certification such as Certified ScrumMaster or Professional Scrum Master. They show you've learned the framework, but interviewers care more about what you did with a real team. Prepare examples of an impediment you removed and an improvement a retrospective led to.
How to prepare
Prepare stories for: a team you coached through a problem, a conflict you helped resolve, a retrospective that changed something, and a time you pushed back on management. Reread the current Scrum Guide so your terms are accurate. See our leadership interview guide and management interview guide for related questions.
Practice in a mock interview and read the transcript for places where you gave a definition when the question asked what you'd do. Follow the employer's rules on AI tools in any live interview.
Practice Scrum Master answers with YesToTheOffer
Run a mock interview, talk through team scenarios out loud, and review your transcript afterward. 30 free minutes, no subscription.
