Horses For Courses

I recently attended a scrum course with Mike Cohn, Mike is one of the biggest names in Agile and has written several books on the topic:

There isn't a lot that mike doesn't know about Agile, he's worked with teams in some of the best technology companies in the world. 

One thing Mike's course excelled in was stimulating conversation between the scrum masters in attendance. 

There were exercises sprinkled throughout Mikes content that often had me debating with one of the scrum masters on my table more than most, as the course went on i realised the reason this particular scrum master and I had such conflicting opinions was down to the maturity of our teams.

I work in a relatively new team that's gone through several transitions and is still not fully stablised, my counterparts team had been running for 18 months with very few staff changes.

Ultimately each team is individual and the only right answer on a lot of process specific questions is the answer that's right for the team.

Newer teams require more structure and a more metric, fact driven, approach to development and much more leniency when it comes to estimation. Once a team becomes more mature, more trust exists in the process and they can tweak the factors to meet the needs of the players.

With any new team it's always important to give them room to find their way and not to assume whats worked for one team can be replicated elsewhere.

No comments:

Post a Comment