Responsibility of scrum master Role

This idea comes from 2013 October when I work as scrum master in Oil and Gas industry. 

In 2013 we start rotate scrum master role to make everyone have deep understanding of agile and scrum activities.

So I summarize responsibility of scrum master, share this to team to make scrum master role rotate smoothly.

Unfortunately I miss the original slides, I just have some materials recorded in One Note, now I recorded in CSDN.

Scrum master is a facilitate role for scrum activities. I cover this from four stage:

1. Sprint planning

For sprint planning, scrum master should facilitate product owner (PA sometime we call) to orgnize planing meeting.

What team will do in comming sprint defined by PO, ohter facility work should be done by scrum master. Scrum master also can

give suggestion to planning from effort capacity, jump-in task view.

2. Daily activities

Normally scrum have daily stand up meeting to show progress of this sprint, scrum master should facilitate stand up meeting.

These work contains many trivial tasks, I also do below things for our team:

1> Remind team member to update status of user story, input effort every day.

2> Update sprint burn down chart before stand up meeting, this help team to keep awareness of sprint progress

3> On stand up meeting, record issues and take action to communicate with other team if team have dependency.

3. Grooming, preparation of next sprint plan

In this stage help PO to pick up user story plan to next sprint, make these sure these user stories have clear requirement description and 

acceptance criteria, this is preparation part of grooming.

On grooming meeting, help team to give effort for each user story, and update this to user story, we use TFS means we update to TFS.

4. Sprint review and retrospective

If we do every stage of sprint very well, we are coming to an happy sprint ending, we need to review and demonstrate what we have done

in passing sprint. Also we need to do retrospective. In retrospective we can summarize thing we do very well and we need to keep this in next sprint.

We can summarize thing we need to improve and have action item assign to team member. we can check action items follow up status in last sprint, 

this is the key point of retrospective, raise up action items and follow up.