25 Scrum Master Interview Questions: Real-World Situations and Model Answers

By Stephen Adindu, CSM, PSM and PSPO, Lead Coach at The Career Accelerators. Last updated October 2026.

Scrum Master interviews mix three kinds of question: real-world scenarios ("what would you do if..."), Scrum basics, and behavioural questions ("tell me about a time..."). The best answers protect the Sprint Goal, use the 2020 Scrum Guide's terms, show you coaching the team rather than fixing everything yourself, and end with a result.

Below are 25 Scrum Master interview questions, each with a short model answer written in your voice. They start with ten common real-world situations, then cover the basics, behavioural questions and the two questions Stephen prepares every Scrum Master student for. Swap in your own examples and numbers before the interview.

What's in this guide

How should you answer Scrum Master interview questions?

Basic questions check that you know Scrum: answer in two or three sentences, in the Scrum Guide's words. Scenario and behavioural questions check how you'd behave with a real team, so give them a little structure. For a scenario, walk through four steps:

For a behavioural question, tell one true story as situation, action and result. Keep it to a minute or two, put most of the time on what you did, and end with what changed.

Scrum Master interview questions based on real-world situations (1 to 10)

These scenarios cover scope creep, competing stakeholders, impediments, low morale and more. Each model answer is one good way to respond, not the only one.

1. How do you handle stakeholders who keep introducing new requirements during a Sprint, causing scope creep?

Model answer: "I'd protect the Sprint Goal. The Scrum Guide says no changes are made during the Sprint that would endanger it, so I'd ask stakeholders to take new requests to the Product Owner, who decides where they go in the Product Backlog. If a request is small and fits the Sprint Goal, the Developers and the Product Owner can agree to adjust scope. I'd also invite those stakeholders to the Sprint Review, which is where they can shape what comes next. If the pattern continues, I'd look for the cause with the Product Owner: maybe stakeholders can't see the Product Backlog, or our Sprints feel too long to wait for."

What they're checking: that you know new work goes through the Product Owner, and that you can say no without damaging the relationship.

2. In a complex project, how do you balance stakeholders with competing priorities?

Model answer: "Ordering the Product Backlog is the Product Owner's call, so my job isn't to pick a winner. It's to help the Product Owner and stakeholders reach a decision they can all see. I'd facilitate a session where each group explains the value and urgency of its request, and we compare them against the Product Goal. The Product Owner then orders the backlog and we keep it visible, so everyone knows where their item sits and why. The Sprint Review becomes the regular place to revisit those choices."

What they're checking: that you facilitate rather than decide, and that you make trade-offs transparent.

3. When a major impediment is beyond what your team can resolve, how do you escalate and prioritize it?

Model answer: "First I'd confirm it really is outside the team's control, because a self-managing team should solve what it can. Then I'd make it visible on our impediment board and explain its impact in plain terms: which part of the Sprint Goal is at risk and by when. I'd take it to whoever can remove it, whether that's another team's lead, a manager or a vendor, agree a date and follow up. I'd keep the Developers and the Product Owner informed, so the Product Owner can talk to stakeholders early if the goal is at risk. The Daily Scrum and the Retrospective are where we'd spot impediments like this sooner next time."

What they're checking: that you get impediments removed, which the Guide makes part of your job, without taking problems away from a team that can solve them.

4. What steps would you take to motivate a team facing burnout or low morale?

Model answer: "I'd start with one-to-one conversations, because people often won't say what's wrong in a group. Then I'd look for the cause: overcommitting at Sprint Planning, constant interruptions, unclear goals or decisions made without the team. In a Retrospective with a safe format, I'd help the team choose one or two changes, such as smaller Sprint Goals or a way to route interruptions through the Product Owner. Agile principles call for a pace people can keep up indefinitely, so I'd watch for overtime and raise it if it continues. If someone is struggling personally, I'd point them to their manager or the support the company offers."

What they're checking: that you look for causes rather than reaching straight for team-building events.

