Scrum Master
When have you decided that Scrum was not the right fit, and adapted to something else like Kanban?
What the interviewer is looking for
- This question tests scrum & agile practice. Understands the purpose behind roles, events and artefacts, and adapts practices like Scrum or Kanban pragmatically to the team's context.
- Strong answers: Explains why the work pattern did not fit, made the change with the team, kept the useful principles, and measured the result.
- Likely follow-up: What did the team lose by changing, if anything?
Another way it may be asked: Have you ever worked with a team where sprints just did not suit the work? What did you change to?
A structure to follow: Answer, explain, example, limits
- Step 1
Answer
Give your direct answer in the first sentence so the interviewer knows where you are going.
- Step 2
Explain
Say how it works or why you would do it that way, in plain words before jargon.
- Step 3
Example
Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.
- Step 4
Limits
Say when your approach would not be the right one. It shows judgement.
This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.
Common slips
- Reciting a definition without showing you have applied it.
- Using terms you cannot explain if asked a level deeper.
- Claiming experience beyond what you can discuss in detail.
How to practise it
Say the answer in 90 seconds, then answer the follow-up as if it were a new question.
Related questions
- Can you explain the difference between the product owner's role and the scrum master's role?
- In your own words, what is the purpose of a retrospective, and how would you run one for a team that finds them boring?
- A developer tells you they are blocked waiting on another team. What would you do today?
- Your daily stand-up has turned into a long status meeting for the manager. How would you fix it?
- Which delivery measures do you track, like cycle time or throughput, and how do you use them without people gaming them?