Scrum Master Interview Questions

Quick answer

Scrum Master interviews test three things: your knowledge of the Scrum Guide, how you handle real team situations, and how you work with people under pressure. Expect questions on the three accountabilities, five events and three artifacts, then scenario questions such as a Daily Scrum that runs too long or a Product Owner who changes scope mid-sprint. Experienced candidates also face questions on metrics, scaling, SAFe and coaching leaders. Answer scenario questions with a simple structure: the situation, what you did, why it fits Scrum, and the result.

Key takeaways

1. How Scrum Master interviews work

Short answer: Most companies run three to five rounds: a recruiter screen, a Scrum knowledge round, a scenario or managerial round, sometimes a role play, and an HR round.

The exact process varies by company, but this pattern is common in Indian IT services firms, global capability centres and product companies.

How to answer scenario questions

Use a simple four-part structure:

Keep answers short. Two minutes is usually enough. Let the interviewer ask follow-ups.

2. Basic Scrum Master interview questions

Short answer: Basic questions check that you understand what Scrum is, why teams use it and what a Scrum Master actually does. Freshers and career switchers get many of these.

Q1. What is Scrum?

Scrum is a lightweight framework that helps people, teams and organisations create value through adaptive solutions for complex problems. It is based on empiricism and lean thinking. Work happens in short Sprints, and the team inspects and adapts its product and its way of working at the end of each one.

Q2. What is Agile, and how is Scrum related to it?

Agile is a set of values and principles for delivering work in small, frequent increments with close customer collaboration. Scrum is one framework that puts those ideas into practice. Kanban, XP and SAFe are other approaches often used in agile organisations.

Q3. What does a Scrum Master do?

A Scrum Master is accountable for the Scrum Team's effectiveness. They help the team, the Product Owner and the organisation understand and use Scrum well. In practice, that means coaching self-management, removing impediments, making sure events happen and stay productive, and helping the organisation adopt Scrum.

Q4. What are the three pillars of empiricism?

The three pillars are transparency, inspection and adaptation. Transparency means the work and the process are visible to everyone involved. Inspection means checking progress often, and adaptation means changing course quickly when something is off.

Q5. What are the five Scrum values?

The Scrum values are commitment, focus, openness, respect and courage. They guide how the team works and behaves. A Scrum Master helps the team live these values, for example by encouraging the courage to raise problems early.

Q6. Is the Scrum Master a project manager?

No. A Scrum Master does not assign tasks or manage people in the traditional way. The Developers decide how to do the work, and the Product Owner decides what to build. The Scrum Master serves the team and the organisation by improving how Scrum is used.

Q7. What does "servant leadership" mean for a Scrum Master?

The Scrum Guide 2020 calls Scrum Masters "true leaders who serve the Scrum Team and the larger organization." It means you lead by helping others succeed, not by giving orders. You remove obstacles, coach, facilitate and protect the team's focus.

Q8. Why do companies use Scrum?

Companies use Scrum to deliver value in small, frequent increments, get feedback early and adapt to change. It reduces the risk of building the wrong thing for months. It also makes progress visible through regular events and artifacts.

3. Scrum Guide interview questions

Short answer: These questions check that you know the Scrum Guide 2020 exactly. Use its terms, because interviewers notice outdated words such as "Development Team".

Q9. What are the three accountabilities in Scrum?

The Scrum Guide 2020 defines three accountabilities: Developers, the Product Owner and the Scrum Master (Scrum Guide, checked October 2026). Developers create a usable Increment each Sprint. The Product Owner maximises the value of the product, and the Scrum Master is accountable for the team's effectiveness.

Q10. What changed in the 2020 Scrum Guide?

The 2020 guide replaced "Development Team" with "Developers" to stress one Scrum Team, introduced the Product Goal, and added commitments for each artifact. It also replaced "self-organising" with "self-managing" and made the guide less prescriptive, for example by removing the three Daily Scrum questions. The language became simpler and less software-specific.

Q11. How big should a Scrum Team be?

The Scrum Guide says a Scrum Team is typically 10 or fewer people. Smaller teams communicate better and are more productive. If a team grows too large, the guide suggests reorganising into several cohesive Scrum Teams that share the same Product Goal and Product Backlog.

Q12. What does the Scrum Master do for the Developers?

The Scrum Master coaches the team in self-management and cross-functionality, and helps them focus on high-value Increments that meet the Definition of Done. They cause the removal of impediments. They also make sure all Scrum events take place, stay positive and productive, and stay within the timebox.

Q13. What does the Scrum Master do for the Product Owner?

