What do you think?
Rate this book
Agile infrastructure and operations: how infra-gile are you?
Some have described Agile and infrastructure as an oxymoron: they just don´t fit together. During one year we have focused on using agile techniques in three different infrastructure related projects. From a unique infrastructural point of view, we will show that the term ´agile infrastructure' consists of multiple layers. To become effective, each layer needs to be addressed.
6 pages, ebook
First published August 8, 2008
1 person is currently reading
7 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
May 20, 2015
As agile software development practices spread, practitioners working in related fields started taking note and wondering whether they could be adapted to their worlds. This is an early paper exploring the use of scrum practices and TDD to the interdisciplinary pit underlying the convergence between development, operations and infrastructure.
The bulk of this short paper is devoted to three experiences, a data center migration, a disaster recovery process improvement effort and an application server upgrade. The most successful effort appears to have been the data center migration, which also included adopting ITIL -however the author appears to point out that they did not solve a crucial issue on service level agreements. The other two efforts do not appear to have been so successful -unfortunately the reasons why are not clearly presented. What is clear though is that they include management issues and cultural issues (both between agile and waterfall practitioners, and between operations, infrastructure and development staff).
The article is not as well written as one would like -there are a number of distracting grammatical errors. The last section, which is supposed to show us how to address the multiple layers of "agile infrastructure" is crammed into a half page of "observed patterns", very arbitrarily divided into "technical, project and operations" patterns, a taxonomy which does not appear to fit well into the development, infrastructure and operations framework which has been used in the rest of the paper. Debois should have taken more time and care over this crucial part of his paper.
ITIL version 3 later took a long hard look at this area and developed service design and service transition practices to address many of these problems but in a non-agile, rather heavyweight fashion. Agile practices bridging developments and operations later coalesced into DevOps.
This paper is still worth reading -the pitfalls depicted are, unfortunately, still very much with us...
The bulk of this short paper is devoted to three experiences, a data center migration, a disaster recovery process improvement effort and an application server upgrade. The most successful effort appears to have been the data center migration, which also included adopting ITIL -however the author appears to point out that they did not solve a crucial issue on service level agreements. The other two efforts do not appear to have been so successful -unfortunately the reasons why are not clearly presented. What is clear though is that they include management issues and cultural issues (both between agile and waterfall practitioners, and between operations, infrastructure and development staff).
The article is not as well written as one would like -there are a number of distracting grammatical errors. The last section, which is supposed to show us how to address the multiple layers of "agile infrastructure" is crammed into a half page of "observed patterns", very arbitrarily divided into "technical, project and operations" patterns, a taxonomy which does not appear to fit well into the development, infrastructure and operations framework which has been used in the rest of the paper. Debois should have taken more time and care over this crucial part of his paper.
ITIL version 3 later took a long hard look at this area and developed service design and service transition practices to address many of these problems but in a non-agile, rather heavyweight fashion. Agile practices bridging developments and operations later coalesced into DevOps.
This paper is still worth reading -the pitfalls depicted are, unfortunately, still very much with us...
Displaying 1 of 1 review