Tuesday, August 9, 2011

Agile rollout issues

As an Agile coach, I noticed few issues which are common across the various teams I helped with Scrum adoption.

Initially looked like most of the team members, team leaders and managers are enthusiastic about the scrum rollout, however, as usual, some are reluctant for the change. 

Eventually after lot of presentations and one-on-one discussions, most of the questions were answered and the agile rollout got initiated and by the way, it had the blessings of executive leaders. Without the executive leadership belief in agile it is difficult to adopt.

Initial sprints are rough and later seemed as if the teams got hang of it. However, after 5-6 sprints[2-week], scrum principles are diluted and Scrum masters are getting into the comfortable state and reluctant to stand-up and work with the team and management to follow the proper guidelines. 

Common themes which needs special attention:

  1. Lack of Test automation: Test automation is consistently given a last priority and in spite of its presence in the the 'Definition of Done'. Team is  preferring the old habits of manual testing and not understanding the importance of automation in agile world.
  2. Not completing a story within a sprint: 
  3. Shared resources instead of dedicated team members
  4. Production support issues: development teams are interrupted a lot for the production issues and I believe a dedicated and well trained production support team should be helpful.
  5. Lack of automated unit testing

I personally feel that there is a chicken and egg situation here :-)

Teams tend to give high priority for customer commits, defects, and high priority and keep the automation at the low end of the stack. Which comes first, the automation or the defects/production issues. 

1 comment:

  1. Thank you for the info. It sounds pretty user friendly. I guess I’ll pick one up for fun. thank u

    Agile Software Development