Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Qualities of Good and Bad Scrum Masters

DZone's Guide to

Qualities of Good and Bad Scrum Masters

As organizations begin to scale, roles and responsibilities begin to blur. People may be asked to take on Scrum Master responsibilities. Do you have the right qualities?

· Agile Zone
Free Resource

See how three solutions work together to help your teams have the tools they need to deliver quality software quickly. Brought to you in partnership with CA Technologies

A Scrum Master is one of the three key roles of the Scrum framework. Ken Schwaber and Jeff Sutherland created the Scrum Framework back in 1986, primarily for product development. With 21 years having passed, you’d think organizations would better understand qualities of a good Scrum Master. More noteworthy, they should know qualities of a bad Scrum Master.

Because of this, I created a simple infographic to focus on both good and bad qualities of Scrum Masters. I’ve noticed, as organizations begin to scale, roles and responsibilities begin to blur. People may be asked to take on Scrum Master responsibilities. Do you have the right qualities?

5 Qualities of a Good Scrum Master

1. Servant Leader 

The Scrum Master should be an empathetic listener and healer. This self-aware steward is committed to the growth of people.

2. Coach 

The Scrum Master can coach the other team members on how to use Scrum in the most effective manner.

3. Framework Champion 

The Scrum Master is an expert on how Scrum works and how to apply it.

4. Problem Solver 

The Scrum Master protects the team from organizational disruptions or internal distractions or helps remove them.

5. Facilitator 

The Scrum Master is a neutral participant who helps a group of people understand their common objectives and assists them to achieve these objectives.

5 Qualities of a Bad Scrum Master

1. Boss 

The Scrum Master should not have the ability to hire and fire others.

2. Taskmaster 

The bad Scrum Master myopically focuses on assigning and tracking progress against tasks.

3. Product Manager 

The Product Manager, not the Scrum Master, is responsible for managing schedule, budget, and scope of the product.

4. Apathy

If you are apathetic, you lack interest in or concern about emotional, social, or spiritual well-being of others.

5. Performance Reviewer 

The Performance Reviewer, not the Scrum Master, is responsible for documenting and evaluating job performance.

Discover how TDM Is Essential To Achieving Quality At Speed For Agile, DevOps, And Continuous Delivery. Brought to you in partnership with CA Technologies

Topics:
agile adoption ,scrum master ,agile ,management ,scrum

Published at DZone with permission of Derek Huether, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}