July flash sale
Scenario questions expose a weakness that definition-based preparation hides. Knowing the purpose of the Daily Scrum does not automatically tell you what to do when a manager uses it to assign tasks. A strong answer has to diagnose the situation, protect Scrum accountabilities and adapt without pretending there is one universal script.
Mock interviews are included in the Expert Scrum Master career packages. You can also use the framework below with a peer, trainer or recording tool.
Use C-A-R-E, not a memorized speech
- Context: clarify what is happening, who is affected and what evidence is available.
- Accountabilities: name the relevant Scrum purpose, boundary or ownership without turning the answer into a lecture.
- Response: explain the next conversation or experiment, including alternatives.
- Evidence: state what you would observe to decide whether the response helped.
The framework keeps an answer grounded while leaving room for judgment. It also prevents a common mistake: jumping from a short scenario to a confident diagnosis without asking what is missing.
Facilitation and Scrum event scenarios
1. The Daily Scrum has become a status report to the manager. What do you do?
Clarify whether Developers still use the event to inspect progress toward the Sprint Goal and adapt their plan. Speak with the team rather than removing the manager by decree. Explore what information the manager needs and create another route for that need. Then observe whether Developers regain ownership of the plan.
2. Retrospectives produce the same action every Sprint.
Inspect why the action does not move: unclear ownership, no capacity, a dependency outside the team, low belief or an action that treats a symptom. Narrow the experiment, make review visible and involve the person able to change the constraint. Success is not a new sticky note; it is learning about the system.
3. Sprint Planning regularly runs over time.
Look before facilitating harder. Work may be poorly understood, the Product Goal may be weak, capacity may be unstable or the group may be doing refinement inside planning. Bring evidence, involve the Product Owner and Developers, and test an upstream improvement.
Conflict, coaching and ownership
4. Two senior Developers openly disagree and the team goes silent.
Do not decide who is right from the interview prompt. Protect a workable conversation, surface observations and impact, and agree on how the technical decision will be made. If behaviour becomes unsafe, address that boundary directly. Follow up on both the decision and the team's ability to disagree.
5. The team expects the Scrum Master to solve every impediment.
Make the pattern discussable without withdrawing support suddenly. Separate impediments by control and influence, ask who is best placed to act, and coach ownership. Take direct action where organizational access is genuinely required, while keeping the team involved.
6. A Product Owner rejects coaching and asks you to focus on meetings.
Respect the person's right not to be coached. Explore the working agreement, share observable effects and offer facilitation, teaching or mentoring where appropriate. Coaching without agreement is not coaching.
Metrics and delivery questions
7. Management asks for individual velocity.
Clarify the decision they are trying to make. Explain why velocity is a team planning aid and why individual comparison can distort behaviour. Offer evidence closer to the concern, such as work item age, blocked time, quality signals or progress toward outcomes.
8. Velocity falls for three Sprints. Is the team underperforming?
A number does not establish the cause. Ask about team changes, work type, estimation practices, quality issues and Sprint Goals. Use the trend as a reason to inspect, not a verdict. State which additional evidence you would seek.
9. Stakeholders want a fixed date although scope is unclear.
Acknowledge the decision need. Work with the Product Owner and Developers to separate fixed constraints from assumptions, identify a smallest valuable outcome, expose uncertainty and create review points. Avoid promising certainty that the evidence cannot support.
AI questions are now judgment questions
10. Would you paste retrospective notes into an AI assistant?
Not by default. Check organizational policy, data classification, consent, contractual limits and tool settings. Prefer synthetic or de-identified data for practice. Even with approval, review the output and do not let a model label people or decide what the team feels.
11. AI produces an excellent retrospective plan. Do you use it?
Treat it as an option. Check whether the design fits the team's context, safety, energy and purpose. Modify or reject it as needed. The Scrum Master remains accountable for facilitation choices.
12. How would you prove that AI improved your work?
Choose a bounded task, establish a baseline and inspect both efficiency and quality. For meeting summaries, measure correction effort and missed actions, not only time saved. Include privacy, trust and error risk in the evaluation.
Questions to ask the interviewer
- What problems do Scrum Masters here spend most of their time helping with?
- How are Scrum Masters supported when an impediment crosses organizational boundaries?
- Which outcomes would make the first six months successful?
- How does the organization use team and flow metrics?
- What is the policy for AI tools and team data?
Run a useful mock interview
- Answer eight questions without notes and record the session.
- Limit the first answer to two minutes.
- Mark unsupported assumptions and places where you skipped diagnosis.
- Replace abstract claims with one truthful example.
- Repeat the same questions in a different order two days later.
A good answer does not make the Scrum Master the hero of every story. It shows how you help people inspect reality, exercise their accountabilities and improve the system.
Use the course package comparison to choose a pathway that includes individual mock interviews and the certification depth needed for your target roles.
