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 Planning

Attendees: Whole Scrum Team (including dev team, scrum master and product owner)

Duration: Ideally 1 hour per sprint week. Example – 3 hrs for a 3 week sprint and 4 hrs for a 4 week sprint

When: Before a Sprint begins.

Why: To populate the sprint backlog for the coming up sprint.


  1. Access team availability to gauge how many stories can be completed in a sprint
  2. Define Sprint Goal
  3. Product owner pull stories from prioritized product backlog
  4. Team discuss the user stories
  5. Team throw estimates on the stories in story points
  6. Discussed and estimated User stories are pulled into sprint backlog
  7. Team commits to the sprint goal and the user stories in the sprint backlog.

Helpful Tip(s): Refinement meetings ( or grooming meetings) before the sprint planning meeting help in hashing out intricate details of the planned stories for the upcoming sprints.


Like my blog?