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: Don’t push scrum to a team without their having bought into it ..

This one seems very obvious, so why write such a post ? After all, if the team management and other senior manages decide that Scrum is being adopted by many teams and over a period of time, there is improvement in productivity and the number of features that have been generated by teams that have adopted Scrum have increased; this being the case, why should their team not adopt Scrum. So the management decides to adopt Scrum and informs the team that they are changing the development methodology and the team will go through some amount of training so that they can start using Scrum.
Sounds good, right ? Well, it can work in some cases, but I have been discussing this with other Scrum Masters and one of the most common problems that the teams report is about not understanding why they moved to Scrum. The amount of cynicism that has been seen from team members can be pretty bad. Some of the statements that the teams have reported go along the line of “Scrum is the new fad so the managers decided we should do this”, “Why are we doing Scrum”, “Nobody asked us before moving to doing Scrum”, and so on. It always sounded a bit odd that the development methodology where the team is expected to take the lead in execution responsibility and where the team has a lot more responsibility is one where the decision is taken top-down and pushed onto the team. It will still work in some cases and the team will do good, but there will be a higher chance that the team really does not see any increase in productivity and could in fact run into problems.
So what is the problem ? Well, a team moving into using the Scrum methodology runs into a large number of changes, you could say the whole way they do their work has changed, and this can be very jarring especially when the team is working well. In such a case, it is not really a good idea to get into a massive process change without getting into a discussion with the team. The managers and the team need to understand why they would want to make such a change; what are the problems that they may be running into and how Scrum could be a benefit to them. This is not a discussion that you need to hurry into; the team needs to get into a discussion with other teams who have implemented Scrum and understand what it means to a team that is doing this; what are some of the issues and process problems that they will run into.
At some point, if the team realizes that Scrum is something that they can consider and move ahead with, then it makes sense to have one or more team member along with a manager or a lead to go off and do an evaluation and present to the team once they are done with their studying. If this works out, then you can be sure that the team will not have those sort of queries about why they are doing Scrum, is there any benefit of moving on to Scrum, and so on, and contribute to the success of the team in using Scrum.

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>