The Scrum Master helps the Product Owner find techniques for defining the Product Goal and managing the Product Backlog. They help the team understand why clear, concise backlog items matter. They also help set up empirical product planning and facilitate stakeholder collaboration when needed.

Q14. What does the Scrum Master do for the organisation?

The Scrum Master leads, trains and coaches the organisation in Scrum adoption. They plan and advise Scrum implementations and help people understand an empirical approach to complex work. They also remove barriers between stakeholders and Scrum Teams.

Q15. Is Scrum free to use?

Yes. The Scrum Guide says Scrum is free and offered in the guide itself, and it is published under a Creative Commons licence (CC BY-SA 4.0). You can use Scrum without paying anyone. Certifications are optional and come from separate bodies.

4. Scrum events interview questions

Short answer: Event questions check that you know the purpose, timebox and attendees of each event, and how a Scrum Master keeps them useful.

Q16. What are the five Scrum events?

The five events are the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. The Sprint is the container for all the other events. Each event is a formal chance to inspect and adapt.

Q17. What are the timeboxes for Scrum events?

For a one-month Sprint, the Scrum Guide sets these maximums: Sprint Planning 8 hours, Daily Scrum 15 minutes, Sprint Review 4 hours and Sprint Retrospective 3 hours. The Sprint itself is one month or less. For shorter Sprints, these events are usually shorter.

Q18. What happens in Sprint Planning?

The Scrum Team decides why the Sprint is valuable, what can be done, and how the chosen work will get done. The result is a Sprint Goal, the selected Product Backlog items and a plan for delivering them. Together these form the Sprint Backlog.

Q19. What is the purpose of the Daily Scrum?

The Daily Scrum lets the Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed. It is a 15-minute event for the Developers. The Scrum Guide no longer requires the three classic questions, so the team can use any structure that keeps it focused.

Q20. Does the Scrum Master have to attend the Daily Scrum?

No. The Daily Scrum is for the Developers. The Scrum Master makes sure it happens and helps the team keep it within 15 minutes, but does not need to run it. If the Scrum Master or Product Owner is actively working on Sprint Backlog items, they take part as Developers.

Q21. What happens in the Sprint Review?

The Scrum Team presents the results of its work to key stakeholders and discusses progress toward the Product Goal. Attendees review what changed and decide what to do next, which may update the Product Backlog. It is a working session, not just a demo.

Q22. What is the Sprint Retrospective for?

The Sprint Retrospective is where the Scrum Team plans ways to increase quality and effectiveness. The team inspects how the last Sprint went regarding people, interactions, processes, tools and the Definition of Done. The most helpful changes are addressed as soon as possible, and some may be added to the next Sprint Backlog.

Q23. Can a Sprint be cancelled, and who can cancel it?

Yes, but only the Product Owner has the authority to cancel a Sprint. It happens if the Sprint Goal becomes obsolete, for example after a major business change. Cancellation is rare and should be treated as a serious event.

Q24. Is backlog refinement a Scrum event?

No. Product Backlog refinement is an ongoing activity, not one of the five events. The team breaks down and adds detail to backlog items so they are ready for future Sprints. Many teams schedule regular refinement sessions anyway to keep the backlog healthy.

5. Scrum artifacts interview questions

Short answer: Artifact questions check that you know the three artifacts, their commitments and why the Definition of Done matters.

Q25. What are the three Scrum artifacts?

The three artifacts are the Product Backlog, the Sprint Backlog and the Increment. Each artifact makes work and value transparent. Each also has a commitment that gives it focus.

Q26. What commitment goes with each artifact?

The Product Backlog has the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done. These commitments give each artifact a clear purpose and a way to measure progress.

Q27. What is the Definition of Done?

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. Work that does not meet it cannot be released or presented at the Sprint Review. It creates shared understanding and transparency about what "done" means.

Q28. What is the difference between the Definition of Done and acceptance criteria?

The Definition of Done applies to every item and the whole Increment, for example code reviewed, tested and documented. Acceptance criteria are specific to one backlog item and describe what that item must do. An item is complete only when it meets both.

Q29. Who owns the Product Backlog?

The Product Owner is accountable for the Product Backlog, including its content, ordering and transparency. The Product Owner may ask others to do some of this work but stays accountable. The Developers own the Sprint Backlog.

Q30. Can the Sprint Backlog change during the Sprint?

Yes. The Developers update the Sprint Backlog throughout the Sprint as they learn more. The Sprint Goal stays fixed, but the plan to reach it can change. Scope may be clarified and renegotiated with the Product Owner if needed.

6. Agile metrics interview questions

Short answer: Metrics questions check whether you can use data to help the team improve without turning numbers into targets or weapons.

