agile top banner
Back to blogs

Scrum master roles and responsibilities

Read it in 5 Mins

Last updated on
27th Jun, 2022
Published
17th Dec, 2018
Views
5,248
Scrum master roles and responsibilities

How do the various roles and responsibilities make a Scrum master an amazing game changer?

Three influential powerful roles in Scrum framework of agile software development are- Product Owner, Scrum Master, and the Development Team (Development Team is a cross-functional team such as UI Designers, Dev, QA, DevOps and specialties necessary to complete the work). Here I am sharing my awesome experience/ roles as a Scrum Master:

1. Scrum Master responsibilities towards Addressing Team Dynamics:

  • A good scrum master encourages the team to follow Scrum and also ensures the team has a more productive environment. 
  • Provide guidance to the team on how they can become Self-organized to achieve the Sprint goals. 
  • Tackles scrum teams, work on impediments, facilitation and also educate organization on agile methodologies to maximize value delivered.  
  • Enabled improvement in team delivery commitments and capacity planning for sprints by identifying & tracking hidden tasks that increased customer’s satisfaction. 
  • Ensures to keep build transparency with the entire team.
  • Share insights throughout the company through blogging, internal confluences etc.
  • Managing, improving, empowering and shielding the Scrum teams to achieve Sprint goals. 
  • Gives trustable Working environment where all problems can be raised without fear.
  • Arbitrate between team members when necessary.
  • Ensures a good relationship with Dev Team and Product owner

2. Scrum Master as a Facilitator, Moderator, and Master of Ceremonies: Facilitator  “key player responsible for Process ”, Moderator “Guide the Scrum team” and Master of Ceremonies “person responsible for the show i.e. Scrum events execution”.

  • Scrum Master conducts ceremonies like Sprint Planning, Daily Stand-Ups, Sprint Reviews, and Retrospective meetings.
  • Sprint Planning and Story Refinement: Ensure the product backlog has been ordered and completed by product owner before sprint planning begins.

Attendees: Product Owner, Scrum Master, and Development Team.

 Time box: 2Hours for 2 Week Sprint.

Daily Scrum (Daily Standup): In a Daily Stand-up meeting each team member needs to update 3 questions:

  • What did you do yesterday? 
  • What will you do today?
  • Any Obstacles or blockers?

Attendees: Scrum Master and Development Team
Time box:  Daily sync-up not more than 15 minutes

Sprint Review or Sprint Demo: Product Increment Demo, planned vs. completed work assignments. Capture actionable feedback as items in the backlog.
Attendees: Stakeholder, Product Owner, Development Team and Scrum Master.
Time box: 2 Hours for 2 Week Sprint

Sprint Retrospective meeting: Meeting organized by Scrum Master in which team discusses three points:

  • What went well in the sprint?
  • What could be improved? 
  • What will we commit to improve in the next sprint?

Any actionable suggestion is captured, assigned and tracked by Scrum Master.  

Attendees: Development Team and Scrum Master. Product Owner is optional.
Time box: 1 Hour for 2 Week Sprint
Burn-Up and Burn-Down charts: Team progress display in terms of graphs is one of the most popular agile methodologies. Scrum master should be able to conduct Sprint /Release progress through Burn-up and Burn-down charts.

Profile

KnowledgeHut

Author
KnowledgeHut is an outcome-focused global ed-tech company. We help organizations and professionals unlock excellence through skills development. We offer training solutions under the people and process, data science, full-stack development, cybersecurity, future technologies and digital transformation verticals.

Trending Blog

6