There are moments in Scrum Mastery where it looks like they’re doing very little.
They’re quiet in a meeting.
They don’t jump in to fix a problem.
They let a conversation run longer than feels comfortable.
From the outside, it can look like inaction.
From the inside, it’s some of the most deliberate work they do.
One of the most persistent misunderstandings about the Scrum Master role is that it exists to enforce process.
Seen this way, the Scrum Master becomes a kind of process police officer – checking attendance, correcting behaviour and reminding people what Scrum says should happen.
But that framing misses the point of the role entirely.
Scrum does not exist to be obeyed.
It exists to help teams work effectively in complexity.
And complexity does not respond well to enforcement.
