Table of Contents
A Scrum Master adds value when they remove blockers, improve the way a team works and protect developers from avoidable process noise. If the job is limited to running stand-ups and updating a board, the team is right to ask what the role contributes.
This is an opinion piece based on my work as a software developer and senior system administrator. It is criticism of poorly implemented Scrum, not an argument that every Scrum Master is useless.
My test is simple: does the role help the team deliver better work, or does it mainly create more meetings and status reporting?
When stand-ups become theatre
Many IT professionals argue that the Scrum Master’s role is nothing more than a scripted symphony, a daily ritual of standup meetings where tasks are reviewed and roadblocks are discussed.
The Scrum Master, often perceived as non-technical, navigates through these meetings with a script, asking about progress and any potential roadblocks, seemingly without understanding the tasks’ intricacies.
This scripted interaction leads many to question the value and necessity of the Scrum Master.
A Personal Reflection on Agile Distortions
In my work as a software developer and senior system administrator, rotating facilitation among team members has often worked better than treating Scrum Master as a permanent layer.
Rotation forces people to understand one another’s work and makes the ceremony a shared responsibility rather than somebody else’s performance.
It also exposes a useful distinction: facilitation is necessary, but a full-time facilitator is not always necessary.
The version of Agile I dislike is the one that adds recurring meetings without giving the team more authority, clarity or time to solve problems.
That is bureaucracy wearing an Agile label.
Scrum Masters or Designated Panicker
Some have humorously labeled their Scrum Masters as the “Designated Panicker,” responsible for orchestrating daily, weekly, and monthly “panics” or meetings without contributing substantial value or solutions. I personally have spent hours a week in meetings to accomplish no tangible outcomes.
A Scrum Master does not need to be the strongest engineer in the room. They do need enough technical context to understand why a blocker matters and enough trust to help remove it.
Scrum Master Roadblock Resolver?
The proponents of the Scrum Master role argue that the essence of this position is to resolve roadblocks and facilitate communication between teams. In my personal experience this is rarely the case.
The “any roadblocks?” question, often perceived as redundant, is deemed crucial in identifying and addressing impediments in the workflow.
However, the effectiveness of a Scrum Master in resolving these roadblocks is contingent upon their authority, proactiveness, and understanding of the tasks at hand.
When these qualities are lacking, the Scrum Master becomes a mere observer, a tracker of progress without contributing to the actual advancement of projects.
The Replaceable Entity
The argument that a Scrum Master’s role can be replaced with software is typical. Suppose the position is confined to tracking progress and identifying roadblocks without actively resolving them or improving processes.
Can software not accomplish the same, if not more efficiently? The demand for Scrum Masters and the training provided for this role is often seen as catering to a redundant need, a formality in the Agile process without substantial benefits.
My verdict
My verdict is not that every Scrum Master is pointless. The pointless version of the role is a meeting chair who records blockers but cannot remove them.
A good Scrum Master should make the team’s work easier to understand and easier to complete. If the team would get the same outcome from a dashboard and a rotating facilitator, the permanent role needs a clearer purpose.
The r/sysadmin discussion that inspired this article contains examples from people who have seen both versions.
Judge the role by outcomes: fewer unresolved blockers, clearer priorities, less wasted meeting time and a team that can change its process when the process is not working.
As a software developer and system administrator, I have seen plenty of Agile ceremony and much less genuinely agile decision-making.
A simple test for the role
Is Technical Understanding Crucial?
- How crucial is it for a Scrum Master to have a technical understanding to add value to the IT workflow?
The Role of Authority:
- Can a Scrum Master effectively resolve roadblocks without having the necessary authority and proactiveness?
The Possibility of Replacement:
- Can software effectively replace the role of a Scrum Master, especially when the contribution is perceived as minimal?
If a team cannot answer the three questions above with concrete examples, start by reducing the ceremonies and defining what the Scrum Master is expected to change.
Keep the conversation going by leaving a comment about your thoughts on Scrum Masters and Agile.