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.

One of the biggest complaints about the Daily Scrum Meeting from team members ..

The Daily Scrum meeting is a very simple meeting, but when run well, it can be critical for the Scrum based project to work well. It essentially comprises of the Scrum team members coming into the meeting, and talking about the work they did the previous day, the work they have planned for the current day, and if there are any issues that could cause them conflicts in their work (and these could be literally any kind of problems – could be a design issue, could be a hardware problem, anything that is causing them problems in their work). If these happen well, then these updates are shared between team members and not delivered in the form of a status update to a manager, not even to a Scrum Master (who in most cases, tends to be a more senior member of the team or a former manager of the team).
But, no matter how empowered the team, one of the most common off the cuff remarks that you hear from team members (across cultural distances, across geographies) is how this matter of a Daily update is seen by the team. When they get the scrum training, then it is emphasized that the Daily Scrum meeting is a quick form of informing the other team members about your progress, and this helps the people whose work is dependent on your work (dependent could be a tester waiting for the developer to finish a task, or could be a developer waiting for another developer to complete a task so that the design dependency is met). Soon after they actually get involved with the Scrum process, informal conversation between the Scrum team members makes the Daily Scrum meeting have a double impact.
So, the Scrum team members do see an impact of sharing these details, but for many of them, the Daily meeting is also a test for them, a sort of quick peer review. For example, one of them told me that when he comes before the Daily Scrum meeting and tells about a task that is still pending, which the others would believe should have gotten done, there is a slight smile on the faces of the other people. That smile, seen whenever a task was delivered late (and which was more often for one of the developers) caused an impact that none of the previous scolding of the Project Manager (when the team was working using the Waterfall development methodology) seemed to have. The Daily Scrum meeting actually caused this developer to improve their speed of working so that he could go the Daily Scrum meeting and stand up there with a straight face, and state that they had completed the work that they had taken on.
This type of getting upto a sort of stage of ones own peers and then seeming to be failing or not being upto the mark as compared to the other members of the team was something that literally forced them into figuring out how to improve themselves. This was despite the knowledge that no matter what happens, there will be always some members of the team who are better than the others and things can only be improved to a certain extent.

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>