Adopting Scrum is widely treated as a change to how one team works, and the harder part is that it changes how the organisation decides. A framework that puts the ordering of a Product Backlog with one person and the sizing of work with the Developers has moved authority that used to sit with a steering group. An adoption can therefore look complete inside the team and fail everywhere above it. The Guide gives the Scrum Master four services to the organisation and no authority over it, which means the accountability reaches further than the means to act on it.
Scrum as a change to how an organisation decides
Three decisions move when a team adopts Scrum. What gets built moves to the Product Owner, how much enters a Sprint moves to the Developers, and what counts as finished moves to a Definition of Done the whole Increment has to meet. Each of the three was usually settled elsewhere before, by a manager holding a plan and a date.
An organisation can therefore run all five events correctly and still be doing something else. A team that holds Sprint Planning and then takes its scope from a quarterly plan nobody in the room may change has kept the event and given the decision back. The practice worth watching is who answers a question about scope once the answer becomes inconvenient.
Where resistance to Scrum comes from
Resistance is usually read as a failure to understand the framework, and most of it is a reasonable response to what the change costs the person resisting. A delivery manager measured on hitting a date loses the mechanism they are judged by. A specialist drawing their standing from being the only person allowed near the billing job is asked to spread that knowledge. A finance function that funds work by fixed scope has nothing to approve once the scope is a Product Goal.
John Kotter's account of why transformations stall, in the 2012 edition of Leading Change, names the absence of a guiding coalition and of visible early results among the most common causes, and both of those sit above the team. Reading resistance as information changes what a Scrum Master does with it, so an objection from the finance function becomes a description of the funding model, and answering it with more training on Scrum leaves the model untouched.
The limits of the Scrum Master accountability
The Guide calls Scrum Masters true leaders who serve the Scrum Team and the larger organisation, and it lists four services to that organisation, which how the Scrum Master serves sets out in full. The verbs across that list are leading, training, coaching, planning, advising, helping and removing barriers. None of them is deciding.
So the accountability covers the organisation while carrying no authority inside it. A Scrum Master cannot change a funding cycle, reorganise a department or overrule a governance board, and treating the role as though it could produces the pattern the assessment tests, which is a Scrum Master announcing a change nobody above them has agreed.
An impediment that sits above the team
The Guide says the Scrum Master causes the removal of impediments, and that wording does real work once the impediment sits outside the team. An approval gate adding nine days to every release of a mobile checkout cannot be cleared from inside the team, and seeing that somebody clears it is still the Scrum Master's work. Three things make that possible without authority.
- Stating the cost in the organisation's own units, so nine days becomes a figure in release frequency or in revenue.
- Attaching the impediment to an owner able to change it, since an impediment with no name against it waits forever.
- Keeping it on the record across Sprints, because one complaint is an opinion and the same measured delay for six Sprints is evidence.
What a Scrum Master does when all three fail is the honest part of the role. Some impediments outlast the person raising them, and the useful response is helping the team work well inside a constraint it cannot change while the record keeps accumulating. A Scrum Master reading every immovable obstacle as a personal failure will not last the year. Quietly dropping the record is the other failure, because it accepts the constraint on the organisation's behalf.