What does a scrum master do on each official day? He has both routine duties that he performs every day, and some miscellaneous jobs that he deals with, as and when required.
Key Elements Of A Scrum Master’s Job
Typically, a scrum master’s day begins with the daily stand-up meeting where he interacts with his Development Team members taking feedback, addressing queries and complaints. He then proceeds to act upon whatever issues may have been raised by his team.
In case there isn’t much to work upon here, the helps the team maintain their burndown charts or complete any other organizational tasks.
He can schedule or attend meetings for planning, discussing or reviewing sprints, or even help out the Product Owner in creating the product backlog.
The day may be interspersed with crisis management and problem solving if unexpected obstacles appear at the work front, especially in regard with the work of the Development team.
What a Scrum Master Should Expect From a First Sprint
Most organizations take a while to get accustomed to the agile strategy of scrum, especially when the transition is abrupt and unexpected.
The team does not know what to expect from the first sprint, and generally have very exaggerated notions of what this change in strategy shall entail.
It then becomes the job of a scrum master to ensure that the Development Team and Product Owner are aware of how the projects shall proceed herein, and what the first sprint shall be like.
The first sprint is usually peppered with multiple crises and dysfunctions, with the cross-functional team being unprepared to deal with the pressure of a time-boxed sprint. Also, sometimes with the individual roles not being very well defined or understood, the first sprint may not even be successfully completed.
Thus, a scrum master must prepare his team about disappointing results at the first shot, and warn them against having exceptionally high expectations so the morale does not go down.