5. During a Sprint, business priorities change sharply. How would you handle a request to change scope mid-Sprint?

Model answer: "My first question would be whether the change makes the current Sprint Goal obsolete. If it doesn't, the new work goes to the Product Backlog and the Product Owner can order it for the next Sprint, which is never more than a month away. The Developers and the Product Owner can still clarify or renegotiate scope, as long as the Sprint Goal isn't put at risk. If the goal really is obsolete, the Product Owner can cancel the Sprint: only the Product Owner has that authority. We'd then plan a new Sprint around the new priority. What I wouldn't do is quietly swap work in and keep pretending the old goal still stands."

What they're checking: that you know the Sprint Goal is protected and that cancelling a Sprint is the Product Owner's decision.

6. How do you address technical debt within a Scrum framework, and stop it from building up?

Model answer: "The Scrum Guide doesn't use the term, but it does say quality shouldn't decrease during a Sprint. I'd help the Developers make the debt visible as Product Backlog items, explained in business terms, so the Product Owner can order it alongside new features. To stop new debt, I'd coach the team to strengthen the Definition of Done, for example by adding automated tests or code review. Some teams also agree with the Product Owner to spend part of each Sprint on improvement work. How the Developers fix the debt is their decision; my part is making sure the conversation happens."

What they're checking: that you use the Product Backlog and the Definition of Done, not side deals.

7. In a globally distributed team, how do you make sure communication and collaboration work?

Model answer: "I'd start with working agreements: core overlap hours, how quickly we reply and which channel is used for what. We'd hold the Daily Scrum at the same time and place every working day, as the Guide asks; for us the place is one video link. I'd help the team pick a fair time, and if no time suits everyone, rotate it from Sprint to Sprint, never day to day. One shared board in a tool like Jira would be the single source of truth for the Sprint Backlog. In meetings I'd ask quieter or remote people for their views directly, and in Retrospectives I'd use a tool that allows anonymous input. I'd also check how the arrangement is working in each Retrospective."

What they're checking: practical habits, and that you include everyone, not only the people in the main office. Our Scrum tools guide compares the boards and retrospective tools teams use.

8. What Agile metrics do you track to measure the team's performance, and how do you use them to improve?

Model answer: "I use metrics to help the team inspect and adapt, not to judge it. Velocity helps the Developers plan, but it's a measurement, not a target, and it can't be compared between teams. I also like flow measures such as cycle time, throughput, work in progress and work item age, because they show where work gets stuck. Alongside those, I'd track how often we meet the Sprint Goal and how many defects reach users. I'd bring the trends to the Retrospective and let the team decide what to change. Burn-down charts help with forecasting, but they don't replace inspecting what has actually been Done."

What they're checking: that you won't turn velocity into a target or a league table.

9. How do you foster a culture of continuous improvement within your Scrum team?

Model answer: "The Sprint Retrospective is the engine. I'd vary the format so it doesn't go stale, bring data such as cycle time or Sprint Goal results, and help the team leave with one or two concrete actions rather than a long wish list. The most useful improvement can go straight into the next Sprint Backlog, as the Guide suggests, so it gets done. At the next Retrospective we'd check whether it worked. Over time I'd want team members to suggest improvements between Retrospectives, without waiting for me."

What they're checking: that improvements are acted on and followed up, not just discussed.

10. As a Scrum Master, how do you make sure the Scrum events, such as the Daily Scrum and the Retrospective, are effective and not a waste of time?

Model answer: "The Guide asks me to make sure every event takes place, stays positive and productive, and keeps to its timebox. I'd start by reminding the team what each event is for. The Daily Scrum, for example, is for the Developers to inspect progress toward the Sprint Goal and adjust their plan, not a status report to me. I'd keep timeboxes, prepare the Sprint Review as a working session with stakeholders rather than a demo, and ask the team in the Retrospective which events feel useful and which don't. Then we'd change the format, not drop the event."

