Preparing for a Scrum Master interview requires a solid understanding of the framework, its practices, and real-world application. This guide covers 30 essential interview questions spanning basic to advanced levels, designed to help candidates at all experience stages—from freshers to those with 3-6 years of experience—succeed in their interviews.
Basic Level Questions (Foundation Knowledge)
1. What is Scrum and how does it work?
Answer: Scrum is an iterative and incremental framework used for managing product development and project delivery. It works by breaking work into fixed time periods called Sprints (typically 1-4 weeks), during which a team commits to completing a set of prioritized tasks. The framework emphasizes continuous feedback, collaboration, and regular inspection to deliver value incrementally. Scrum operates on empirical process control, meaning decisions are based on observation, transparency, and adaptation rather than predictions alone.
2. What are the three main accountabilities in Scrum?
Answer: The three main accountabilities in Scrum are:
- Product Owner: Responsible for managing the Product Backlog, prioritizing items based on business value, and ensuring the team understands what needs to be built.
- Development Team: Responsible for creating the product increment and determining how to accomplish the work within each Sprint.
- Scrum Master: Responsible for facilitating Scrum events, removing impediments, and coaching the team on Scrum practices and values.
3. What are the five Scrum values?
Answer: The five Scrum values are commitment, focus, openness, respect, and courage. These values drive Scrum’s success and distinguish it from traditional project management approaches. Commitment refers to team dedication to sprint goals; focus means concentrating on sprint work; openness involves transparent communication; respect acknowledges team members’ skills and perspectives; and courage enables teams to face challenges and experiment with new ideas.
4. What is a Sprint in Scrum?
Answer: A Sprint is a fixed time-boxed iteration, typically lasting 1-4 weeks, during which the Scrum team works to complete a set of prioritized Product Backlog items. The Sprint has a clear beginning and end, with a defined Sprint goal. All Scrum events (planning, daily standups, reviews, and retrospectives) occur within a Sprint, and at the end, the team delivers a potentially releasable product increment.
5. What is the Product Backlog?
Answer: The Product Backlog is an ordered list of features, enhancements, bug fixes, and other work items that need to be completed for the product. It serves as the single source of truth for product requirements and is maintained by the Product Owner. Items are prioritized based on business value, risks, and dependencies. The Product Backlog is visible and accessible to the entire organization, though only the Product Owner can modify it.
6. What is the Sprint Backlog?
Answer: The Sprint Backlog is a detailed list of tasks that the Scrum team commits to completing during a specific Sprint. It represents the team’s plan for achieving the Sprint goal and includes user stories broken down into actionable tasks. Unlike the Product Backlog, the Sprint Backlog is visible primarily to the Scrum team and is updated daily as work progresses. It provides a detailed view of what the team will deliver within the sprint timeframe.
7. What is the Product Increment?
Answer: The Product Increment is the sum of all completed Product Backlog items at the end of a Sprint. It represents a potentially usable and deliverable piece of the product that meets the Definition of Done. The Product Increment must be of high quality and contribute to the overall product vision. Each Sprint produces an additive Product Increment that builds upon previous increments.
8. What are the five Scrum events?
Answer: The five Scrum events are:
- Sprint Planning: Held at the beginning of each Sprint to define the Sprint goal and select items from the Product Backlog.
- Daily Standup: A 15-minute daily meeting where the team synchronizes work and identifies impediments.
- Sprint Review: Held at the end of the Sprint to inspect the Product Increment and gather stakeholder feedback.
- Sprint Retrospective: A meeting where the team reflects on their process and identifies improvements for the next Sprint.
- Backlog Refinement: An ongoing activity where the team clarifies and prepares Product Backlog items for upcoming Sprints.
9. What is the ideal size of a Scrum team?
Answer: The ideal Scrum team size is 3 to 9 members, excluding the Scrum Master and Product Owner. This range allows for effective communication and flexibility while ensuring the team has sufficient skills to complete tasks efficiently. Teams smaller than three may lack the necessary skills and diversity, while teams larger than nine can face communication challenges and become difficult to coordinate.
10. What is the Definition of Done in Scrum?
Answer: The Definition of Done is a shared understanding of what it means for work to be complete. It includes quality standards, testing requirements, documentation needs, and any other criteria that must be met before a Product Backlog item is considered finished. The Definition of Done ensures consistent quality and prevents incomplete work from being included in the Product Increment. It is reviewed during Sprint Planning and may evolve over time.
Intermediate Level Questions (Practical Application)
11. What is Sprint Planning and how should it be conducted?
Answer: Sprint Planning is a time-boxed meeting held at the beginning of each Sprint where the Product Owner and Development Team collaborate to define the Sprint goal and select items from the Product Backlog. During this meeting, the team discusses the sprint goal, aligns it with product priorities, and estimates workload to ensure selected items fit within the sprint timeframe. The team then breaks items into actionable tasks and reviews the Definition of Done. The outcome is a clear understanding of the work ahead and shared commitment to the Sprint goal, with the team leaving with a realistic sprint plan.
12. How do you prioritize items in the Product Backlog?
Answer: Product Backlog items are prioritized based on business value, risk, dependencies, and stakeholder feedback. The Product Owner works with stakeholders and the Development Team to understand the relative importance of each item. Items with higher business value or those that unblock other work typically receive higher priority. Regular backlog refinement sessions help ensure that high-priority items are detailed and ready for upcoming Sprints, while lower-priority items may remain less detailed until they approach the top of the backlog.
13. What is the role of a Scrum Master?
Answer: A Scrum Master is a servant-leader who facilitates the Scrum framework’s adoption and ensures the team follows Scrum practices. Key responsibilities include facilitating Scrum events, removing impediments that block the team’s progress, coaching team members on Scrum values and practices, promoting self-organization, and helping the organization understand and embrace Scrum. The Scrum Master does not manage the team but instead supports them in delivering value and maintaining a sustainable pace.
14. How do you handle impediments in Scrum?
Answer: Impediments are obstacles that prevent the team from making progress. To handle them, the Scrum Master should first identify and understand the impediment through team discussions or Daily Standups. Then, the Scrum Master works to remove or mitigate the impediment by coordinating with relevant stakeholders, escalating when necessary, and finding creative solutions. Examples of impediments include missing resources, unclear requirements, technical blockers, or organizational obstacles. The key is to resolve them quickly to maintain team momentum and productivity.
15. What is a Daily Standup and what should it cover?
Answer: A Daily Standup is a 15-minute time-boxed meeting held every day during a Sprint where team members synchronize their work. Each team member typically answers three questions: What did I complete yesterday? What will I complete today? What impediments are blocking my progress? The Daily Standup is not a status report to management but a synchronization meeting to help the team stay aligned, identify issues early, and maintain focus on the Sprint goal.
16. What is the purpose of a Sprint Review?
Answer: A Sprint Review is held at the end of each Sprint to inspect the completed Product Increment and gather feedback from stakeholders. During this meeting, the Development Team demonstrates the work completed during the Sprint, and stakeholders provide feedback on what was delivered. The review helps ensure that the product is moving in the right direction and allows the Product Owner to adjust priorities based on feedback. It is a collaborative event that strengthens the connection between the team and stakeholders.
17. What is the purpose of a Sprint Retrospective?
Answer: A Sprint Retrospective is a meeting held after the Sprint Review where the Scrum team reflects on their process and identifies improvements for future Sprints. The team discusses what went well, what could be improved, and commits to specific actions for the next Sprint. This continuous improvement mindset is central to Scrum and helps teams become more effective, efficient, and collaborative over time. The focus is on process improvement rather than blaming individuals.
18. How do you estimate work in Scrum?
Answer: Estimation in Scrum typically uses Story Points, which represent the relative size and complexity of work rather than exact hours. Common estimation techniques include Planning Poker, where team members independently estimate items and discuss discrepancies until consensus is reached. Other methods include T-shirt sizing (XS, S, M, L, XL), Fibonacci sequences, or ideal hours. The goal is to help the team understand the scope of work and commit to realistic Sprint goals based on their capacity and historical velocity.
19. What is velocity and how is it used?
Answer: Velocity is a measure of how much work (in Story Points) the team completes in a single Sprint. It is calculated by summing the Story Points of all completed items in a Sprint. Velocity helps predict future capacity and allows the team to commit to realistic Sprint goals. By tracking velocity over multiple Sprints, teams can identify trends and make informed decisions about sprint planning. Velocity should be stable over time, though variations can indicate changes in team composition, skill level, or external factors.
20. How do you foster collaboration in a Scrum team?
Answer: Fostering collaboration involves creating an environment where team members feel comfortable sharing ideas, asking questions, and supporting each other. Key practices include holding effective Daily Standups, creating psychological safety, encouraging pair programming or peer reviews, facilitating open communication, and promoting transparency. The Scrum Master can facilitate collaboration by removing obstacles, mediating conflicts, and modeling collaborative behavior. Regular retrospectives also provide opportunities to discuss how the team can work together more effectively.
Advanced Level Questions (Scenario-Based & Strategic)
21. A team’s velocity dropped from 100 Story Points last Sprint to 80 this Sprint. As a Scrum Master, how would you address this with the Product Owner?
Answer: First, investigate the root causes of the drop. Common reasons include team members being absent, unexpected technical challenges, scope creep, or external dependencies. Meet with the team to understand what happened and identify any impediments. Present the findings to the Product Owner objectively, discussing whether the drop is temporary or a pattern. If temporary, explain the contributing factors and assure that normal velocity should resume. If it’s a pattern, work with the team to address systemic issues. Avoid focusing on blame; instead, emphasize measuring value delivery and team health rather than just busyness. Use this as an opportunity to improve planning and forecasting accuracy.
22. How would you handle a situation where a team member consistently misses Daily Standups?
Answer: First, have a private conversation with the team member to understand their perspective and any challenges they face. There may be legitimate scheduling conflicts or other issues affecting their attendance. Work together to find a solution, such as adjusting the standup time or finding alternative ways for them to stay connected. If the issue persists, discuss it with the team and establish team norms around attendance. Frame the Daily Standup as a critical synchronization meeting that benefits everyone, not as a mandatory command. If external factors are preventing attendance, work with management or other stakeholders to address them. Document any agreements and follow up regularly.
23. A stakeholder is pressuring the team to add new features mid-Sprint. How would you handle this?
Answer: Explain to the stakeholder that mid-Sprint changes disrupt the team’s focus and commitment to the Sprint goal, reducing productivity and quality. Propose adding the new feature to the Product Backlog for consideration in future Sprints. If it’s truly urgent, discuss the trade-offs: either descope other items from the current Sprint or push the feature to the next Sprint. Involve the Product Owner in this decision, as they manage the backlog and prioritize work. This situation is an opportunity to educate stakeholders about Scrum principles and the importance of Sprint integrity. Over time, establishing clear boundaries around Sprint changes will improve stakeholder understanding.
24. How do you build trust with your team?
Answer: Trust is the foundation of an effective Scrum Master role. Build trust through transparency by openly communicating decisions, challenges, and feedback. Demonstrate consistency by following through on commitments and maintaining fair, predictable behavior. Show empathy by listening to team members’ concerns and supporting their professional growth. When conflicts arise, handle them fairly and support vulnerability by creating a safe environment for honest conversations. Model integrity by acting according to Scrum values and acknowledging mistakes. Specific actions might include protecting team members from external pressure, advocating for their needs, and recognizing their contributions. Trust is built over time through demonstrated reliability and genuine care for the team.
25. How would you handle a conflict between team members during a Sprint?
Answer: Address conflicts promptly before they escalate. First, meet privately with each person involved to understand their perspective. Listen without judgment and identify the underlying issues. Bring the parties together to discuss the conflict in a respectful manner, focusing on the problem rather than personal attacks. Facilitate a conversation aimed at finding a mutually acceptable solution. If needed, involve HR or management, though most conflicts can be resolved at the team level. After resolution, follow up with the individuals to ensure the conflict is truly resolved. Use this as an opportunity to strengthen team relationships and establish healthy communication norms.
26. Describe how you would help a newly formed Scrum team adopt Scrum practices.
Answer: Start by educating the team on Scrum fundamentals—the framework, events, and values. Explain the rationale behind each practice and how they contribute to success. Conduct the first few Sprints with guidance and hands-on facilitation, being present to explain decisions and answer questions. Create psychological safety by encouraging questions and experimentation. Set realistic expectations; the team won’t be perfect immediately, and that’s normal. Facilitate retrospectives to discuss what’s working and what needs adjustment. Gradually increase the team’s autonomy as they become comfortable with the framework. Provide coaching throughout the adoption journey and celebrate small wins to build momentum and confidence.
27. How do you ensure that Scrum practices are continuously followed and adhered to by the team?
Answer: Consistency comes through coaching, education, and facilitation rather than enforcement. Facilitate all Scrum events consistently and on schedule, demonstrating the importance of time-boxing and structure. Coach the team on Scrum values and principles, explaining the “why” behind practices rather than just the “what.” Observe team behavior and gently redirect when practices drift. Use retrospectives to discuss Scrum adherence—ask the team if current practices are serving them well and what adjustments might help. Measure adoption through metrics like Definition of Done compliance or Sprint commitment accuracy. Promote Scrum throughout the organization by sharing successes and educating stakeholders. Remember that the goal is not blind adherence but thoughtful adoption that maximizes value delivery.
28. How would you handle a situation where the team disagrees with a Product Owner’s prioritization?
Answer: First, ensure the team understands the Product Owner’s reasoning for the prioritization. Ask clarifying questions to understand the business context. The team may have technical insights that affect feasibility; create space for this discussion. Facilitate a conversation between the team and Product Owner focused on trade-offs and constraints. The Product Owner has the authority to prioritize, but effective prioritization considers both business value and technical reality. Help the team articulate their concerns professionally, focusing on impact rather than opinion. After the decision is made, the team should commit to the Sprint plan even if they disagree. Use this as a retrospective topic to improve future prioritization discussions.
29. Tell me about a time you helped create a self-organized team. What did you do?
Answer: Self-organization is central to Scrum. Share a specific example where you gradually transitioned responsibility from yourself to the team. Initially, you might have assigned tasks, but over time you encouraged the team to own task assignments. You supported the team in breaking down user stories independently, making technical decisions collaboratively, and resolving issues without escalating to you. Key actions included asking questions rather than providing answers (“What do you think we should do?”), creating space for the team to experiment and learn from mistakes, removing barriers that prevented autonomy, and celebrating their successes. Emphasize that self-organization develops gradually as the team gains confidence and capability. Share specific metrics showing improved team ownership or faster decision-making.
30. How do you scale Scrum across a large organization or multiple teams?
Answer: Scaling Scrum requires frameworks and practices tailored to your organization’s size. Common scaling frameworks include SAFe (Scaled Agile Framework), Nexus, and Scrum@Scale. These approaches address challenges like managing dependencies between teams, aligning multiple teams toward a common vision, and maintaining Scrum principles at scale. Key practices include establishing clear communication channels between teams, synchronizing planning and review activities across teams, managing shared resources effectively, and maintaining transparent product vision and roadmaps. Be honest about frameworks you’ve personally used and which have worked in your experience. Scaling is complex and context-dependent; tailor your approach to your organization’s specific needs, culture, and constraints rather than forcing a one-size-fits-all solution.
Key Takeaways for Interview Success
When preparing for Scrum Master interviews, focus on demonstrating both conceptual knowledge and practical application. Interviewers value candidates who can explain Scrum principles clearly, share specific examples from their experience, and show a commitment to continuous improvement. Be ready to discuss how you’ve coached teams, resolved conflicts, removed impediments, and fostered collaboration.
Remember that Scrum is fundamentally about delivering value, maintaining team health, and embracing change. Your answers should reflect these priorities. Practice discussing your real-world experiences, but also be prepared to articulate the “why” behind Scrum practices, not just the “what.”
For freshers, focus on understanding foundational concepts and demonstrating eagerness to learn. For those with 1-3 years of experience, emphasize practical application and specific examples. For those with 3-6 years, showcase strategic thinking, scaling experience, and thought leadership on organizational adoption of Scrum practices.
