I’ve noticed the term “Scrum Master” results in a variety of facial expressions for people who are unfamiliar with the Scrum roles. These run the gamut from confusion to suspicion to outright incredulity.
“What does this even mean? What is this “Master of Scrum”?
Sounds like complete rubbish; an imaginary role that offers no credibility or substance.” Their body language further reinforces their intrinsic cynicism – arms crossed, neck tensed, palms clammy. I imagine they envision hundred-dollar bills engulfed in flames, each time a Scrum Master deposits their paycheck.
I rise to the challenge and dutifully describe the role of the Scrum Master.
A Scrum Master is the “servant leader” for the Scrum Team, Product Owner and organization. This means promoting and supporting Scrum through teaching Values, theory, practices, and rules. Scrum Masters serve the Scrum team by shielding them from outside forces, removing impediments and coaching them in self-organization and cross-functionality, all of which allow them to focus on creating high value products. They also encourage the team to improve its development process and practices to make it more effective and enjoyable for the next sprint.
They serve the Product Owner by offering techniques for effective product backlog management, ensuring goals, scope, and product domain are understood by everyone, and facilitating Scrum events as requested or needed. The organization relies on the Scrum Master to lead and coach the Scrum adoption, induce change to increase the productivity of the Scrum teams and help everyone to understand and enact Scrum and empirical product development. In addition, the Scrum Masters are continually monitoring transparency by inspecting the artifacts, sensing patterns, listening closely to what is being said, and detecting differences between expected and real results.
Without Scrum Masters, we must assume that the Scrum Team and a Product Owner work together like a well-oiled machine and fully comprehend Scrum. (I have yet to experience this.) Who is going to help those outside the team understand which interactions are helpful and which aren’t? Who will explain the agile “Why” behind the agile “What”? Who is monitoring the health of the team, keeping Scrum events focused & efficient, and coaching the team on autonomy, cross-functionality, and self-organization? Who is continually observing the team dynamics, enforcing the agile mindset, and challenging for continual improvement?
After explaining all of this, a mental light bulb turns on, I know this because their facial expressions change. Their eyebrows relax, body leans forward, fingers steepled at their lips, in a thought-provoking manner.
AHA! Perhaps I’ve cracked the code.
What if we replace the role of “Scrum Master” to “Team Coach”? If leadership and team members viewed them as “Team Coaches”, then perhaps they wouldn’t be continually trying to understand or justify their role.
After all, every great team needs a coach. Don’t they?