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: Raising issues at the Daily Scrum or after ..

This one issue is turning out to generate more posts that I thought. I started having a discussion with some office colleagues about this one, and it turned out to be an issue that did not have some clear answers. How are impediments resolved and who does resolve the impediments. Further, should there be a meeting to resolve the impediments, or are those to be resolved at a hallway discussion or in somebody’s office. So, as you might imagine, people have their own views about what should be done to resolve these, and many times, these issues cannot be resolved by way of a simple process. This post will take an opinion on this topic, and if you have any comment to make on this issue, please provide so in the comments.
One of the biggest problems with the Daily Scrum meeting and which requires the most discipline is the need to keep it short. The Daily Status meeting is supposed to be short, where team members come in, talk about what they did the previous day, what they will do the next day, and, what is giving them some kind of problem. If these problems are some kind of infrastructural issues such as computing resources or others similar to this, then these can be resolved by the Scrum Master without anybody else getting involved. However, if it is a design or architectural issue or some dependency issue, then it would typically require other team members to step in and help to resolve the issue. However, it is important that resolutions not be discussion in the Daily Scrum meeting, since that will mean that the meeting cannot remain small anymore. Once people start discussing solutions to problems in these meeting, the meeting no longer works as a short meeting and there is a high risk that some team members who are not connected to the issue being discussed start getting put off from these meetings.
So, one solution would be for the Scrum Master to have a regular discussion with the Scrum team about the need to ensure that the Daily Scrum meeting remains short (many teams make these meetings stand-up where nobody sits, so that there is an impulse to ensure that nobody takes too much time during the meeting). Once the meeting is over, the issues are brought up, and these can be discussed in a follow up meeting where more than 2 people are involved. On the other hand, if the issue just requires 2 folks to do a discussion, then these can be brought up over a discussion that can just happen in the office of one of the folks involved, or can happen even in terms of a hallway conversation if the time required is not very large.
It is not necessary that the Scrum Master be a part of these discussions, but it is important that the Scrum Master should have discussed these with the team and worked out the kind of discussion mechanisms required for these follow up meetings. This will help when there are issues brought up in the Daily Scrum meeting that need some kind of technical or feature discussion and the scrum master wants to ensure that things can get quickly resolved soon after.

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>