What they're checking: that you know each event's purpose. Interviewers often say "ceremonies"; the 2020 Scrum Guide calls them events, and using its word shows you've read it.

Basic Scrum Master interview questions on the Scrum framework (11 to 18)

Most interviews include a few knowledge checks. Answer them briefly and in the Guide's terms, then add where you've used the idea if you can. For general Agile questions, such as the Agile Manifesto, Kanban or user stories, see our 60 Agile interview questions and answers.

11. What is a Scrum Master accountable for?

Model answer: "For establishing Scrum as the Scrum Guide defines it and for the Scrum Team's effectiveness. I serve three groups. For the team, I coach self-management and get impediments removed. For the Product Owner, I help with Product Backlog techniques and stakeholder collaboration. For the organization, I help people understand and adopt Scrum, and I remove barriers between stakeholders and the team. The Guide calls Scrum Masters 'true leaders who serve the Scrum Team and the larger organization.'"

12. Who is on a Scrum Team?

Model answer: "One Scrum Master, one Product Owner and the Developers, usually 10 people or fewer, with no sub-teams or hierarchy. Since the 2020 Guide there's no separate 'Development Team'; it's one Scrum Team. The team is cross-functional and self-managing, which means it decides internally who does what, when and how."

13. What are the five Scrum events?

Model answer: "The Sprint, which holds the other four, then Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective." Be ready to give the purpose and timebox of each:

Source: The 2020 Scrum Guide. For shorter Sprints, the events are usually shorter.

14. What are the three Scrum artifacts and their commitments?

Model answer: "The Product Backlog, whose commitment is the Product Goal; the Sprint Backlog, whose commitment is the Sprint Goal; and the Increment, whose commitment is the Definition of Done. The commitments give each artifact something to measure progress against."

15. What is a Sprint Goal, and can it change during the Sprint?

Model answer: "It's the single objective for the Sprint, agreed by the whole Scrum Team before Sprint Planning ends. It gives the Developers focus and the flexibility to change which items they work on. The goal itself shouldn't change mid-Sprint: no changes are made that would endanger it. If the work turns out different from what we expected, the Developers negotiate the scope of the Sprint Backlog with the Product Owner without affecting the goal."

16. Who can cancel a Sprint?

Model answer: "Only the Product Owner. The Guide says a Sprint can be cancelled if its Sprint Goal becomes obsolete. That might happen if the market or the company's direction changes. The Scrum Master, a manager or a stakeholder can't cancel it. It's rare, and I'd treat it as a sign to look at why our Sprint Goals are going out of date."

17. What is the Definition of Done?

Model answer: "It's a formal description of the quality an Increment must meet. An item that doesn't meet it can't be released or even shown at the Sprint Review; it goes back to the Product Backlog. If the organization has a standard Definition of Done, every Scrum Team follows it as a minimum and can add to it."

18. Does Scrum require story points, velocity or user stories?

Model answer: "No. The Scrum Guide doesn't mention any of them. Scrum is deliberately incomplete, so teams add practices like these when they help. I'd use whatever helps the Developers forecast and plan, and drop it if it doesn't."

Why it's asked: interviewers use it to see whether you know the Guide itself or only one company's version of Scrum.

Behavioural Scrum Master interview questions (19 to 23)

These questions ask what you actually did. Answer with a real example as situation, action and result. If you haven't been a Scrum Master yet, use a live project or a past job and say which it is: being clear about where the example comes from builds trust.

19. Tell me about a time you helped a team resolve a conflict.

Model answer: "Situation: On a live project, two Developers disagreed about whether to rebuild a feature or patch it, and the argument was spilling into every Daily Scrum. Action: I met each of them separately to understand their concerns, then facilitated a short session where they listed the risks and costs of each option side by side. I asked the Product Owner to join for the part that affected value. Result: They agreed on a patch now and a rebuild item on the Product Backlog, and the Daily Scrum went back to 15 minutes."

20. Tell me about a time you helped a team become more self-managing.