Q31. What is velocity, and how should it be used?

Velocity is the amount of work, often in story points, a team completes in a Sprint. It helps the team forecast how much it can take on in future Sprints. It should not be used to compare teams or judge individuals, because story points are relative and team-specific.

Q32. What is a burndown chart?

A burndown chart shows the work remaining in a Sprint over time. A line that falls steadily toward zero suggests the team is on track. A flat line or a late drop can signal blockers, unclear items or work that is too large.

Q33. What is the difference between a burndown and a burnup chart?

A burndown shows work remaining, while a burnup shows work completed against total scope. A burnup is useful for releases because it shows scope changes clearly. When the scope line rises, everyone can see that new work was added.

Q34. What is cycle time, and why does it matter?

Cycle time is the time an item takes from when work starts to when it is done. Shorter, more predictable cycle times usually mean better flow. Tracking it helps the team spot bottlenecks such as long waits for code review or testing.

Q35. What would you do if management wants to compare velocity across teams?

I would explain that velocity is relative to each team's own estimates, so comparing it across teams is misleading and can push teams to inflate estimates. I would suggest outcome-based measures instead, such as delivered value, cycle time and customer feedback. I would offer to build a dashboard that answers the real question behind the request.

Q36. Which metrics do you track as a Scrum Master?

I track velocity for forecasting, sprint burndown for progress, cycle time and throughput for flow, and the share of Sprint Goals met. I also watch team health signals from retrospectives, such as recurring blockers. I treat all of these as conversation starters with the team, not targets.

7. Scenario-based Scrum Master interview questions

Short answer: Scenario questions are the heart of most interviews. Show that you protect Scrum, respect people and focus on outcomes.

Q37. The Daily Scrum keeps running for 30 to 40 minutes. What do you do?

I would first observe why it overruns, which is often problem-solving or status reporting to a manager. I would remind the team that the Daily Scrum is 15 minutes and focused on the Sprint Goal, and suggest moving detailed discussions to right after the event with only the people needed. I might use a visible timer and a board-based format that walks the work instead of the people.

Q38. The Product Owner wants to add work in the middle of the Sprint. How do you respond?

I would help the Product Owner see the impact on the Sprint Goal. If the new work is urgent and fits the goal, the Developers and Product Owner can renegotiate scope, usually by removing something of similar size. If it does not fit and is truly critical, the Product Owner may consider cancelling the Sprint, but that should be rare.

Q39. The team keeps missing the Sprint Goal. How do you handle it?

I would raise it in the retrospective and look for patterns with the team, such as over-commitment, unclear items, dependencies or unplanned work. Based on the causes, we might take on less work, improve refinement or make dependencies visible earlier. I would track whether the change helps over the next few Sprints.

Q40. A senior developer dominates discussions and others stay quiet. What do you do?

I would speak to the developer privately, acknowledge their expertise and ask for help drawing out others' ideas. In events, I would use facilitation techniques such as silent writing, round-robins or small group work so everyone contributes. I would watch whether quieter members start speaking up.

Q41. Two team members are in conflict. How do you help?

I would first listen to each person separately to understand the issue. Then I would bring them together, focus on shared goals and facts, and help them agree on how they will work together. If the conflict continues or becomes personal, I would involve their manager or HR as appropriate.

Q42. A manager asks you for individual performance reports from Jira. What do you do?

I would explain that Scrum focuses on team outcomes, and individual reports from Jira can damage collaboration and encourage gaming the numbers. I would ask what problem the manager is trying to solve. Then I would offer team-level data and suggest that individual feedback happens through normal people-management conversations.

Q43. The team says retrospectives are boring and useless. What do you change?

I would change the format, for example by using different retro techniques, rotating facilitators or focusing on one theme. More importantly, I would make sure action items are small, owned and followed up, because retros feel useless when nothing changes. I would show the team what improved because of past retros.

Q44. Stories are often carried over to the next Sprint. What would you do?

I would look at why: items too large, unclear acceptance criteria, dependencies or too much work in progress. Fixes include splitting stories smaller, improving refinement, limiting work in progress and swarming on items to finish them. I would track carry-over across Sprints to see whether the changes help.

Q45. A stakeholder goes directly to developers with new requests. How do you handle it?

I would thank the stakeholder for their interest and explain that requests go through the Product Owner so priorities stay clear. I would coach the developers to redirect such requests politely. If it keeps happening, I would help the Product Owner set up a regular channel for stakeholder input, such as the Sprint Review.

Q46. The team does not want to estimate. What do you do?

