Effective Scrum Master’s Dos and Don’ts


Scrum is a framework with just three roles (Product owner, Scrum master and Team), three artifacts (Product backlog, Sprint backlog and Burn-down chart) and a few ceremonies (Sprint planning, sprint review, sprint retrospective and daily stand up). Its easier to learn but way more difficult to practice. Adopting scrum is not just a change of titles but mindset. In this article I will focus on the role of a scrum master. Being only a good scrum master is not enough, effective is the goal. Below are the Dos and Don’ts for a scrum master to be effetive

Scrum Master Dos :

  1. Facilitate the product owner to maintain and prioritize the backlog items.
  2. Facilitate team members with any additional training or coaching required.
  3. Makes sure that team delivers the  true value to the business.
  4. Inspires the team members to own the tasks.
  5. Allow and help team members to make decisions.
  6. Removes any impediments holding the team back to achieve their goals.
  7. Helps team to become self-organised.
  8. Shields team from external interference.
  9. Acts as a servant leader.
  10. Should be willing to improve continuously.
  11. Handles only one team. If you  are a scrum master of more than one team, the commitment cannot be the same.

Scrum Master Don’ts :

  1. Own the decisions on product backlogs from product owner’s behalf.
  2. Make estimates on team’s behalf.
  3. Assign the tasks to the team members
  4. Try to manage the team.
  5. Make changes to team in middle of sprint.
  6. Accept backlog changes in middle of sprint.
  7. Make commitments on behalf of the team.

Scrum master does not control the team. He acts as a facilitator and works on the concept of servant leadership.

I hope this will help someone. Please add your thoughts in comments.

Advertisements

One thought on “Effective Scrum Master’s Dos and Don’ts

  1. *8. Don’t attend to meetings on behalf of development team (SoS or discussions with external teams) – the team members should feel empowered to freely collaborate with others and take decisions related to HOW they are going to deliver the WHAT. At most facilitate/arrange these meetings but always have DEVs with you.

    Liked by 1 person

What do you think about this article?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s