Model answer: "Situation: The Developers were reporting to me in the Daily Scrum and waiting for me to assign tasks. Action: I explained that the Daily Scrum is their event, moved to the side of the room, and asked them to walk the board against the Sprint Goal themselves. When someone asked me what to pick up next, I asked what would move the goal forward most. Result: Within three Sprints they were running the Daily Scrum without me and raising blockers to each other first."

21. Tell me about a time you had to share bad news with a stakeholder.

Model answer: "Situation: Midway through a release, our forecast showed a feature a sales lead was counting on wouldn't be ready for her launch date. Action: I helped the Product Owner prepare the data and we told her that week rather than at the end. We showed her what could be Done by the date and what that meant for her launch. Result: She chose a smaller first version on time, and afterwards she started coming to Sprint Reviews so she wasn't surprised again."

22. Tell me about a mistake you made and what you learned.

Model answer: "Situation: Early on, I kept stepping in to remove every small blocker myself because I wanted the team to move fast. Action: In a Retrospective a Developer said they'd stopped trying to solve problems because I'd do it. I asked the team which blockers they could handle themselves and agreed to step in only for those outside their control. Result: They solved more on their own, and I learned that getting impediments removed doesn't always mean removing them myself."

23. You haven't held the Scrum Master title before. What experience can you bring?

Model answer: "Situation: I spent four years in customer service, leading a shift of eight people. Action: I ran short daily huddles, calmed escalations and brought ideas from the team to management, which is very close to facilitating events and removing impediments. During my training I then worked as the Scrum Master on a live project, making sure every Scrum event took place and facilitating Sprint Planning, Reviews and Retrospectives. Result: I can show you both: the people skills from my last role and the Scrum practice from the project."

Why it's asked: interviewers want to see that you can link past work to the Scrum Master accountabilities, not just list duties.

How we do it at TCA: the two questions every Scrum Master student practises (24 and 25)

Many TCA students who move into Scrum Master roles come from customer service, administration and finance. Stephen prepares every Scrum Master student for the two questions below. Ola's story is one example of that preparation: she was a customer service representative, and during the program she brought questions from her phone interviews to our group discussions to work through them.

24. The team keeps missing its Sprint Goal. What would you do?

Model answer: "I'd treat it as something for the team to inspect, not something for me to fix alone. First I'd look at the last few Sprints with the team: are the Sprint Goals single, clear objectives or just lists of items? Are we taking on too much at Sprint Planning? Is unplanned work arriving mid-Sprint? Are items reaching the Sprint unrefined, or failing the Definition of Done at the end? I'd bring that picture to the Retrospective and help the team choose one or two changes, such as a smaller, sharper Sprint Goal, more refinement with the Product Owner, or making unplanned work visible so the Product Owner can deal with it. I wouldn't extend the Sprint or lower the quality bar to hit the goal. Then I'd watch the next two or three Sprints to see whether the change worked."

What interviewers listen for: that you find the cause with the team, keep the Sprint fixed in length, keep the Definition of Done intact and measure the result.

25. Tell me about a time someone pushed back on the process. How did you handle it?

Model answer: "Situation: A senior Developer told me the Daily Scrum was a waste of time and started skipping it. Action: I asked to talk one-to-one, and listened rather than defended the event. It turned out a manager had been joining to collect status updates, so it felt like being checked on. I explained that the Daily Scrum belongs to the Developers, agreed with the manager to get updates from the board instead, and asked the team in the Retrospective how they wanted to run it. Result: The Developer came back, the event got shorter, and he started raising blockers earlier."

If you're changing careers: use a real example from your last job, such as a colleague who resisted a new way of logging customer complaints or month-end checks, and show the same steps: listen, find the reason, explain the purpose and involve the person in the change.

How do you prepare for a Scrum Master interview?

Work through this checklist in the week before:

Scrum Master interview FAQs

Can I answer Scrum Master interview questions if I've never been a Scrum Master?

