ScrumMaster: A Role or a Title?

[article]
Summary:

The ScrumMaster is the most controversial position in agile. Is a ScrumMaster a natural leader within the team or is the role a profession in itself? Here, Mariya Breyter takes a look at what a ScrumMaster actually does and writes that it is a state of mind based on a strong commitment to agile values and a dedication to the team and its success.

The Scrum Guide defines team roles very clearly. We all know that the product owner envisions products that deliver value and team members write and validate code, but what does a ScrumMaster do? According to the Scrum Guide, a ScrumMaster ensures that Scrum is enacted. But, isn't this what every team member does on a self-organizing team? What does “servant leadership” mean to a Scrum team, and why does the team even need a designated “servant” or a proclaimed “leader?”

The ScrumMaster is the most controversial role in agile. Is a ScrumMaster a natural leader within the team or is the role a profession in itself? Is it the basis for a career or a simply a stepping stone? This is not a simple question to ask, and I believe that this is a question every ScrumMaster asked him- or herself at a specific point of time as their teams became more self-organized and mature in their agile implementation. Am I still bringing value? Am I expendable? As one of my colleagues presented it in a ScrumMaster paradox, “if I am a good ScrumMaster, I will become obsolete soon.” Does it mean that the better a ScrumMaster is, the more likely this ScrumMaster is to no longer be needed by his or her own team?

Let’s attempt to answer this question in three logical steps:

  1. What is the ScrumMaster’s role on a team?
  2. Is ScrumMaster a role or a title?
  3. Is the ScrumMaster job a stepping stone or a career in itself?

The Role
What does it mean to ensure that Scrum is enacted? I am sure you’ve seen this role being interpreted as a combination of facilitating meetings, managing the Scrum process, and removing impediments. A more detailed description of a ScrumMaster role is provided by the Scrum Alliance in which a ScrumMaster is perceived as being a “facilitative team leader who ensures that the team adheres to its chosen process and removes blocking issues.”

According to Mike Cohn, “The ScrumMaster is responsible for ensuring that the Scrum team adheres to Scrum values, practices, and rules. The ScrumMaster helps the Scrum team and the organization adopt Scrum. The ScrumMaster teaches the Scrum team by coaching and by leading it to be more productive and produce higher quality products. The ScrumMaster helps team members understand and use self-organization and cross-functionality, and also helps them do their best in an organizational environment that may not yet be optimized for complex product development. When the ScrumMaster helps make these changes, this is called “removing impediments.” The ScrumMaster’s role is one of a servant-leader for the Scrum team.

For me, most importantly, the ScrumMaster role is about orchestrating a team’s work. The ScrumMaster’s responsibility should not fall on facilitating ceremonies (I encourage ScrumMasters to delegate this responsibility to the team members), removing impediments (regarding self-organizing teams, team members do a marvelous job removing all sorts of obstacles and coordinating cross-team dependencies), and minimizing distractions to the team members (for empowered co-located teams, this stops being an issue once your agile implementation matures to a state in which there is shared process understanding, focus, and common goals). So, why do teams need a ScrumMaster then?

My team of internal agile coaches runs our agile implementation as Scrum. Our product owner defines a roadmap, and every sprint we work on is a subset of user stories aligned with the roadmap and prioritized by the product owner. Recently, my colleague was working on a story involving a “ScrumMaster elevator pitch.” If someone within the company who is new to agile asks you “What does it mean to be a ScrumMaster?” during a three-minute elevator ride, what would you tell this person? We brainstormed on this topic as a team and found out that describing tasks or positioning the ScrumMaster as someone being responsible for the process did not resonate with people. We then moved to using analogies, with the one we chose relating to the idea of a race-car mechanic; someone who ensures that the race car operates smoothly and efficiently so that the team performs at its best. This person is someone in the background, yet highly reliable, knowledgeable, and respected by the team and stakeholders.

Another analogy that I like is the idea of an orchestra conductor, but this analogy is more suitable to a less mature team that needs someone to suggest direction and set up rhythm, while the race-car mechanic is the one in the background giving the team all of its pre-requisites for success. If there is no mechanic, the race car will start experiencing issues and will eventually halt to a stop. This provides an answer to the question whether a great team still needs a ScrumMaster. It does, the same way as a great race car still needs a mechanic to keep it going.

Is a ScrumMaster a Title or a Role?
This question is the most controversial one and the one that I personally do not have a good answer to, yet. As a hiring manager, I asked the following question repeatedly to myself and to recruitment professionals: What is the most important factor when you hire a ScrumMaster? Is it the people skills, the ability to lead by example, or one’s previous experience or technical skills?

What I found out is that similar to agile, values come first and the rest (experience, technical knowledge, familiarity with specific agile tools) come next.

