Coaching the organisation: the Scrum Master beyond the team

Most Scrum Masters are hired for a team and spend the first year discovering that the team's biggest problems are not inside it. A release must be approved by a board that meets monthly. A manager wants a weekly report on individual output. A budget is set for a year with scope fixed up front. None of these can be fixed by a better Retrospective. They need someone to work with the organisation, and the Guide says that someone is the Scrum Master.

What the Guide asks

The Guide lists how the Scrum Master serves the organisation. They lead, train and coach the organisation in its Scrum adoption. They plan and advise Scrum implementations within the organisation. They help employees and stakeholders understand and enact an empirical approach for complex work. And they remove barriers between stakeholders and Scrum Teams.

Each item is about influence and understanding rather than authority. A Scrum Master seldom has the power to change a policy. They have the standing to describe the effect of the policy clearly, to propose alternatives, and to help the right people try something different.

The Guide also reminds us that the Scrum Team is "structured and empowered by the organization to manage their own work". That sentence puts the origin of empowerment outside the team. A Scrum Master who only works inside the team is not working on the main source of the team's freedom or lack of it.

The SBOK® Guide has a few organisational structures for this. It describes an optional but recommended Scrum Guidance Body, a set of documents or experts who define organisational objectives such as quality, security and regulation and who act as a consulting structure for teams without making project decisions. For large projects it adds a Chief Scrum Master to coordinate across teams, and describes the Scrum Masters as peers. These are ways of spreading and sharing the coaching work, and they do not replace it.

Three kinds of organisational work

Understanding. People above the team often hold a picture of how work should happen that comes from sequential projects. Explaining empiricism in their terms, with their numbers, is slow, repeated work. It goes best in short conversations tied to a real event: "here is what we saw at the Review, and what it changed".

Barriers. These are specific obstacles: an approval step, a shared environment, a procurement rule. The Scrum Master gathers evidence of the cost, finds the owner of the barrier and asks for a change or an exception. GOV.UK's guidance on agile governance describes the aim: decisions made at the right level, with teams knowing the boundaries of their authority and who is accountable for helping them when a decision lies outside it.

Structure. Some changes are larger: how teams are formed, how funding works, how performance is reviewed. A Scrum Master advises here, and the decisions belong to leaders.

A worked example: the weekly status report

This is an illustrative case. A department head asks every team for a weekly spreadsheet listing each person's hours and tasks. The Scrum Master sees three effects: it takes about two hours per team per week to produce, it is out of date by Monday, and it makes Developers reluctant to say that a task is stuck.

A weak approach is to refuse. A better one is to find out what the head needs. In a conversation, the Scrum Master learns that she is asked monthly by her own director whether the work is on track, and has no other way to know.

The Scrum Master offers an alternative with the same purpose: an invitation to the Sprint Review, where she can see the working Increment, and a one-page summary after each Sprint stating the Sprint Goal, whether it was met and the top two risks. She tries it for three Sprints. The first review impresses her more than the spreadsheet ever did. By Sprint three the spreadsheet is dropped, the teams save two hours a week each and the department head has a statement she can pass up with confidence.

The Scrum Master did not win an argument. They met an organisational need in a way that fitted the framework, and made the better option the easier one.

Signals that the organisation is learning

Progress at this level is slow and quiet, so it helps to know what to look for. Managers start asking about the Sprint Goal instead of individual tasks. A policy gets an exception, then a trial, then a change. Leaders turn up at the Sprint Review unprompted, and ask about the Increment. Budget conversations begin to mention outcomes and learning, not only scope. Each of these is small, and together they show that the empirical approach the Guide describes is spreading beyond the team.

There are also signals that it is not. Requests for individual reports return after a reorganisation, approvals pile up again after a new director arrives, and teams quietly stop inviting stakeholders. These are not failures of the Scrum Master. They are the normal return of old habits, and the work resumes with a new conversation.

Choosing battles

An organisation has many barriers, and a Scrum Master has limited standing. A few guidelines help.

1. Start with what blocks the Sprint Goal. Evidence from the team's own board is the strongest case.
2. Prefer small experiments to proposals. "Can we try this with one team for six weeks?" is easier to say yes to than a policy change.
3. Find an ally with authority. A sponsor or director who understands the issue can open doors.
4. Count the cost. Quantify time lost or delay, in plain numbers.
5. Accept partial progress. Some barriers will not move this year. Record them so they are visible, and return when conditions change.

Common mistakes

• Becoming a crusader. Pushing Scrum as an ideology gets resistance. Focus on problems people already have.
• Working only through the team. Developers cannot fix a budget cycle.
• Overstepping into management. The Scrum Master advises and coaches, and does not decide for the organisation.
• Speaking only to the top. Middle managers often hold the practical power over how teams work. Include them.
• Hiding the cost. If an organisational barrier is costing weeks, say so, with numbers, in a place leaders will see it.

How to practise it

List the three biggest delays your team had last quarter and mark which were inside the team. Choose one that is not, and write down who owns it and what you could offer them. In the simulator you meet pressure from sponsors and managers, and your replies show how well you are serving the wider system.