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.

What are some of the impediments that can hold up a Daily Scrum ? How are impediments handled ?

Part of the routine of a Daily Scrum is where team members come up with the issues that they face which could be stopping them from doing their work. These are called impediments, and are typically problems that are preventing them from completing their work. Once the team members articulate their impediments, it is the role of the ScrumMaster to resolve these issues. But resolving of these impediments is not done during the Daily Scrum meeting, since the meeting is supposed to be a quick and short meeting and this would not be possible if people start solving these impediments right then and there. Further, it would be a big turn-off to other team members if they have to sit in a meeting where some issue is being discussed that is not relevant to them.
An impediment is just that, anything that prevents a person from getting their tasks done. It could be complicated matters such as technical dependencies, or it could be small matters such as an unpleasant odor near the office of the person, or a non-working machine. Once these are communicated during the meeting, it is then the responsibility of the ScrumMaster to resolve these issues offline, depending on the nature of the impediment. Some matters would require the ScrumMaster to call a meeting to resolve these issues, while infrastructural issues need to be handled by the ScrumMaster by contacting the required organizational persons. These can also be policies related to the organization (typically found in teams which have recently moved over to Scrum or where the organization uses other methods of development for a significant number of its projects). In such cases, the ScrumMaster will have to also raise these organizational issues. If the team members start to get a feeling that their impediments are not being handled in time or handled effectively, it can quickly have a very quick effect on the efficiency of the whole Scrum process. Part of the process of impediment handling is to ensure that people can see the status of their impediments, when they will be resolved, and that there is sustained action towards the same. If this require some sort of tool, then that should also be used.
Some of the more difficult impediments relate to personnel issues. You could have a team member who is dragging his / her feet, either because of lack of capability, or because they are not convinced about Scrum; in such cases, resolutions can be to try and figure out what is wrong, and if that does not work with the employee, then it makes sense to talk to get a different person.
Some of the impediments are related to user stories or the specifications. In such cases, the ScrumMaster has to make sure that he gets the Product Owner (and maybe the experience designer) to answer all questions and provide the required level of detail.

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>