Tips to Scrum Master on removing impediments

One of the important duty of a Scrum Master is to remove impediments to the Development Team’s progress. This is correct and must be followed and here are some tips on doing this effectively

1. During development sprint, team need clarity on the design from Architect who may not be co-located, this can become a potential impediment if clarification does not come on time from architect.

In such cases, Scrum Master should advise the team member to draft the clarification with  his/her thoughts on tackling it rather than just looking for Architect's guidance. This will help Team member to evolve his thinking and at the same time this will help Architect the respond fast as he/she will have some ideas.

      2.  During development sprint, testing member raises bugs/issues which they realize when they get the build to test from development. This can become a potential blocker to completion of the story as this has come late in the game.

In such cases, Scrum Master should try to avoid such situation in future by coaching the team members. Testing member should prepare automation test scripts and validate all possible scenarios in the beginning of the sprints which would at least help team to reduce such situation.

Another approach that testing team member should take is to collaborate and ask relevant questions rather than dependent on the development member to  think about. it should be a team work.

   

There are many other improvements we can make in the sprint to track the impediments which I will share in my future posts.