There are definite signs of Agile methods (with a capital A) may be losing mind share or, at the very least, suffering from a certain amount of perhaps over-hype or over familiarity. Or maybe it is just the rise in cases of AFS (Agile Fatigue Syndrome). For some, agile is giving away to the rise of lean software development. Where will it end?
A variety of agile software development methods and practices have now been around for a solid ten years and existed for at least another ten years prior. Configuration management (CM) for agile development has now been discussed since the turn of the century. So what are the core principles of CM and how can CM help agile teams?
In this article, the authors the use of basic patterns that can help build a software configuration management process that works well with your agile development environment. They discuss how codeline policy, private work spaces, smoke tests, private system builds, integration building, unit testing, and regression testing all work together to enable you to maintain an active development line.