Top 4 Scrum master Interview Questions
Browse 4 real-world technical and behavioral interview questions about Scrum master. Review scenarios, edge cases, and architectural best practices.
How do you run a retrospective that actually changes something, and what do you do when the team has stopped engaging with them?
A retrospective changes something when it ends with one owned improvement that enters the next Sprint Backlog as work. Disengagement is nearly always evidence that previous actions went nowhere, so the fix is to close the loop on old commitments before redesigning the format.
Your Product Owner says everything in the sprint is top priority and refuses to rank the backlog. How do you handle it?
Do not argue about priority in the abstract; make the cost of not choosing visible by showing capacity against the ask, then force a decision through a mechanism that requires ordering rather than asking for agreement.
The team has missed its Sprint Goal four sprints in a row. What do you do as Scrum Master?
Treat four misses as data about the system rather than a verdict on the team: find out whether the goal is set by the team or handed to it, whether unplanned work arrives mid-sprint, and whether done is being deferred, then fix the cause you find instead of shrinking the commitment.
The engineering manager runs your team's Sprint Planning and assigns every item to a named person up front. The team says it works fine. What do you do?
Do not open with the Scrum Guide. Show what pre-assignment costs in flow terms, since assigning everyone an item on day one puts the whole Sprint in progress at once and stretches cycle time. Then find out what the manager needs from it and offer a mechanism that meets that need without the assignment.