5 exercises — choose the best-structured answer to common Scrum Master interview questions. Focus on servant-leadership vocabulary, Scrum framework precision, and process coaching language.
Structure for Scrum Master interview answers
Diagnose first: ask or state "why" before jumping to solutions
Name the technique: use specific Scrum/agile terminology (servant-leader, sprint goal, Definition of Ready)
Show the feedback loop: measure → reflect → adjust
Demonstrate ownership: show you follow through, never wait passively
0 / 5 completed
1 / 5
The interviewer asks: "What is the difference between a Scrum Master and a Project Manager?" Which answer is most accurate and professionally articulated?
Option A is the strongest: it defines both roles with specific responsibilities, uses the key Scrum framework term (servant-leader), and anchors the comparison on the most meaningful differentiator — authority over work. Option D makes a good structural point about the PO/SM split of ownership, and "SM owns the process" is a useful formulation — but the claim that "PO owns the product" is an oversimplification of shared ownership. Option C is accurate but only describes the SM side without genuinely contrasting with PM. Option B is informal and dismissive ("just facilitates meetings"). Tip: in Scrum Master interviews, always lead with "servant-leader" — it frames your authority model and philosophy before the details.
2 / 5
The interviewer asks: "How do you facilitate a retrospective when the team seems disengaged?" Choose the best answer.
Option A is the best structured answer: it starts by diagnosing root causes (three specific possibilities), proposes a concrete format change with named examples (silent writing, 4Ls), limits scope for focus (one or two outcomes), and addresses the most common root cause of disengagement — no visible follow-through. Option D correctly identifies the "retro outcomes not actioned" root cause and proposes anonymous input — these are both good insights. Option C names formats (Start/Stop/Continue, 4Ls) and mentions action items — good specifics. Option B is too vague and informal. For SM facilitation questions: diagnose the cause first, then name a specific technique, then show the feedback loop that makes the technique work.
3 / 5
The interviewer asks: "How do you handle an impediment that is outside your control?" Which answer best demonstrates Scrum Master maturity?
Option A is the strongest: it covers every dimension — making it visible (transparency), escalating to the right authority, describing impact, setting a resolution timeline, persistent follow-up, workaround if needed, and documentation as a risk. The phrase "persistently but professionally" calibrates the tone correctly for a leadership context. The explicit statement "I never wait passively" shows ownership mindset. Option C is strong on the communication side and mentions replanning — a practical operational detail. Option D describes a system (impediment board, standup, escalation, tracking) which is good process. Option B is too brief and doesn't mention impact communication or the passive/active distinction. Key: impediment management is about transparency + persistence + workarounds — never passive waiting.
4 / 5
The interviewer asks: "How do you help a team improve their estimation accuracy?" Choose the most practical and structured answer.
Option A is the most complete: it covers retrospective feedback loop (estimated vs actual velocity), story decomposition, making assumptions explicit in refinement, names specific estimation techniques (t-shirt sizing, planning poker), and adds the expertise-level insight about story points vs raw time — a conceptual confusion that Scrum Masters regularly need to address. Option B is solid and mentions the Definition of Ready — an underappreciated but important concept. Option C is accurate but doesn't distinguish estimation techniques or the story points/time confusion. Option D is accurate but brief. For coaching questions: show the feedback loop (measure → reflect → adjust), name the technique, and add the non-obvious insight that separates experienced SMs.
5 / 5
The interviewer asks: "How do you protect the team's focus during a sprint?" Which answer best demonstrates servant-leadership?
Option A is the best: it provides a practical mechanism for saying no (sprint goal as a filter), names the correct person to redirect requests to (PO), uses data to make the cost invisible visible (unplanned work correlates with missed sprint goals), and adds the actionable meeting management tactic. The data use is a distinctive detail — it turns the "protection" argument from a process rule into an evidence-based conversation. Option D is good structure but lacks specifics. Option C is correct and mentions the stakeholder communication dimension, but doesn't mention the cost-visibility tactic. Option B is technically fine but uses "I tell stakeholders" which sounds directive rather than facilitative — a minor register issue for a SM role. Key principle: protection should be evidence-based and transparent, not just rule-enforcement.