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: Team members do not present required details in the Daily Scrum ..

The Daily Scrum meeting is one of the simplest meetings that I know about. I have been through different kinds of meetings, whether these be in the Waterfall kind of methodology, or in Scrum, or any other such methodology, but the Daily Scrum meeting is one of the simple meetings. The meeting is defined to be less than 15 minutes long (well, I am not sure whether there is such a rule, but all the literature I have read seems to cater to the 15 minute rule and ensure that the meeting is brief). The meeting is meant to happen on a Daily basis, and expects each team member to talk about the following to the rest of the team in a non-storytelling kind of manner:
– What the team member has done since the last meeting
– What the team member will be doing till the next meeting
– Any impediments that the team member is facing right now
In my experience, the team members realize the advantages that the Daily Scrum meeting provides them, but there is some amount of impatience to have such a meeting on a Daily basis and there is a need to have the meeting updates by the individuals done quickly, so that the team members can leave and get on with their work. However, one of the items that can elongate the meeting is when you have team members who are either not properly prepared with their updates or were so busy (and so much on their mind that they take time to provide their updates). This happens more often than you would think, and is something that needs to be handled.
What do you do in the case where some of the team members do not do enough preparation of the Daily Scrum meeting and do not have either complete or accurate information to talk about in the meeting. Given the dependencies that happen in the Scrum team, there is a need that the person providing the update typically has correct and uptodate information; if people are not providing such an update, then the meeting becomes more like a formality, and soon any interest in attending such a meeting with go away, and people will be forced to go through other meetings or communication to get the information that they need.
One way that teams handle such a problem is by also having a Task wall where the items that are being worked on are displayed, and this ensures that the team members can quickly see the tasks that they are working on, which helps them provide an update more easily if they are not prepared as such. This also ensures that the meeting gets an added touch of professionalism since now ever work update can be seen against the Task wall and the team can also see progress as the cycle goes by. If something is going slowly, this is also pretty clear to the team right away without the Scrum master trying to drum this into the team. And of course, if somebody is deliberately not taking the time to be prepared, then the team needs to exert the right amount of pressure.

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>