Yes. Scrum Alliance notes that you can go after Scrum Master jobs without having held the role before. Use examples from a live project, volunteering or your last job, and say clearly where each one comes from. Facilitating, calming conflict and removing obstacles are skills many people already use in customer service, admin and finance roles.

Do I need a CSM or PSM certification to get a Scrum Master interview?

Not always. Scrum Alliance says certification isn't required to get a Scrum Master job, but some employers list the Certified ScrumMaster (CSM) in their qualifications. The CSM needs a 16-hour course with a Certified Scrum Trainer, followed by an online test: 50 questions in one hour, with 37 correct answers needed to pass. Scrum.org's Professional Scrum Master I (PSM I) doesn't require a course: it's 80 questions in 60 minutes with an 85% pass mark, at US$200 per attempt. Our CSM exam prep guide covers the test in detail.

What salary should I give if they ask about pay?

Job Bank Canada files the Scrum Master title under NOC 10019, "Other administrative services managers". That's a broad group, so the figure covers more than Scrum Master jobs. Its Canadian median is C$50.00 an hour, about C$97,500 a year at 37.5 hours a week for 52 weeks. Treat that as a starting point, and check your province and the size of the role. Our Scrum Master salary guide has the figures by province.

How long should my answers be?

Give definitions in two or three sentences. Scenario and behavioural answers usually work best at one to two minutes. If the interviewer wants more, they'll ask a follow-up question.

Should I say "ceremonies" or "events"?

Say "events": it's the 2020 Scrum Guide's term, and the word "ceremony" doesn't appear in the Guide. If the interviewer says "ceremonies", there's no need to correct them; just use the Guide's terms in your own answers.

What should I ask at the end of a Scrum Master interview?

Ask questions that show how you'd work: Who is the Product Owner, and how much time do they have for the team? What happens when urgent work arrives mid-Sprint? What would success look like in this role after six months? Our guide to questions to ask at the end of an interview has more.

Stephen's tip: Your last job is full of Scrum Master stories. A tense customer call you calmed down is a conflict story; a month-end process you fixed is an improvement story. Map two of them before the interview.

Ready to practise for your Scrum Master interview?

TCA's Agile Scrum Master Certification Course starts with a two-day comprehensive workshop on Agile and Scrum fundamentals, after which you're eligible to take the CSM test. You then take on the role of a Scrum Master on one of our live projects, with Jira and Confluence training, resume refinement and an intensive mock interview once you're invited to a Scrum Master job interview. The program includes guaranteed work experience on live projects and exclusive job placement opportunities through our industry partners and contacts.

If you only need the certification, our CSM certification training is a two-day, 16-hour course led by Certified Scrum Trainers, with 16 Scrum Education Units (SEUs).

Not sure which suits you? Book a free call with one of our coaches.

Related reading

• 60 Agile interview questions and answers, by role
• How to become a Scrum Master in Canada: steps, certification and pay
• How to prepare for your CSM certification exam

Sources

• The 2020 Scrum Guide (scrumguides.org): accountabilities, the five events and timeboxes, artifacts and commitments, protecting the Sprint Goal, Sprint cancellation, the Definition of Done, the Scrum Master's services, self-management and forecasting practices.
• Scrum Guide revision history: the move from a separate Development Team to one Scrum Team in 2020.
• Agile Alliance glossary: velocity: velocity as a measurement that isn't a target and can't be compared between teams.
• The Kanban Guide: the flow measures work in progress, throughput, work item age and cycle time.
• Principles behind the Agile Manifesto: sustainable pace.
• Scrum Alliance: becoming a Certified ScrumMaster: course length and trainers, the CSM test, and whether certification is needed for Scrum Master jobs.
• Scrum.org: Professional Scrum Master I: PSM I fee, format and pass mark.
• Job Bank Canada: Scrum Master (NOC 10019): the Canadian median wage, converted at 37.5 hours a week for 52 weeks.
• TCA's Agile Scrum Master and CSM certification training course pages: course details.