Agile Adoption Roadmap

[article]
    • may also include test tools, continuous integration tools, and collaboration tools (amongst others). The benefit with tooling is that it may help support the Agile process, improve interaction with distributed teams, and enable automation. If the team is fortunate enough to be colocated, then a physical team wall is a suitable replacement for an Agile planning tool.
  • Focus on Agile mindset and cultural shift
    • While it is important to provide a focus on Agile practices and tools, a specific focus on establishing an Agile mindset is important. This involves a focus on self empowerment, servant-leader, assertiveness, volunteering, etc. The benefit is that this ensures there is a focus on the Agile mindset.

Agile Deployment

The goal of the deployment phase is to execute the Agile approach and practices and help the team apply them to the project. This phase typically lasts about one to three months. Tasks to consider getting Agile deployed within product teams include:

  • Set up the Agile Planning tool
    • During the readiness phase, there should have been a focus on Agile tool needs, and if so, a selection of a tool or tools. Once the tool has been selected, approved, ordered, and received, it is time to install and deploy the tool for team use. This ensures that the team has a common interface, and access to the user stories and work ahead.
  • Provide Agile Training
    • This involves providing role-specific training to those that will be applying Agile. While off-the-shelf Agile training is fine, it is beneficial to incorporate context-specific details into the training, or provide a one-off training that walks the team through the Agile methodology and practices framework that was established during the readiness phase. Types of training to consider are:
      • Agile for the Team – Agile training with a view from the team’s perspective. This should include the Agile methodology and practices with a specific focus on Agile engineering practices
      • Product Owner training – Agile training with a view from the Product Owner’s perspective. Specific focus should be given to writing user stories.
      • ScrumMaster training - Typically Certified ScrumMaster (CSM) training. Given the abundance of CSM training held throughout the world, it may be best to approach this using an external vendor.
      • Agile Tool training - If there is an Agile planning tool, it is beneficial to train the Product Owner (to establish and manage their backlog), the Agile team (to refine stories and use their wall), and the ScrumMaster (to manage burndowns and other reporting).
    • While there is an obvious benefit to Agile training, it is important to ensure there is an emphasis on adapting to the Agile mindset.
    • In addition, consider providing periodic Agile Qamp;A sessions. These sessions provide the opportunity for team members to ask questions that come up after they have had formal training.
  • Deploy the Agile methodology and Agile practices
    • As the project gets kicked off, and Agile methods and practices start getting used, this where the Agile Coach (or someone experienced in Agile) helps deploys the Agile practices to aid in improving the execution. This may involve helping apply the practices for the first three sprints and providing coaching and mentoring to the team to correctly apply the practices. This ensures that the Agile practices are being understood, deployed as defined, and applied with an Agile mindset.
  • Periodic Meetings to ensure deployment is on track and directionally correct
    • As the deployment phase is underway, it is important to have brief periodic meetings to ensure there is a focus on the deployment activities. The benefit of doing this is to ensure the team sees that Agile adoption is not
Tags: 

About the author

Mario  Moreira's picture Mario Moreira

Mario Moreira is a Columnist for the CM Journal, a writer for the Agile Journal, an Author, an Agile and CM expert for CA, and has worked in the CM field since 1986 and in the Agile field since 1998. He has experience with numerous CM technologies and processes and has implemented CM on over 150 applications/products, which include establishing global SCM infrastructures. He is a certified ScrumMaster in the Agile arena having implemented Scrum and XP practices. He holds an MA in Mass Communication with an emphasis on communication technologies. Mario also brings years of Project Management, Software Quality Assurance, Requirement Management, facilitation, and team building skills and experience. Mario is the author of a new book entitled “Adapting Configuration Management for Agile Teams” (via Wiley Publishing). It provides an Agile Primer and a CM Primer, and how to adapt CM practices for Agile Teams. Mario is also the author of the CM book entitled, “Software Configuration Management Implementation Roadmap.” It includes step-by-step guidance for implementing SCM at the organization, application, and project level with numerous examples. Also consider visiting Mario’s blog on CM for Agile and Agile adoption at http://cmforagile.blogspot.com/.
 

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

May 04
May 04
May 04
Jun 01