John Hines' Software Process Blog

A blog on Agile software development and Scrum

  Home  |   Contact  |   Syndication    |   Login
  39 Posts | 6 Stories | 42 Comments | 0 Trackbacks

News

The information in this weblog is provided “AS IS” with no warranties, and confers no rights.

This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.

To err is human, to forgive is divine.

Tag Cloud


Archives

Post Categories

agile

If there's nothing else to know about Scrum (and Agile in general), it's this:

You can't force a team to adopt Agile methods.  In all cases, the team must want to change.

Well, sure, you could force a team.  But it's going to be a horrible, painful process with a huge learning curve made even steeper by the lack of training and motivation on behalf of the team. 

Even if just one person on the team is fiercely against Agile, it won't work.  It's incredible to me how a single person can strongly influence the direction of an entire team.  Let alone if Scrum comes down as some managerial decree onto a functioning team who have no idea what it is.  Pity the fool.

If you preside over a team process change, it's beneficial to start the discussion on how the team will work as early as possible.  You should have a vision for this and guide the discussion, even if decisions are weeks away.

And anyone in a leadership position should be wary of always rooting for the underdog.  It may feel like this is where a leader can really make a difference, but team harmony should also be taken into account as well.

Technorati tags: Scrum Scrum Process Scrum and Waterfall

posted on Tuesday, March 16, 2010 2:23 AM