I would ask why, because the team may find estimation slow or misused. Options include lighter techniques such as t-shirt sizing, or forecasting from throughput instead of story points. The goal is useful forecasting, not estimation for its own sake.

Q47. Your team has a critical production issue mid-Sprint. What happens?

The team handles the issue, because production stability usually matters more than planned work. I would help the team and Product Owner reassess the Sprint Goal and adjust the Sprint Backlog. Afterwards, I would raise the issue in the retrospective to look for causes and prevention.

8. Behavioural Scrum Master interview questions

Short answer: Behavioural questions check how you think and act. Use real stories with the situation, action, Scrum link and result.

Q48. Tell me about a time you removed a difficult impediment.

Pick a real example, such as a long wait for test environments or another team's dependency. Explain how you found the root cause, who you worked with and what changed. End with the result, such as faster delivery or fewer blocked items, using your own numbers.

Q49. How do you handle a team that resists Scrum?

I start by understanding their concerns, because resistance often comes from bad past experiences. I explain the purpose behind each practice, start with small changes and let the team see results. I also involve the team in deciding how to improve, which builds ownership.

Q50. Describe a time you disagreed with your manager.

Share a real example where you disagreed respectfully, for example on individual metrics or adding scope. Explain how you shared data and Scrum reasoning, listened to their view and reached an outcome. Show that you can push back without damaging the relationship.

Q51. How do you keep yourself learning as a Scrum Master?

I reread the Scrum Guide, read agile books and blogs, attend meetups and learn from other Scrum Masters. I also experiment with new facilitation techniques in retrospectives. I review what worked and what did not with my team.

Q52. What is your biggest weakness as a Scrum Master?

Choose a real but manageable weakness and show how you are working on it. For example, you may have jumped in to solve problems for the team, and you now ask coaching questions instead. Avoid fake answers such as "I work too hard".

Q53. Why do you want to be a Scrum Master?

Give an honest answer that links your strengths to the role, such as enjoying helping teams work better and solving people and process problems. Mention a moment that showed you this, for example running your first retrospective. Keep it short and specific.

9. Jira and tools interview questions

Short answer: Tool questions check that you can run Scrum day to day in Jira and Confluence and produce useful reports.

Q54. How do you set up a Scrum project in Jira?

I create a Scrum board, set up the Product Backlog with epics and stories, and configure the workflow to match how the team works. Then I create a Sprint, help the team pull items into it during Sprint Planning and start it. I also set up quick filters and a dashboard for the team.

Q55. Which Jira reports do you use?

I use the burndown chart for sprint progress, the velocity chart for forecasting, the sprint report to review what was completed and carried over, and the control chart or cycle time reports for flow. I share them with the team as input for discussion, not as judgement.

Q56. How do you use Confluence as a Scrum Master?

I use Confluence for team agreements, the Definition of Done, retrospective notes, meeting notes and release notes. Linking Confluence pages to Jira issues keeps decisions traceable. It helps new team members get up to speed quickly.

Q57. What tools do you use for remote retrospectives?

I use digital whiteboards such as Miro or MURAL, or retro tools with templates and anonymous voting. On video calls through Zoom or Microsoft Teams, I keep cameras on where possible and use timeboxes. The tool matters less than good facilitation and follow-through on actions.

Q58. How do you use AI tools as a Scrum Master?

I use AI tools to summarise meetings, draft sprint reports and suggest retro formats, which saves time. I always check the output, because AI can miss context or get facts wrong. I use the time saved for coaching and improving the team.

10. SAFe and scaling interview questions

Short answer: Scaling questions appear in global capability centres and banks that run SAFe or other scaled frameworks. Know the basic terms and the Scrum Master's role.

Q59. What is SAFe?

SAFe, the Scaled Agile Framework, is a framework from Scaled Agile for applying agile and lean practices across many teams. It organises teams into Agile Release Trains that plan and deliver together. Scaled Agile offers its own SAFe Scrum Master certification for Scrum Masters in SAFe organisations.

Q60. What is an Agile Release Train?

An Agile Release Train (ART) is a long-lived team of agile teams that plans, commits and delivers together toward a shared mission. It typically includes several teams plus roles such as the Release Train Engineer. All teams on the train align on a common cadence.

Q61. What is PI Planning, and what is the Scrum Master's role in it?

PI Planning is a regular event where all teams on an Agile Release Train plan the next Program Increment together. The Scrum Master, sometimes called a Team Coach in SAFe material, helps the team plan realistically, surfaces dependencies and risks, and facilitates the team's breakouts. Afterwards, they help the team track its PI objectives.

Q62. How do you scale Scrum without SAFe?

