So, you’ve got a Scrum Master interview coming up. Maybe it’s your first one. Maybe you’ve been in the Agile world for years and just want to make sure you’re sharp. Either way, you’re in the right place.
This guide covers the most important Scrum Master interview questions — the ones that actually come up in real interviews at companies like Infosys, TCS, Capgemini, Wipro, startups, and global product firms. We’ve broken them down by difficulty level, added honest, conversational answers, and sprinkled in tips that go beyond textbook definitions.
Let’s get into it.
WHY SCRUM MASTER INTERVIEW QUESTIONS MATTER MORE THAN YOU THINK
Here’s the thing about Scrum Master interviews — they’re not like developer interviews. You won’t be asked to reverse a binary tree. Instead, interviewers want to understand how you think, how you handle team dysfunction, and whether you actually live the Agile values or just memorize the Scrum Guide.
That’s what makes Scrum interview questions and answers so nuanced. Two people can give technically correct answers. Only one of them will get the job — the one who sounds like they’ve actually stood in a retrospective and navigated a messy sprint.
Keep that in mind as you go through this list.
SECTION 1: BASIC SCRUM MASTER INTERVIEW QUESTIONS
These are the foundation. If you’re interviewing for a junior or entry-level Scrum Master role, expect a heavy focus here.
- What is Scrum?
Scrum is an Agile framework used to develop, deliver, and sustain complex products. It’s built on three pillars — transparency, inspection, and adaptation — and five core values: commitment, courage, focus, openness, and respect.
What to add: Don’t just recite the definition. Mention that Scrum is lightweight and intentionally incomplete — it’s a framework, not a methodology. That subtle distinction impresses interviewers.
- What does a Scrum Master do?
A Scrum Master serves the Scrum Team, the Product Owner, and the organization. They’re not a project manager. They don’t assign tasks. Their job is to remove impediments, coach the team on Agile practices, facilitate Scrum events, and protect the team’s focus.
What to add: Emphasize the servant-leader aspect. Many candidates say “facilitator” and stop there. Go deeper — a great Scrum Master enables self-management and continuous improvement.
- What are the three roles in Scrum?
The three accountabilities in Scrum are:
- Scrum Master
- Product Owner
- Developers (the rest of the Scrum Team)
Note: The 2020 Scrum Guide replaced “Development Team” with “Developers” and dropped the term “roles” in favor of “accountabilities.” Mentioning this shows you’ve actually read the latest guide.
- What are the five Scrum events?
- Sprint (the container for all other events)
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
Pro tip: Don’t forget that the Sprint itself is an event. Many candidates list four events and forget the Sprint wrapper.
- What are Scrum artifacts?
- Product Backlog
- Sprint Backlog
- Increment
Each artifact has a commitment: the Product Goal, the Sprint Goal, and the Definition of Done, respectively. This was introduced in the 2020 Scrum Guide.
- What is the Definition of Done?
The Definition of Done (DoD) is a formal description of the state of the Increment when it meets the quality standards required for the product. If an item doesn’t meet the DoD, it cannot be included in the Sprint Review.
What to add: The DoD creates transparency and shared understanding. It’s not a wish list — it’s a commitment.
- What is a Sprint?
A Sprint is a time-boxed iteration, typically one to four weeks, during which a usable and potentially releasable Increment is created. Sprints have consistent durations throughout the development effort.
- What is Sprint Planning?
Sprint Planning initiates the Sprint. The entire Scrum Team collaborates to define the Sprint Goal and select the Product Backlog items they’ll work on. The Developers then plan how they’ll deliver those items.
Time-box: Eight hours for a one-month Sprint.
- What is a Daily Scrum?
A 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It’s not a status meeting — it’s for the team’s coordination, not management’s reporting.
- What is the Sprint Review?
The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog. Stakeholders are invited. It’s a working session, not a demo presentation.
Time-box: Four hours for a one-month Sprint.
- What is a Sprint Retrospective?
The Retrospective is the team’s opportunity to inspect how the last Sprint went — people, relationships, process, and tools — and create a plan for improvements. It’s arguably the most powerful event in Scrum.
Time-box: Three hours for a one-month Sprint.
- What is the Product Backlog?
An emergent, ordered list of everything that is known to be needed in the product. It’s never complete and is constantly refined. The Product Owner is accountable for it.
- What is Backlog Refinement?
Backlog Refinement (also called Backlog Grooming) is the act of adding detail, estimates, and order to Product Backlog items. It’s ongoing and typically takes no more than 10% of the team’s capacity.
- Can a Scrum Master also be a Developer on the same team?
Technically yes, but it’s not recommended. The Scrum Guide says this combination is often problematic. As a Developer, you have deliverables; as a Scrum Master, you serve the team. These two roles can create conflicts of interest, especially when impediments involve the team’s workload.
- What is the Sprint Goal?
The Sprint Goal is a single objective set during Sprint Planning. It gives the team flexibility while providing focus. If work becomes obsolete, the Developers can negotiate scope with the Product Owner without canceling the Sprint — as long as the Sprint Goal is still achievable.
SECTION 2: INTERMEDIATE SCRUM MASTER INTERVIEW QUESTIONS
These Scrum interview questions and answers go deeper. They test your understanding of real-world application.
- How do you handle a team member who consistently misses the Daily Scrum?
Start by understanding why. Is the time inconvenient? Do they feel the meeting is unproductive? Is there a personal conflict? As a Scrum Master, you don’t mandate attendance through authority — you help the team understand the value of the event and solve the underlying issue together.
If it’s a behavioral issue, address it in a 1:1 first before raising it with the broader team.
- What’s the difference between a Scrum Master and a Project Manager?
A Project Manager typically owns the project plan, manages resources, tracks timelines, and reports to stakeholders. They have authority.
A Scrum Master has no formal authority. They coach the team, remove impediments, and facilitate — but they don’t manage people or dictate work. If a Scrum Master starts assigning tasks or doing performance reviews, they’ve crossed into Project Manager territory.
- What is velocity and how do you use it?
Velocity is the amount of work a Scrum Team completes in a Sprint, measured in story points or similar units. It’s used for forecasting, not for measuring team performance or comparing teams.
Common mistake to avoid: Using velocity as a KPI to push teams to “go faster.” That destroys trust and inflates estimates.
- What are story points?
Story points are a unit of measure for estimating the complexity, effort, and risk of a Product Backlog item. They’re relative, not absolute. A 5-point story isn’t five hours of work — it means it’s roughly twice as complex as a 2-point story.
- What is Planning Poker?
Planning Poker is a consensus-based estimation technique where team members simultaneously reveal their estimates using numbered cards (usually following the Fibonacci sequence). If estimates differ, the team discusses until they reach consensus. It prevents anchoring bias.
- How do you handle a conflict between the Product Owner and the Development Team?
First, listen to both sides separately to understand the root cause. Then bring them together and facilitate a conversation focused on the Sprint Goal and the product’s needs rather than individual positions. Your job is to create a safe space for dialogue, not to take sides.
- What is the difference between Scrum and Kanban?
Scrum uses time-boxed Sprints, fixed roles, and specific events. Work is pulled into Sprints during Sprint Planning.
Kanban is a continuous flow system with no Sprints. Work is pulled as capacity becomes available. There are no prescribed roles or events.
Many teams use both — this is called Scrumban.
- What is the difference between Agile and Scrum?
Agile is a mindset, a set of values and principles described in the Agile Manifesto. Scrum is one framework that implements those values. Not all Agile teams use Scrum, and not all Scrum teams are truly Agile.
- What is a burn-down chart?
A burn-down chart tracks the remaining work in a Sprint or release over time. The Y-axis is work remaining; the X-axis is time. Ideally, the line trends downward to zero by the Sprint’s end.
It’s a tool for the team, not for management to monitor the team.
- What is a burn-up chart?
A burn-up chart shows work completed over time, with a separate line for total scope. Unlike burn-down charts, burn-up charts make scope changes visible — you can see when new work was added.
- What is an impediment? Give an example.
An impediment is anything that slows the team down or blocks their progress. It could be a missing software license, unclear requirements, a dependency on another team, or an organizational policy that conflicts with Agile ways of working.
The Scrum Master’s job is to resolve impediments the team can’t resolve themselves.
- What is the “chicken and pig” story in Agile?
It comes from a fable: a pig is committed (it gives its life for bacon), while a chicken is involved (it contributes eggs). In Scrum, the Developers are committed to Sprint work; stakeholders are involved.
Note: The 2020 Scrum Guide dropped this metaphor, but interviewers still ask about it because it illustrates the difference between committed and uninvolved parties.
- What is Technical Debt?
Technical debt is the implied cost of rework caused by choosing a quick, easy solution now instead of a better approach that would take longer. Like financial debt, it accrues interest over time — the longer you ignore it, the more expensive it becomes.
A Scrum Master advocates for addressing technical debt by ensuring it’s visible in the Product Backlog and has space in Sprints.
- How do you handle scope creep in Scrum?
Scope creep is managed through the Product Backlog. Any new requirement goes into the backlog, gets prioritized by the Product Owner, and is considered for future Sprints. Within a Sprint, the scope is protected by the Sprint Goal. Mid-Sprint additions must be discussed with the Product Owner and Developers.
- What is the difference between Sprint Review and Sprint Retrospective?
Sprint Review focuses on the product — what was built, what’s next, and whether the increment meets stakeholder needs.
Sprint Retrospective focuses on the team — how they worked, what went well, what can be improved in terms of process, collaboration, and practices.
They’re often confused. The Review is external-facing; the Retrospective is internal.
SECTION 3: ADVANCED SCRUM MASTER INTERVIEW QUESTIONS
These are the Scrum Master interview questions that separate senior practitioners from those who’ve just read a book.
- How do you scale Scrum across multiple teams?
Frameworks like SAFe (Scaled Agile Framework), LeSS (Large-Scale Scrum), and Nexus are designed for this. Nexus is the official Scrum.org scaling guide and introduces a Nexus Integration Team.
Mention that scaling isn’t just about adding more teams — it’s about managing dependencies, aligning on a shared Product Goal, and ensuring cross-team collaboration doesn’t become bureaucracy.
- What is the Nexus framework?
Nexus is a framework for scaling Scrum to three to nine Scrum Teams working on a single Product Backlog. It introduces a Nexus Integration Team responsible for coordinating integration and addressing cross-team dependencies.
- How do you handle a Scrum Team that’s resistant to change?
This is a coaching challenge. First, acknowledge their resistance as valid — change is hard. Then explore the root cause. Is it past failed initiatives? Lack of psychological safety? Fear of job changes?
Use retrospectives to surface concerns. Introduce changes incrementally. Celebrate small wins. The Scrum Master creates conditions for the team to want to improve, not forces them.
- What is the role of a Scrum Master in organizational change?
A senior Scrum Master doesn’t just serve one team — they help the organization become more Agile. That means coaching leadership, helping remove systemic impediments, and sometimes challenging policies or structures that prevent teams from self-managing.
This is where the “change agent” aspect of the role comes in.
- How do you deal with a Product Owner who doesn’t engage with the team?
This is extremely common. Start with a direct conversation about the impact of low engagement — unclear priorities, wasted Sprint effort, misaligned increments. Offer support: maybe they’re overwhelmed, don’t understand their role, or are buried in other work.
Escalate to leadership only if direct coaching fails and the issue seriously affects the team’s ability to deliver.
- What is an Agile Release Train (ART)?
Used in SAFe, an ART is a long-lived team of Agile teams (typically 50-125 people) that plan, commit, and execute together in a Program Increment (PI). PIs typically run 8-12 weeks.
Not all interviewers will ask about SAFe — but large enterprise roles almost always do.
- What is a Program Increment (PI) Planning?
PI Planning is a cadenced event in SAFe where all teams on an Agile Release Train meet face-to-face (or virtually) to align on a shared vision and plan work for the next 8-12 weeks. It’s considered the heartbeat of SAFe.
- What is empiricism in Scrum?
Empiricism means making decisions based on what is known, through observation and experimentation. Scrum’s three pillars — transparency, inspection, and adaptation — are all expressions of empirical process control.
This is a key philosophical question. If you can explain why Scrum works rather than just how it works, you stand out.
- What is the Agile Manifesto?
Published in 2001 by 17 software practitioners, the Agile Manifesto outlines four values:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
The right side of each statement still has value — the left side is valued more.
- How do you measure team health?
There’s no single Scrum metric for this, which is intentional. Common approaches include:
- Team happiness or energy metrics (1-10 at retrospectives)
- Qualitative retrospective feedback
- Squad health checks (Spotify model)
- Cycle time and lead time trends
- Frequency and quality of collaboration
A healthy team is self-managing, improving, and psychologically safe. Metrics support that judgment; they don’t replace it.
- What is psychological safety and why does it matter in Scrum?
Psychological safety — coined by Amy Edmondson — is the belief that you won’t be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes. Without it, retrospectives become performances. Daily Scrums become status meetings. Teams hide problems until it’s too late.
A great Scrum Master actively cultivates psychological safety.
- What would you do if the Sprint Goal is at risk mid-Sprint?
Raise it transparently in the Daily Scrum. Work with Developers to understand the root cause. If necessary, collaborate with the Product Owner to re-negotiate scope without abandoning the Sprint Goal. A Sprint cancellation is a last resort and only the Product Owner can cancel a Sprint.
- What is the Scrum Master’s role during Sprint Planning?
The Scrum Master ensures the event happens, is time-boxed, and is productive. They don’t decide what goes into the Sprint — that’s the Product Owner and Developers. They might facilitate discussions, help the team decompose stories, or help clarify the Sprint Goal.
- What is the difference between coaching and mentoring in an Agile context?
Coaching is asking powerful questions to help someone discover their own answers. Mentoring is sharing your experience and guidance directly.
A Scrum Master does both — coaching teams on self-management and mentoring individuals who are new to Agile practices.
- How do you handle a team that skips retrospectives?
Find out why. Common reasons: they feel nothing changes, they don’t see the value, or they’re too busy. Show them examples of how past retrospectives led to concrete improvements. Co-create a retro format that’s actually engaging — not just “what went well / what didn’t.”
If senior leadership is the reason (too busy, too short-sighted), that’s an organizational impediment you need to escalate.
SECTION 4: SITUATIONAL AND BEHAVIORAL SCRUM MASTER INTERVIEW QUESTIONS
These Scrum interview questions and answers test your real-world judgment. Use the STAR method: Situation, Task, Action, Result.
- Tell me about a time you removed a significant impediment.
Structure your answer: What was the impediment? Why couldn’t the team solve it themselves? What did you do? What was the outcome?
Strong answers involve navigating organizational politics, negotiating with other departments, or escalating appropriately without creating conflict.
- Describe a difficult retrospective you facilitated.
Look for answers that show the ability to handle tension, surface hidden issues, and maintain psychological safety. Weak answers describe a smooth retro. Strong answers describe one where trust was low, conflict was real, and the Scrum Master’s facilitation made the difference.
- Have you ever disagreed with a Product Owner? How did you handle it?
This tests courage and communication. A good answer shows you raised the concern professionally, presented data or Scrum principles to support your position, and ultimately respected the Product Owner’s accountability while making your perspective clear.
- How do you onboard a new team to Scrum?
Don’t just run a training session. Start with a kickoff to understand the team’s context and pain points. Introduce Scrum incrementally — don’t overwhelm them with events on Day 1. Run a few Sprints, reflect at retrospectives, and adjust. Coaching is more effective than classroom teaching.
- What do you do when a senior stakeholder starts attending Daily Scrums and asking the team for status updates?
This is a common scenario. Politely but firmly explain the purpose of the Daily Scrum — it’s for Developers, not stakeholders. Offer the stakeholder an alternative: attend the Sprint Review, get a brief post-standup update from the Product Owner, or view a live dashboard.
If they refuse, escalate as an impediment to leadership. The Daily Scrum must remain protected.
- What is your approach to continuous improvement?
A strong Scrum Master models what they preach. Talk about how you reflect on your own facilitation skills, stay current with the latest Scrum Guide updates, participate in Agile communities, pursue certifications (CSM, PSM, SAFe), and apply retrospective thinking to your own work.
- How do you handle a team where two members have a personal conflict?
Start 1:1, not in a group setting. Understand both perspectives. Don’t take sides. Help each person understand the other’s point of view. If needed, bring them together in a safe, neutral setting with agreed-upon ground rules.
Only escalate to HR or management if the conflict is creating a hostile environment or if direct coaching has failed.
- What would you do if you discovered the team was gaming velocity?
This is a trust and transparency issue. Don’t shame the team publicly. Explore why they’re inflating estimates — fear of management pressure, unrealistic commitments, or previous punishment for “missing” targets.
Address the root cause. Educate on the real purpose of velocity. And escalate the systemic issue (like management using velocity as a KPI) to leadership.
SECTION 5: CERTIFICATION-RELATED SCRUM MASTER INTERVIEW QUESTIONS
- What is the difference between CSM and PSM?
CSM (Certified Scrum Master) is offered by Scrum Alliance and requires attending a two-day training before taking the exam. PSM (Professional Scrum Master) is offered by Scrum.org and has no mandatory training — just a rigorous exam. PSM I, II, and III go from foundational to advanced practitioner to expert level.
Neither is universally superior — the PSM is generally considered harder to pass; the CSM is more commonly recognized in job postings.
- Is certification enough to become a Scrum Master?
No — and you should say this confidently. Certification validates knowledge. Experience builds skill. A great Scrum Master combines both with genuine people skills, emotional intelligence, and the courage to coach teams even when it’s uncomfortable.
SECTION 6: QUICK-FIRE SCRUM MASTER INTERVIEW QUESTIONS
These are short questions that test breadth of knowledge. Answer them concisely.
- What is the maximum Sprint length?
One month (four weeks). - Who can cancel a Sprint?
Only the Product Owner. - What happens to incomplete Sprint Backlog items at the end of a Sprint?
They return to the Product Backlog for reprioritization. - Who owns the Product Backlog?
The Product Owner is accountable for it. - Can the Scrum Master be the Product Owner?
Not recommended. These are two distinct accountabilities with potential conflicts of interest. - What is a Scrum of Scrums?
A technique for coordinating multiple Scrum Teams. Representatives from each team meet regularly to sync on progress, dependencies, and impediments. - What is the Scrum Guide?
The official guide to Scrum, co-created by Ken Schwaber and Jeff Sutherland — the inventors of Scrum. The current version is from 2020 and is available free at scrumguides.org. - What does “potentially shippable product increment” mean?
Each Sprint should produce an Increment that could theoretically be released to users, even if the organization chooses not to release it. - What is an Epic?
An Epic is a large body of work that can be broken down into multiple user stories. It’s not a Scrum term — it comes from SAFe and other scaling frameworks, but is widely used in practice. - What is a User Story?
A user story is a short, simple description of a feature from the perspective of the user: “As a [user], I want [goal] so that [reason].” It’s not a Scrum artifact, but widely used in Agile teams to describe backlog items.
SECTION 7: TIPS TO CRACK SCRUM MASTER INTERVIEWS
Read the 2020 Scrum Guide Cover to Cover
The latest guide dropped several terms (Development Team, Sprint 0, velocity as a metric) and introduced new concepts (commitments for artifacts, the term “Developers”). Interviewers will catch you using outdated terminology.
Show You Understand Servant Leadership
Every answer should reflect that you serve the team rather than manage it. Phrases like “I would coach the team,” “I would facilitate a conversation,” and “I would remove that impediment” signal you understand the role.
Use Real Examples
Even if you’re entry-level, draw from project management experience, volunteer coordination, or academic team projects. Show that you understand how real teams work.
Know Your Metrics — And Their Limits
Velocity, burn-down, cycle time, lead time — know what they measure and, more importantly, what they don’t. Never use velocity to measure team performance or compare teams.
Prepare for Scenario-Based Questions
These Scrum Master interview questions are where candidates either shine or fall flat. Practice STAR-format answers for at least five real or hypothetical scenarios: handling a disengaged Product Owner, managing a conflict, removing an impediment, dealing with resistance to Scrum, and facilitating a difficult retrospective.
Understand the Agile Mindset
Scrum is a framework. Agile is a mindset. Interviewers at mature Agile companies want to know you understand the difference. If you approach Scrum as a rigid checklist, you’ll struggle in interviews at companies that truly live Agile values.
FINAL THOUGHTS ON SCRUM MASTER INTERVIEW QUESTIONS
There are no perfect answers to Scrum interview questions and answers — and that’s actually the point. Scrum is empirical. It’s built for complex, unpredictable environments where rigid scripts fail. The best Scrum Masters are curious, humble, and courageous. They serve without being servile. They coach without controlling. They challenge without being combative.
If your answers reflect that mindset, you’ll walk out of most interviews with a strong impression — regardless of whether you could recite every time-box from memory.
Good luck. Trust the process. Inspect and adapt.
FREQUENTLY ASKED QUESTIONS (FAQ)
Q: How many Scrum Master interview questions should I prepare?
Aim for deep preparation on 30-40 core questions rather than surface-level familiarity with 100. Behavioral and situational questions matter more than rote definitions at the mid-to-senior level.
Q: What is the most common Scrum interview question asked?
“What is the difference between a Scrum Master and a Project Manager?” is the most universally asked Scrum Master interview question. Nail your answer here — it sets the tone for everything that follows.
Q: Are Scrum Master interview questions different for freshers vs experienced candidates?
Yes. Freshers face more definition-based Scrum Master interview questions. Experienced candidates get scenario and behavioral questions testing judgment, coaching ability, and conflict resolution.
Q: What certifications help in Scrum Master interviews?
CSM (Scrum Alliance), PSM I/II/III (Scrum.org), SAFe Scrum Master, and PMI-ACP are the most recognized. PSM II and III carry significant weight for senior roles.
Q: Can I become a Scrum Master without IT experience?
Yes. Scrum is used in marketing, HR, education, healthcare, and beyond. Non-IT Scrum Master roles exist and are growing. Focus on the framework, coaching skills, and facilitation experience.