Being a strong proponent of both agile and configuration management (CM), I was curious to learn if agile professionals perceived CM to be of value in an agile setting. Having worked in both areas for some time, my initial hypothesis was "yes" agile professionals value CM. It should be noted that the Agile manifesto has a value that says, "People and interactions over processes and tools". I interpret this to mean that the people and their interactions should drive the appropriate level of processes and tools and not have tools or processes dictate how people should work and interactions should occur. In addition, the word "over" does not mean "versus" so it does not mean that processes and tools are unimportant.
While most agile professionals do not let CM drive their interactions, they appear to value CM. Having worked in agile teams and hearing stories from agile and CM professionals, I decided to exercise my hypothesis and find out if in fact agile professionals do find CM tools and processes to be of value in their software development work and at what level. With that in mind, I conducted two studies to determine the importance of CM.
Study #1: How Important Are CM Tools?
The first study was conducted in both the "Agile Journal" and on "LinkedIn". Since this was the first study (and I believe the first study of its kind), I led with a very simple questionnaire where I asked Agile professionals the following question: How important are CM tools (e.g., version control) for agile projects?
I provided five categories as possible answers: extremely important, very important, somewhat important, not very important, and not important at all. While not meant to be an exact survey, it certainly provided a telling outcome.
The results from this study (based on 208 respondents) indicate that CM tools (or at least the version control function) are indeed important for agile teams working in software development. When combining the number of respondents who answered either "extremely important" or "very important", the result was a dramatic 94%. This is quite an amazing number. Parsed out, this includes 75% of the respondents answering "extremely important" and 19% answering "very important". I wonder if there are any other tools where 75% of agile professionals would answer as being extremely important to their work. Respondents who answered "not very important" or "not important at all" accounted for only 2%. While there were over 200 people who responded, I do not consider this conclusive data. However, it is certainly data to consider. Table 1 illustrates the spread of answers across all 5 categories.
Table 1: Importance of CM tools (e.g., Version Control) for Agile projects
Another interesting result from this survey is the distribution of those that answered "extremely important" appears to vary by age in a telling way. The chart below indicates that older Agile professionals find more importance in CM tools. About 67% of those in the 18-24 age category find CM tools extremely important. Of those in the 25-34 age category, 78% find CM tools extremely important. Of those in the 34-55 age category, 89% find CM tools extremely important. Most telling are those agile professionals that are 55 years of age or older, 100% find CM tools extremely important. To be fair, there was a smaller sample of data for those 55+ years old, so further studies should occur to make this data more meaningful. However, it raises the question, as engineering professionals increase in age (and presumably in experience) do CM tools become more important? Have they experienced enough problems as a result of not having solid version control, where a CM tool is considered extremely important? Table 2 illustrates the age spread and importance of CM tools.
Table 2: Distribution by age range of who rated CM tools "Extremely Important"
Finally the last bit of data from the survey results indicates that there may be a slight difference in the way the agile engineers (e.g., as part of the agile project team) perceive the importance of CM tools versus the way product managers do. In this case, 90% of the agile professionals who are engineers appear to indicate that CM tools are extremely important while only 60% of agile professionals who are product managers indicate this. This may account for the fact that engineers are more severely impacted when there are problems with identifying or controlling code. However, upon further investigation, when combining the top two categories, 100% of both engineers and product managers believe CM tools are either "extremely important" or "very important". Table 3 illustrates the distribution of importance by these two roles.
Table 3: Distribution of Importance by Role (e.g., Engineers and Product Managers)
Study #2: How Important are CM Functional Areas?
The second study sought to drill down further as to which CM functions are perceived to be valuable by agile professionals and which are more valuable than others. With this in mind, I conducted a second survey in the "Agile Journal" where I asked agile professionals within a polling questionnaire to please place a value rating on each of the following CM functional areas:
· CM for the project including planning activities, roles, etc.
· Version control: tool with check-out/check-in process
· Build management: tool with continuous build process
· Branching and merging: tool and continuous integration process
· Change control: process of managing changes
· Problem management: tool and process, a.k.a., defect tracking, issue management
· Audit: process, baseline, etc.
· Reporting/status accounting: process
· Release engineering: tool and process, aka, migration and installation
I provided 10 value choices (from 1 to 10) where 1 is the lowest value and 10 is the highest value. While not meant to be an exact survey, it provided some interesting data.
The results from this study (based on a modest 25 respondents) indicate a range of perceived values for the various CM functions. Build management received the overall highest average value score with 9.21 (out of 10). This is not surprising since continuous integration and build is a highly valued practice for those who implement agile. This was closely followed by version control which received an average value score of 9.13. This may be because of the recognized need of control due to the high volume of code changes. The high value of the version control function correlates well with the first study where a high percentage of agile professionals indicated that CM tools (e.g., version control) were either extremely important or very important.
Branching and merging is next with a score of 8.33. When considering that a big part of continuous integration assumes merging, then this high score is not surprising. Most interesting is change control with the fourth highest score of 7.92. In the survey, there was a short description included with change control that said "process of managing changes". With this additional piece of information, it may be that Agile professionals align control of changes with iteration planning where change is periodically managed. Not surprisingly, CM reporting and auditing are perceived as least valuable. Agile tends to find reporting beyond the basic burn-down charts of less value and believes that auditing is just an extra step that is unnecessary when the team works continuously and closely together. Table 4 illustrates the average values of the various CM functions. While I do not consider this conclusive data, it is certainly data to consider.
Table 4: Average value scores of the various CM functions.
Configuration management (CM) appears to be valued by agile professionals after receiving a combined score of 94% who responded with either "extremely important" or "very important" from the first survey. Why this is may be because agile is a facilitator of change that requires change mechanisms that can handle the high volume of change. CM provides those change mechanisms to ensure the integrity of change on a software project. When drilling down one level, several CM functions appear to be of high value based on the second survey results starting with build management. With the continuous integration and build practice spanning both CM and agile this may be no surprise. Being a strong proponent of both configuration management and agile, I am happy to see these results. For agile professionals who have not yet considered CM as a valuable asset to their work, it may be time to do so now. It may be to your advantage. For agile professionals who do understand this powerful combination, more power to you and it may be worth giving some of the CM functions a second look.