Scrum Master Scenario Interview Questions: 25 Questions With Model Answers
Scrum Master interviews have shifted from "define the Sprint Retrospective" to scenario questions: what would you do if...? Hiring managers know that anyone can memorise the Scrum Guide, so they probe judgement. This lesson gives 25 realistic questions in five groups, each with a model answer approach. Do not memorise the answers word for word. Use them to practise structuring your own experience, and adapt them to your real stories. For general preparation advice see Scrum Master Interview Preparation.
How to Structure an Answer
Use a simple frame: Situation, Action, Result, Learning. Keep each answer to about two minutes. Where you lack direct experience, say so honestly and explain how you would approach the situation, drawing on principles from the Scrum Guide and your coaching practice. Authenticity beats invented heroics.
Group 1: Scrum Fundamentals Applied
1. What is the difference between a Scrum Master and a project manager?
Model answer: A project manager typically owns the plan, assigns tasks and reports against scope, time and budget. A Scrum Master has no authority over the work or the people; they are accountable for helping the team and organisation understand and use Scrum effectively. Planning moves to the Product Owner and Developers, and I focus on removing impediments, coaching and facilitating. I would add that some project management needs, such as budgets or vendor contracts, still exist and I can support them without taking over the team's decisions. See Scrum Master vs Project Manager vs Product Owner.
2. Is the Definition of Ready part of Scrum?
Model answer: No, it is not in the Scrum Guide. The Definition of Done is. Readiness is better treated as an outcome of good refinement than as a gate. If a team finds a Definition of Ready helpful, I would keep it short and review it regularly so it does not create handoffs. See Definition of Ready vs Definition of Done.
3. A team consistently carries over stories. What do you do?
Model answer: I would first look at data: how many stories, how large and why. Then I would facilitate a retrospective to explore causes: stories too big, too much work in progress, hidden dependencies, over-commitment or interruptions. Possible actions are smaller slicing, a lower WIP, a more realistic Sprint Goal and addressing dependencies. I would avoid solving it by extending the Sprint. See Splitting User Stories.
4. Can a Sprint be extended if the team needs more time?
Model answer: No. Sprints are fixed-length. Unfinished items return to the Product Backlog and the Product Owner re-orders them. Extending hides real capacity and removes the regular inspection that Scrum depends on.
5. When can a Sprint be cancelled, and by whom?
Model answer: Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete, for example because the company direction changed or the product is no longer needed. It is rare, and it is worth a retrospective-style conversation about how the situation arose.
Group 2: Working With the Product Owner and Stakeholders
6. The Product Owner is never available. What do you do?
Model answer: First, I would seek to understand why: overloaded, unclear on the role or caught in organisational demands. I would have a private conversation with the Product Owner, share the impact on the team with concrete examples, and explore options such as scheduled office hours, a proxy for day-to-day questions or reducing their other responsibilities. If the problem is structural, I would raise it with the sponsor as an impediment. See Product Owner Collaboration.
7. A senior stakeholder bypasses the Product Owner and gives the team work directly. How do you respond?
Model answer: I would protect the team's focus without embarrassing the stakeholder. I would thank them for their input, explain that priorities go through the Product Owner so that trade-offs are visible, and introduce them to the Product Owner. I would also coach the team to redirect such requests politely. If it persists, I would raise it with leadership as an organisational impediment. See Stakeholder Management.
8. A stakeholder insists on a fixed scope, fixed date and fixed budget. What do you say?
Model answer: I would explain the trade-off between scope, time and cost and show data about the team's pace. I would propose fixing the date and budget while flexing scope, ordering by value so that the most important items are delivered first, with regular reviews so they can see progress and decide. See Agile Release Planning and Roadmaps.
9. The Product Owner keeps adding items mid-Sprint. What do you do?
Model answer: I would remind the team and Product Owner of the Sprint Goal as the commitment. New items can enter the backlog, and if something is genuinely urgent, the Product Owner and Developers discuss what can be traded out without endangering the goal. If it keeps happening, I would examine whether the Sprint is too long for the volatility of requirements.
10. How do you handle a Sprint Review where stakeholders do not attend?
Model answer: I would find out why. Perhaps the event is poorly timed, feels like a status meeting, or does not show anything meaningful. I would work with the Product Owner to make it more valuable: live demos, a clear Sprint Goal story and specific questions for stakeholders. I would also talk to key stakeholders individually. See Sprint Review Explained.
Group 3: Team Dynamics and Coaching
11. Two Developers have a persistent conflict. How do you approach it?
Model answer: I would speak to each privately to understand their perspectives, then, if appropriate, facilitate a conversation focused on specific behaviours and shared goals, not personalities. I would encourage them to find the solution themselves and follow up. If it affects the team, I would use a retrospective to look at working agreements. See Conflict Management.
12. One team member dominates every discussion. What do you do?
Model answer: I would use facilitation techniques: silent writing before discussion, round-robin input and time-boxed contributions. Privately, I would give the dominant person feedback and ask for their help drawing others in. I would also invite quieter members to share in ways they find comfortable. See Facilitation Techniques.
13. The team says Scrum is a waste of time. How do you respond?
Model answer: I would listen first. They often have valid frustrations with how Scrum has been implemented. I would ask which parts feel wasteful, connect each event to the problem it should solve and propose small experiments, such as shortening the Daily Scrum or changing the retrospective format. The aim is value, not ritual. See Common Scrum Myths.
14. Nobody speaks in the retrospective. What do you do?
Model answer: I would suspect lack of psychological safety or a stale format. I would try anonymous input, a different format and a clear statement that the purpose is system improvement, not blame. Over time I would work on trust through my own behaviour, and check in one-to-one. See Retrospective Formats and Psychological Safety.
15. How would you help a team that is new to Agile?
Model answer: I would start by understanding their context and concerns, then teach the fundamentals briefly with practical exercises. I would introduce practices incrementally, a visible board, a Sprint Goal, a basic Definition of Done, and use retrospectives to adapt. I would stay close in the first few Sprints and gradually step back as they grow. See Scrum Team Maturity and First 90 Days as a Scrum Master.
Group 4: Metrics, Quality and Delivery
16. Management wants to compare velocity across teams. What do you say?
Model answer: Velocity is a planning tool specific to one team's estimation scale, so cross-team comparison is misleading and encourages gaming. I would offer more meaningful measures such as cycle time, Sprint Goal success and customer outcomes. See Scrum Metrics Explained and Forecasting in Scrum and Agile.
17. The team is pressured to skip testing to meet a deadline. What do you do?
Model answer: I would remind everyone that the Definition of Done is a commitment and that unfinished quality becomes technical debt. I would help the Product Owner and stakeholders see the options: reduce scope, adjust the date or accept visible risk explicitly. I would not allow quality to be silently compromised. See Technical Debt and Spikes.
18. How do you measure whether a team is improving?
Model answer: I would combine quantitative and qualitative signals: flow measures such as cycle time and throughput, quality indicators such as escaped defects, Sprint Goal success rate and team health surveys, along with customer feedback. I would use these in retrospectives for learning rather than judging individuals.
19. What is your approach to estimation?
Model answer: Scrum does not mandate a method. I help the team find an approach they trust, whether relative sizing with story points, simple sizing categories or counting items with historical throughput, and I stress that estimates are for planning and not for performance evaluation. See Agile Estimation Beyond Story Points.
20. A stakeholder asks, "When will feature X be done?" How do you answer?
Model answer: I would provide a forecast as a range based on the team's actual history, explain the assumptions and what could change it, and show a regularly updated burnup chart. I would avoid single-point commitments unless scope is truly fixed and understood.
Group 5: Organisation, Career and Self-Awareness
21. What do you do when the organisation does not support Agile?
Model answer: I would focus on what the team can control, build evidence through small wins and communicate benefits in terms leaders care about, such as speed to feedback and reduced risk. I would identify allies, escalate genuine impediments with data and accept that change takes time.
22. Describe a time you failed as a Scrum Master.
Model answer approach: Choose a real failure, perhaps taking over a facilitation role too much or not challenging a stakeholder early. Describe what happened, what you learned and what you do differently now. Interviewers value honesty and reflection far more than a polished success story.
23. How do you handle working with multiple teams?
Model answer: I prioritise based on each team's maturity and needs, avoid spreading too thin and aim to grow self-sufficiency so that teams rely less on me over time. I would be explicit with leadership about the limits of what is possible and use patterns such as shared practices and communities of practice. See Scaling Agile Frameworks Compared.
24. Why do you want to be a Scrum Master?
Model answer approach: Connect your motivation to enabling teams, learning and helping people grow, with an example of something you enjoyed, such as facilitating a workshop or solving a team problem. Avoid generic claims. If you are transitioning from another role, link your previous experience; see From Project Manager to Scrum Master.
25. What questions do you have for us?
Model answer approach: Ask about the maturity of Agile in the organisation, how the Scrum Master role is viewed, how teams are formed, what impediments are typical, and how success is measured. Good questions show that you think about outcomes. Avoid asking only about salary and perks at this stage.
Practice Method
- Pick five questions a day and answer aloud, timing yourself.
- Replace the model details with your own examples.
- Record yourself or practise with a friend, and listen for waffle.
- Prepare three stories from your own experience that you can adapt: a conflict, a failure and an improvement.
- Review the Scrum Master Final Learning Checklist to find gaps.
- Interviewers test judgement through scenarios; use Situation, Action, Result, Learning.
- Be honest about experience and show how you think, not just what you know.
- Prepare real stories from your own work for conflicts, failures and improvements.
- Ask thoughtful questions about the organisation's Agile maturity.