Other approaches include Nexus, LeSS and Scrum@Scale, each with its own rules. Whatever the framework, the key ideas are a shared Product Goal, one Product Backlog per product, frequent integration and clear management of dependencies. I would choose the lightest approach that solves the coordination problem.

Q63. What is a Scrum of Scrums?

A Scrum of Scrums is a meeting where representatives from several Scrum Teams coordinate work and surface cross-team dependencies and impediments. It is not part of the Scrum Guide, but many organisations use it when several teams work on one product. Keep it short and focused on integration risks.

11. Interview questions for experienced Scrum Masters

Short answer: Experienced and senior candidates face deeper questions on coaching, transformation, leadership and measurable impact.

Q64. How do you measure your success as a Scrum Master?

I measure success through the team's outcomes and health: steadier delivery of Sprint Goals, shorter cycle times, better quality and better stakeholder feedback. I also look at team self-management, such as whether the team solves problems without me. A team that needs me less over time is a sign of success.

Q65. How would you lead an agile transformation in a traditional organisation?

I would start with the purpose and a pilot team, show results and expand step by step. I would work with leaders on their own behaviour, because transformation fails if leadership habits do not change. I would also train teams, set up communities of practice and adjust the approach based on feedback.

Q66. How do you coach leaders who micromanage teams?

I would understand what worries them, often visibility or risk, and give them better transparency through Sprint Reviews and dashboards. I would coach them on asking for outcomes instead of tasks. Small experiments, such as letting the team choose how to deliver one feature, can build trust.

Q67. How many teams can a Scrum Master support effectively?

It depends on team maturity, complexity and the organisation. A new team may need a full-time Scrum Master, while mature teams may share one. I would be honest that supporting too many teams turns the role into meeting scheduling and reduces real coaching.

Q68. How do you handle a Product Owner who is unavailable to the team?

I would talk to the Product Owner about the impact, such as unclear items and wasted work. Together we might set fixed refinement and question-answering slots, or agree on a delegate for day-to-day questions while the Product Owner stays accountable. If the problem continues, I would raise it with leadership as an organisational impediment.

Q69. What is the difference between a Scrum Master and an Agile Coach?

A Scrum Master usually focuses on one or a few Scrum Teams and their effectiveness. An Agile Coach works more broadly across teams and leadership, often with several frameworks and organisation-wide change. Many Agile Coaches come from experienced Scrum Master backgrounds.

Q70. Which certification do you hold, and why did you choose it?

Give an honest answer about your certification and your reason. For example, the CSM from Scrum Alliance involves 16 hours of training with a Certified Scrum Trainer and an online test of 50 questions in one hour, with a pass mark of 37 out of 50 (Scrum Alliance, October 2026). Explain what you learned and how you use it at work.

12. Questions to ask the interviewer

Short answer: Asking smart questions shows you understand the role. Ask about the team, the agile maturity and how success is measured.

The answers tell you a lot about whether the role is a real Scrum Master job or mostly project coordination.

13. How to prepare for a Scrum Master interview

Short answer: Revise the Scrum Guide, prepare five to eight real stories, practise scenario answers out loud, know your metrics and tools, and research the company before each round.

Freshers and career switchers

If you have not worked as a Scrum Master yet, use stories from your current role, such as testing, analysis or coordination, and from practice projects. Be honest about what was practice. Interviewers value clear thinking and honesty more than inflated titles. Our guide to Scrum Master roles and responsibilities helps you map your current work to Scrum Master duties.

Salary questions

Know your range before the HR round. AmbitionBox puts the average Scrum Master salary in India at ₹17.4 lakh a year at around 5 years of experience, based on 20.9k salaries (AmbitionBox, October 2026). Your number depends on your experience, city and the role.

Your resume backs your answers

Interviewers often pick questions from your resume. Make sure every bullet is one you can explain in detail. Our Scrum Master resume guide shows how to write outcome-based bullets, and our Scrum Master jobs guide covers where to apply.

14. How Brolly Academy helps

Short answer: Brolly Academy's 1-week Scrum Master course ends with two days of exam preparation, role plays, mock interviews, resume building and placement guidance, so you practise these questions before the real interview.

Our Scrum Master training in Hyderabad runs in the classroom at Nizampet, near JNTU Metro Station, or live online:

Placement support includes interview question banks, mock interviews, ATS-friendly resumes, aptitude preparation and interview scheduling. The online course includes mock interviews and 50+ sample resumes. Fees are ₹5,000 for the video course, ₹10,500 for live online and ₹15,000 for classroom training, with EMI available. CSM, PSM and SAFe exam fees are separate. Attend a free demo class before you enrol.

Frequently asked questions