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.

Daily Scrum: See this initially as an overhead by the team

The Daily Scrum meeting is an important part of the meetings that happen as a part of the meetings under Scrum. It is the meeting that happens most often, and is a very important part of making Scrum effective and productive for the team. What is the basic purpose of the Daily Scrum. It acts as a forum where team members can very quickly:
– Talk about what they have done since the last such meeting (not necessarily completed, just been working on)
– Talk about the work they are planning on getting done till the next such meeting
– Point out any impediments that they are facing that need help in resolving

The purpose of the Daily Scrum is to ensure that the team provides updates to each other about their work. This is extremely useful given that there are a lot of dependencies between the different team members related to their work. The work done by a developer passes onto a member of the testing team who would then test it out; similarly, in the case of tech dependencies between the team members, the work done by one team member may be dependent on the work done by another team member and hence there is a need to know when the first work is completed so that the dependent task can be initiated. Instead of the project manager doing this task of informing team members, in the case of Scrum, given that the team has a lot more authority, it is expected that the team attends the Daily Scrum meeting and is aware of the progress of their colleagues on a daily basis.
However, when there are teams that are attempting the use of Scrum for the first time, there could be members of the team who don’t really see the need for such a meeting; after all, they would never have had such a meeting as a part of Waterfall and consider the inconvenience of attending a daily meeting as a significant overhead. This would be even after there has been training for the team and they may have even gone in for some practice sessions as a part of the initial training. How would you handle such individuals and their belief that the team really does not need to have this meeting every day (many of them would argue that the meeting could be held every other day, or on every third day).
As always, there are no bullet points on how to handle such a situation and make it perfect right away. In some cases, you will find that there will be people who are not really convinced by the need for a daily meeting, and you just have to ensure that they are still doing the Daily meeting and providing their best inputs for the same. In the case of others, you hope that once they start seeing that the meeting gets done quickly and they find that there is useful information coming for them out of the meeting, they will be more convinced of the need for the meeting. The team could have internal discussions about why there is the need for a Daily Status meeting and team members who are convinced about the same could do the explanation. In many such cases, you can only explain so much, but you cannot force somebody to change their attitudes; only through explanation and through experience do people get convinced that there is a lot of value in the Daily status 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>