The Rules of Scrum: Your ScrumMaster consistently avoids doing hands-on technical work with the team

The ScrumMaster is focused on two main goals: to remove obstacles of all sizes and to help the team become better at using Scrum. Both of these jobs require much work and plenty of skill. To do this well the ScrumMaster will need to refrain from doing hands-on technical work. If the ScrumMaster does this then the team will be protected from interruptions, move faster, and feel supported. If the ScrumMaster doesn’t do this then the team will be interrupted often, become slow, and feel unsafe and in harms way. A ScrumMaster doing hands-on technical is wasteful and distracting.

To learn more about ScrumMasters, 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!
facebooktwittergoogle_plusredditpinterestlinkedinmailfacebooktwittergoogle_plusredditpinterestlinkedinmail

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>