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

ScrumMaster Can be a Tough Job

DZone's Guide to

ScrumMaster Can be a Tough Job

· Agile Zone ·
Free Resource

The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.

I’m writing about a talk given by Paul Hodgetts at Agile 2009 called “ScrumMasters Considered Harmful – Where Did We Go Wrong?” ( Link to full presentation).

So, why doesn’t the title of this blog post match?  The title is really catchy, but the the talk was more of an investigation and discussion of what the ScrumMaster role really entails.  Check out the Mind Map below.

scrum-masters-good-or-bad

Some of the interesting things to note are that there are a lot of roles that a ScrumMaster is supposed to take on if you are following Scrum – see the green checkmarks.  (If you are not following Scrum – why do you have a ScrumMaster? ;-)  Anyway, it’s a tough job!

One hot area  is around the role of Project Manager or Task Master – there is often a management expectation that they will play this role.  I have seen this many times.  Hint: a better answer is that work needs to come through the Product Manager and that the team is un-interrupted for the duration of the Sprint.  But every situation is different, so there is no always in this.

On the left in purple, can be seen a number of candidates for taking on the role of ScrumMaster.  It can be a tough role to fill.

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap, brought to you in partnership with Techtown Training

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}