Infrastructure Envisioning

[article]

After each infrastructure piece is delivered and effectively implemented, then acquire feedback on the infrastructure functionality as input for adjustment and prioritization for the next iteration. Let us look at each strategy in more detail.

Assess Risk
Now that you have a high-level view of the infrastructure stack and layers therein, it is time to identify risks that can prevent success. It is important to manage risk, as it provides lead time into potential problems that can slow velocity. By identifying and assessing infrastructure related risks, the more serious risks can be appropriately mitigated. This ensures we do not waste time upfront focusing on lesser risks and also do not waste time later on resolving a problem that could have been prevented if a mitigation of the greater risk had occurred.

Prioritize
Prioritization of infrastructure needs allows the project team using Agile and those involved in establishing the infrastructure with a means of knowing how much value certain tools are to the infrastructure and then implementing them in a just in time (JIT) approach. As an example, the need for a server and desktops typically are high priority or work cannot get done so they should be available when the project team is ready in the first iteration. However, prioritization of other tools in the support layer may be a lower priority or until such time as the effort to implement them is outweighed by the need to have them in place. Another example of this is configuration management (CM) tools. Sometimes on new projects, people avoid a CM tool or use a very simple CM tool. Howeve,r as code starts to change frequently and many

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. He has worked in the CM field since 1986 and in the agile field since 1998. Mario 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. Mario is the author of Adapting Configuration Management for Agile Teams  and Software Configuration Management Implementation Roadmap. 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

Sep 22
Sep 24
Oct 12
Nov 09