The values that I find important for ScrumMasters are being honest, fair, open, never finger pointing, always analyzing and suggesting ideas, listening well, being respectful to team members, and having open communication targeting the right group of stakeholders—not too large, which leads to unnecessary escalations, and not too small, which can lead to team members feeling excluded; it has to be just right. A ScrumMaster makes judgment calls in case of uncertainty, and has a quiet and confident demeanor. All of these values that are hard to quantify make someone a good ScrumMaster. Of course, having knowledge of agile principles and techniques, exposure to successful agile implementations, prior coaching and mentorship experience, and possessing technical knowledge are all important, but they can be acquired. Values and instincts cannot.

User Comments

3 comments
Ben Linders's picture

A Scrum master is a role, preferrably one that multiple people from a team can take. My preference is to let the Scrum master come from the team, a part time role next to technical activities. When recruiting, I would focus on the mindset and skills of people to have people in your team that can do the activities that are needed to have a servant leader that helps the team to do their work.

My view is that to work effectively as a team (or in any other way), you need to pay attention to your process, your way of working. That is mainly what a Scrum master does, which should be only a percentage of his/her time. So for me it’s a role, not a function.

December 12, 2013 - 1:29pm
Skip Pletcher's picture

Perhaps this is a false dichotomy.  Scrum master is certainly, by definition, a role.  The team draws value from someone being designated as SM for a given sprint, someone to act as Scrum parliamentarian and to chase down impediments. 

Whether that is the same person from sprint to sprint or rotated among team members is a secondary consideration.  Whether some organizations decide to so specialize that SM becomes a billet with title(s) does not change the role.

I share your appreciation of the diminsihing value offered by a the SM role as a team (and its parent organization) mature with agile practices.  I also think we risk agility when we decide to specialize staff beyond what their own motivations and aptitudes require.

We disagree with respect to the inability to develop 'values and instincts' perhaps because I have seen civilians converted to warfighters through the development of just such traits.

December 18, 2013 - 12:08pm
Tom Mellor's picture

 

I don't agree that the ScrumMaster is the most controversial role in agile-based development.  That distinction could arguably go to Product Owners.  If you feel that ScrumMaster is just a title, then it is effectively meaningless.  Mike Cohn knows Scrum, for sure, and his opinion about the value and responsibilities of the ScrumMaster are certainly well founded in knowledge and experience. 

In my many years of experience with Scrum and as a ScrumMaster, I would not characterize my work as an orchestration of a team's work.  S/O, S/D teams do that for themselves.  I wouldn't even characterize myself in the ScrumMaster role as a "servant leader."  I would characterize it as a "servant."  I might lead and I might not.  That is situational.  Metaphors and analogies are helpful, but also limiting and sometimes dangerous.  They are easy to call upon and they provide familiar comfort to the mysterious. 

 

Let's see what the Scrum Guide says about ScrumMasters:  "The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.” 

 

 

The Guide then goes on to list ScrumMaster services provided to the PO:  

 

• Finding techniques for effective Product Backlog management;

 

• Helping the Scrum Team understand the need for clear and concise Product Backlog items;

 

• Understanding product planning in an empirical environment;

 

• Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;

 

• Understanding and practicing agility; and,

 

• Facilitating Scrum events as requested or needed.

 

And services provided to the Development Team:  

 

• Coaching the Development Team in self-organization and cross-functionality;

 

• Helping the Development Team to create high-value products;

 

• Removing impediments to the Development Team’s progress;

 

• Facilitating Scrum events as requested or needed; and,

 

• Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

 

 

And services provided to the organization:  

 

• Leading and coaching the organization in its Scrum adoption;

 

• Planning Scrum implementations within the organization;

 

• Helping employees and stakeholders understand and enact Scrum and empirical product development;

 

• Causing change that increases the productivity of the Scrum Team; and,

 

• Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

 

It seems clear what the ScrumMaster is to do.  How you characterize the person – a role or a title – seems trivial except to people who care about such things.  I have seen many various people serve admirably as ScrumMasters and the title or role was unimportant to them.  What is important is performing in the role with élan and bringing about expected value through such performance. 

While career ambitions are perhaps an admirable quality, they are realized because of qualities in work and performance are realized and appreciated.  Values and instincts can be acquired – through experience.  There is an old Montana cowboy wisdom about it:  “Good judgment comes from experience, and a whole bunch of that comes from bad judgment.”

 

December 24, 2013 - 1:27pm

About the author

Mariya Breyter's picture Mariya Breyter

Mariya Breyter is an IT management and project management professional with over ten-year experience ranging from government jobs to versatile corporate experience in media and education. She is a passionate agilist and an active member of New York City agile community. Mariya is also a contributor to a number of online resources on agile and project management topics, including her own blog. In 2011, Mariya was selected as one of the winners of The IT Metrics and Productivity Institute’s PMO Case Study competition. In February 2012, Mariya facilitated a discussion on executive coaching in Agile at Agile Open NYC. She has combined BA /MA degree in Linguistics and Computer Science and Ph.D. in Computer Linguistics from Moscow State University, followed by post-doctoral fellowship at Stanford University. Mariya mostly enjoys coaching teams in their  journey to a successful Agile implementation.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!