Infrastructure Refactoring


the change per a standard Agile iteration. At the end of the iteration, the project team and product owner decides if the infrastructure change is acceptable and ready to go live into the working infrastructure and start being used by the project team. If not the change can be bundled with the deliverables of next iteration(s) and then released together.


Work the IPAIR Loop

The next strategy in approaching the changes is to consider the steps that will help you through an iteration focused on establishing or changing infrastructure. Because it is less likely that there will be a fully dedicated infrastructure team assigned due to the multi-tasking nature of infrastructure work, we want to keep the steps fairly simple and consistent. Also infrastructure professionals may not be into Agile as much as the project team, so a simpler variant of the traditional iteration is suggested. In this case, consider an IPAIR approach or something similar:

·         Identify changes and place in infrastructure backlog

·         Prioritize changes

·         Assess impact of changes

·         Iteratively make the changes

·         Re-assess impact of change seeking approve and release of changes

·         Begin the loop again (e.g., rinse, then repeat)

The steps within the iteration should be brief and simply enough to follow. The changes that are identified should be small enough that they can be made within the 1 week iteration. If you encounter a situation where you need more than one week, be flexible enough to expand the iteration timeframe. Also, you may find that if it is a larger change, that there may be a way to break up the change into smaller chunks of work to fit a short iteration.

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!