The Rules of Scrum: Your ScrumMaster believes that Scrum will help the team improve

The primary job of the ScrumMaster is to remove impediments for the productivity of the team. If the ScrumMaster truly believes that Scrum is not helping the team, for whatever reason, it is antithetical to Scrum for the ScrumMaster to continue serving in this capacity. If the ScrumMaster is in doubt of the applicability of Scrum as a whole at any given time, this concern needs to be shared with the team and an assessment of whether or not to continue with Scrum may need to be considered. It may be that the ScrumMaster is struggling with understanding how to implement a specific aspect of Scrum in a particular situation and with the help of the team is able to overcome this obstacle. Another possible outcome may be that the ScrumMaster is unable to overcome personal issues with Scrum at which point the team may decide to continue the Scrum implementation without that person’s involvement. Whatever the process for getting there, it is imperative that the ScrumMaster holds this firm belief. Scrum is extremely difficult to do well. Being a ScrumMaster is a very difficult job. If the ScrumMaster does not believe that Scrum will help the team, then the ScrumMaster will not be able to sustain the work of removing obstacles for the team. Instead, shortcuts will be taken, the benefits will not be realized and much effort will be wasted.

To learn more about helping your team improve visit the Scrum Team Assessment.

Try out our Virtual Scrum Coach with the Scrum Team Assessment tool - just $500 for a team to get targeted advice and great how-to information

Please share!
This entry was posted in Scrum, XP and Lean and tagged , , , , by Mishkin Berteig. Bookmark the permalink.

About Mishkin Berteig

Mishkin Berteig is a Baha'i, a father of four, a husband and an experienced Agile consultant and trainer. Mishkin is a Certified Scrum Trainer (CST) with the Scrum Alliance, a certified Master of OpenAgile with the OpenAgile Centre for Learning and a certified SAFe Program Consultant (SPC) with the Scaled Agile Academy. Mishkin has a technical background including a B.Sc. in Computer Science and worked as a Chief Architect reporting to the CIO of Charles Schwab, but gave it up to be more Agile.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>