Whether you’re ready to accept it or not, DevOps is becoming the standard among software development organizations. Infrastructure as Code tools are just one of the many tools that are often implemented as part of a DevOps Toolchain. Implementing new tools can often be challenging but in the long run, adopting tools and best practice can have a huge positive impact on the enterprise.

My colleague, Olivia, recently wrote a series of posts that outline a recommended strategy for incrementally adopting Infrastructure as Code at the organizational level.

This strategy is a six-step, cyclical approach that not only minimizes the risk and costs of adopting Infrastructure as Code, but will build the necessary in-house skill set and momentum for larger and faster cycles. Each steps is additive – building as you go, both in terms of investment and preparation, as will each overall cycle. Olivia does a great job at outlining exactly what’s need for each step, and also suggest the approximate time it will take to implement.

The hours are realistic for many enterprises, but will vary widely depending on many factors such as culture and politics of your organization. I encourage you to check out the entire series and discover how this approach can guide and ease your tool implementation.

Head over to the Inedo Blog to check out all three parts of the series: Part One, Part Two, and Part Three.