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). It's easier to learn but much more difficult to practice. Adopting scrum is not just a change of titles but is a 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. The following are the Do's and Don'ts for a Scrum Master to be effective.
Scrum Master Do's
- Facilitate the product owner to maintain and prioritize the backlog items.
- Facilitate team members with any additional training or coaching required.
- Makes sure that team delivers the true value to the business.
- Inspires the team members to own the tasks.
- Allows and helps team members to make decisions.
- Removes any impediments holding the team back to achieve their goals.
- Helps team to become self-organised.
- Shields team from external interference.
- Acts as a servant leader.
- Should be willing to improve continuously.
- 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
- Own the decisions on the product backlogs from the product owner's behalf.
- Make estimates on the team's behalf.
- Assign the tasks to the team members.
- Try to manage the team.
- Make changes to the team in the middle of the sprint.
- Accept backlog changes in the middle of the sprint.
- Make commitments on behalf of the team.
A Scrum Master does not control the team. He acts as a facilitator and works as a servant leadership.I hope this will help someone. Please add your thoughts in comments.
Reference: http://www.scrumzen.com/scrummaster-dos-and-donts