Wednesday, January 17, 2018

Scrum Master (SM): A Practical Approach | Supreme Agile

The scrum master role contains many theoretical descriptions that do not provide an  answer to the basic question of “What is the Day to Day activities of the scrum master?”

In this post, I will provide a short checklist that will try to answer that basic question while examining few of the main ceremonies and artifacts of the Scrum framework.

Retrospective meeting

The retrospective meeting allows the team to determine new ways to create continues improvement of the process, the scrum master responsibilities: 

  1. Ensure that all team members will raise any issues that they had in the last sprint.
  2. Suggest work cases/events that can contribute to the open discussion.
  3. Ensure that the meeting will not transform into “Blaming” meeting
  4. Ensure that the team understands the importance of this meeting.
  5. Search for new techniques to make the reporting more effective.
  6. Ensure that every team member will have the chance to speak.
  7. Ensure that all issues from previous meetings are fulfilled.
  8. Suggest new formats of retro. 

Review (A.K.A: Demo) meeting

The review meeting is held at the end of each iteration to review the work done by the team (according to the DoD) and to adapt the product backlog accordingly. The scrum master is responsible for the following activities:
  1. Ensure that the product backlog reviewed and adapt based on the PO requirements.
  2. Ensure that the team can answer any questions regarding the uncompleted stories.
  3. Ensure that the team is ready to present the work they accomplished.
  4. Ensure that all stakeholders presented.

Product Backlog Refinement (A.K.A: Grooming) Meeting
The product refinement meeting used to validate that the product backlog is in good condition, prioritized and ready for the next planning meeting, the SM activities are:
  1. Validate that the PO receives all answers from the team regarding technical stories.
  2. Responsible to write and follow-up all questions raised by the participants.
  3. Validate that the meeting participants are familiar with the meeting goals.
  4. Raise ant issues raised by the team regarding stories prioritization.
  5. Validate that all questions from the previous meeting are answered.
  6. Validate that the product owner is ready for the meeting.
  7. Validate that the relevant stakeholders are participating. 

Activities during iterations (A.K.A: Sprints)

The scrum master will perform some basic but critical activities that will determine if the team will run an effective iteration or not, these activities include the following:
  1. Responsible to increase the communication and knowledge sharing among the team members.
  2. Responsible to validate that all stories and tasks updated based on team progress.
  3. Ensure that the team enforces the scrum rules during the different scrum activities.
  4. If necessary, the scrum master provides technical assistance for team members.
  5. Clearing any impediments from the team that can affect the iteration goal.
  6. Sent invitations to the relevant stakeholders for scrum events.
  7. Ensure the required stakeholders will present at meetings.
  8. Lead the team by example.
  9. Build training session and any other learning activities that will increase team knowledge in scrum. 

Planning Meeting

The planning meeting used to determine the work capacity, team commitments, and the sprint goal, the scrum master activities focuses on:
  1. Help the team to understand if there any major risks that can affect their commitments.
  2. Help the team and the product owner to establish a clear goal for the upcoming sprint.
  3. Help the team to make an efficient task breakdown.
  4. Help the team to understand when they need to stop/Take commitments (Based on the team velocity, Capacity and the complexity of the user stories).
  5. Help the team to bring any technical resource (Expertise) to provide technical information that helps the team to make a more accurate estimation.
  6. Help the team with task prioritization.
  7. Prior to the team to take their next commitments, the scrum master should provide the team “Velocity” and “Capacity” metrics.
  8. The scrum master can use is technical skills to help the team with any questions raised during the task breakdown.

Daily Standup A.K.A Daily scrum) Meeting

The scrum daily meeting designed to allow the team to synchronize about the work progress and to make sure that all team members are focused on the iteration goal, the scrum master activities:
  1. Ensures that each team member provides the full and true information about its progress.
  2. Validate that the iteration burn-down chart reflecting the real work progress of the team.
  3. Validate that all open questions from the previous meeting are answered.
  4. Validate the product backlog PBI’s updated based on the team answers.
  5. Ensures that each team will speak during the time limit of 2-3 minutes.
  6. Stop any member that is not come prepared for the meeting.
  7. Remove all impediments that raised during the meeting.
  8. Ensure that the meeting conducted on a daily basis.
  9. Validate that the meeting starts and end on time.
  10. Validate that there will not be any electric devices that can affect the focus of the meeting.
  11. Ensures that team members will not use the meeting to resolve technical issues (in that case, the SM will take this issue offline).
  12. Remove interruptions from other stakeholders that arrive at the meeting (Product Owner, Managers of other teams Etc.).
  13. The SM should validate that team members will not report to him; this is not a reporting meeting! 
  14. Validate that team members are participating and share their insights based on the meeting agenda.

1 comment:

  1. The retrospective meeting allows the team to determine new ways to create continues improvement of the process, the scrum master responsibilities:



My Presentations