Scrum Master Job Description

Beware candidates who treat Scrum as a rigid checklist — the best Scrum Masters care about outcomes and team health, not ceremony for its own sake. Look for servant-leadership instincts: do they describe their wins in terms of what the team achieved, or in terms of how strictly they enforced process? Strong candidates can point to specific impediments they removed and improvements that stuck after a retrospective. Coaching ability matters more than authority — they should influence through trust, not mandate. Ask how they handle a team that resists agile practices; the answer reveals whether they coach or simply impose.

Ask the candidate to describe a team that was struggling to deliver and what they did to improve it — listen for diagnosis, intervention, and measurable outcome. Probe how they run retrospectives and how they ensure agreed improvements actually happen. Ask how they handle a stakeholder who repeatedly disrupts the sprint with urgent requests. Present a scenario where two team members are in persistent conflict and ask how they would address it. Finally, ask which agile metrics they find most useful and which they distrust — this reveals depth beyond surface familiarity with the framework.

Agile communities such as the Scrum Alliance network, Agile Alliance, and local agile meetups surface engaged practitioners. LinkedIn searches filtered by certification and years of facilitation experience help qualify candidates. Referrals from engineering and product teams who have worked with effective Scrum Masters are high-signal, since the role's value is hard to assess on paper. Conference attendees and speakers from Agile20XX and regional agile events tend to be invested in the craft. Be cautious of candidates whose experience is purely certification-based without demonstrated team-improvement outcomes.

The clearest red flag is a candidate who confuses ceremonies with outcomes — someone who runs the meetings by the book but cannot point to a team that got faster, calmer, or more predictable under their coaching. Be wary of the certificate-only Scrum Master who has never navigated real organisational friction; the hard part of the job is influence without authority, not facilitating a stand-up. Watch for anyone who treats velocity as a target rather than a planning aid, because weaponising metrics quickly destroys trust. Command-and-control language is another warning sign; a Scrum Master serves the team rather than directing it. Finally, distrust candidates who cannot describe a time they removed a genuine impediment that sat above the team — chasing another department, unblocking a dependency, or protecting focus from stakeholder churn.

A new Scrum Master should observe before changing anything. In the first weeks they need to understand how the team actually works, where flow breaks, and what the recurring impediments are — sitting in ceremonies and one-to-ones as a listener, not a reformer. By the second month they should be facilitating confidently, surfacing real blockers, and building relationships with the stakeholders and adjacent teams whose dependencies cause most delays. By ninety days, expect visible improvement in predictability or team health, and a retrospective culture the team owns. The classic failure mode is imposing a rigid framework on day one; agility comes from adapting to the team's context, not enforcing textbook process against their grain.