Infrastructure Refactoring


Putting the Strategies into Action

Let us consider a scenario where we have an existing infrastructure in place for a product. After the product has been in production for two years and three releases, the product manager realizes that the project team is having problems keeping up with the customer needs due to following a phased lifecycle approach that delivers once a year. The product manager decides to implement an Agile method using Scrum for the project management practices and XP for the engineering practices. A customer advisory board (CAB) is set up that is made up of key end-users who are willing to meet weekly. Also established are two customer liaisons from within the company who join the project team to continuously interact with both the team and the CAB to ensure that customer value is always considered and reassessed.

The team decides to run with two week iterations. After two iterations, the team becomes very aware that their current infrastructure, which was fine for a more phased and hierarchical approach, does not support the Agile methodology very well. 

The team agrees that changes must be made. They stop progress for an iteration and instead introduce an iteration 0 which simply focuses on infrastructure change strategy and identifying the changes. They identify several infrastructure personnel to form an infrastructure team. The project and infrastructure teams decide that iteration 0 will be 1 week and focus only on identifying infrastructure improvements.

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

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

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