Scrum Master

Scrum Master is one of the 3 scrum roles and the characteristics of an ideal Scrum Master are as follows:

  • Ensures the team is completely functional and productive
  • Helps the team to organize its work by keeping them focused on the sprint goals.
  • Leads the team through conflicts
  • Removes impediments for the team
  • Fosters the team on the path of continuous improvement
  • Protects the team from external disturbances so they can focus on their goals and commitments
  • Helps the team become self organizing by empowering the team members
  • Creates transparency by keeping the scrum artifacts visible to the team and the stakeholders.
  • Creates and manages matrices like burndowns and burnups for the stakeholders’ and team’s reference.
  • Takes care of the Scrum Process by facilitating scrum ceremonies like Daily scrum, demos, sprint planning and sprint retrospectives
  • Makes sure agile ideas are understood and respected by all stakeholders, PO and organization
  • Moderator, Trainer, Mentor and Mediator for the team.

Keys to a successful Scrum Master:

  • Should have a servant’s heart to be ready to help the team in any way possible to make them move forward
  • Should not act as the team’s manager but a leader and a facilitator
  • Should be an expert on Scrum
  • Has decision making authority
  • Actively involved in setting goals for the team including release goals and sprint goals.

 

Like my blog? 

 

Sprint Restrospective

Attendees: Whole Scrum team (including dev team, ScrumMaster and Product owner)

Duration: 1 hour

When: Last day of a sprint after all the stories are ‘Done’

Why:

  1. Inspect & Adapt
  2. Improve
  3. Learn
  4. Process Improvements

What:

  1. Scrum Master facilitates
  2. Scrum Team discusses ‘what went well’, ‘what can be improved’ and ‘New Ideas / suggestions’
  3. For what went well – appreciate and encourage the team / team members.
  4. For what can be improved – team inspects and tries to come up with solutions or process improvements
  5. Welcome suggestions
  6. Continuous improvement is the main idea behind sprint retrospectives.

Helpful Tip(s):

  1. Sprint Retrospective should not be used as a forum to blame each other.
  2. Try to keep the Sprint retrospective closed to only the scrum team members as that will give them a comfortable environment to communicate their views.
  3. Bring up the ‘suggestions’ or ‘what could be improved’ cards from the last retrospective and get the scrum team’s views on how the team has improved on those.
  4. Keep changing the format of the sprint retrospectives once in a while, otherwise people may get bored soon. For more ideas to run retrospectives please visit: Retrospective Ideas

 

Like my blog?