A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Scrum: Encouraging people to not wait for the Daily Scrum meeting to list obstacles ..

The Daily Scrum Meeting is supposed to be the meeting where the team discusses their work done on the previous day, the impending work that is planned to be done in the next day, and also any impediments that may be there for the team members. These impediments can be in different forms, such as those related to design issues, those related to some dependencies with other teams and linkages with their work, organizational issues, and the like. The problem that sometimes happens in Scrum teams is their training emphasizes the basic need of the Daily Scrum meeting and the items that are supposed to be discussed in the meeting; the training that I have seen does not focus on providing solutions for the impediments outside of the Scrum meeting. As a result of all this, the Scrum team members typically have an inclination to bring up the impediments in the Daily Scrum meeting, even if they have to wait for some time for the same (and this is not true of every Scrum team, but if it happens in a Scrum team, then the issue needs to be highlighted and a solution needs to be found).
So what is the solution ? There is no magical solution or anything like that. This typically happens in new Scrum teams, or in teams that are already showing some sort of issues or problems. The team needs to understand that the process of resolving impediments devolves on everybody in the team. It is only when an impediment cannot be resolved by the team member, then it needs to be brought forward in the Daily Scrum meeting where the Scrum Master can note the issue and then, after the meeting, work out the process to ensure the impediment is resolved (and needs to do this in a way that the team can see and come to an understanding that the impediment has been resolved quickly – which gives them confidence in the abilities of the Scrum Master is working to resolve impediments quickly).
However, as a result of all this, the team should not get the feeling that they do not have a responsibility to resolve impediments. There are a number of impediments that can be resolved through quick discussions among the team members, and they need to ensure that they do a best case attempt at resolving them. Else, you will not have the team really taking on the responsibility that Scrum methodology demands that its team undertake. If this is not happening, or the team members have some doubt on how this can happen, then the Scrum Master and the team can take any of the impediments that are raised in the Daily Scrum Meeting and try to resolve them by guiding a team member for the steps. This will help to ensure that the team learns about the type of impediments that can be resolved at their end vs. the impediments that need to be raised in the meeting with the scrum master taking the lead to figure out how to resolve them post the meeting.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>