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: It causes divas to get exposed on a daily basis

You know those kind of people, they exist in almost every software team. Typically folks with more experience and well feted, they are truly the divas of the team. In a majority of the case, the reputation is well deserved, and they do a lot for the teams that they are working in. However, once in a while you will come across a person who is well feted, very influential in the team and yet there is the niggling feeling about whether this reputation is well deserved or not. You could take a closer look at the work done and maybe come to a conclusion that there was nothing special, but the reputation means that trying to make changes will not happen so easily.
Enter Scrum. One of the definitions of the effects of Scrum that I have read elsewhere is about the use of Scrum in a team exposing all the problems that a team faces and ensuring that you see those problems on a regular basis. These problems also are present in other projects but they are hidden, or maybe the Project manager and / or the leads know about some of these problems abut a lot of times, the problems are not brought out in the open and they can cause problems (or at the minimum, the Project Manager and the leads may have to spend additional time fixing these issues).
If you take the case of divas who don’t really perform, then one of the most effective ways in which Scrum can expose these problems is through the Daily Scrum meeting. Every day the team gathers about for a quick meeting where they update each other on the work done since the previous day as well as the work planned on being done for the next day. It is here that the reality of tasks and the schedule is pretty clear; and it is also in this meeting where the under-performer is exposed. In fact, this is even more problematic for those team members who have not been performing.
It can get pretty bad to stand there in front of your team members and on a regular basis talk about tasks that are not yet done although they should have been done, and so on. Now, the idea of the Daily Status meeting is not to pass judgment, but if you have people who are dependent on the task of one person and that person is delaying his or her work, then it starts affecting the schedule of other people. Pretty soon you will find that feedback from within the team will reach the person who is regularly delaying their work, even if they are a diva within the team. I had a team member whose excellent reputation took a bit of a tarnish when people could see that even though the work was pretty good, the estimation was problematic and more often than not, the Daily Scrum meeting would see that person talking about a delay. The problem was that being a diva with influence, getting such a person to change was not easy; it finally took such performances in many Daily Scrums for the team to provide an appropriate feedback which resulted in a change in behavior.

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>