Recent Articles



Intro to Software Configuration Management

configuration management system Posted by Rob Castellow


        What I would like to provide to software development groups is a simple easy to reproduce approach to SCM.  This website will attempt to help many of the development groups out there that are interested in either improving their existing software configuration management plans or that are creating an effective software configuration management system from nothing.  This is not the esoteric information that you may see on the web or books, but  configuration management for the real software world.

Oh yeah! I forgot to mention one thing.   I'm extremely cheap too, so this website is geared towards saving some cash on software configuration management tools while implementing a good software configuration managment process that handles the needs of small or large groups. 


Software Configuration Definition

So whats the point of all this?  Why can't I develop my software the way I always have?  The answer may not be obvious when starting to develop a good configuration managment process, but when the development process is in full swing a good software configuration process is a necessity.

My goal is to define software configuration management in practical terms, so that even your manager can understand.

I have several goals when setting up a configuration management

1.) repeatability

2.) enhanced communication between developers and management

3.) enable SCMs to identify code releases

4.) reportability of the state of the code at all times

5.) manage process

6.) track defects and enhancements

7.) manage expectations

8.) manage environments

Lets not get into the details of these goals yet.  They soon shall be explained.

  

Who needs Software Configuration Management?

The software configuration manager answer to this question is EVERYONE!  However in reality, the number of people getting into the code base has a direct effect on the level of software configuration management that is needed.

        Let's take for instance my 1-3 man outfit at my company, PAC Enterprises LLC.  With 1-3 developers, the concern is not so much on communication since good old fashioned conference calls, IMs, etc are easy with this number of developers.  The main concern is not losing code, creating releases, and some degree of defect/enhancement tracking.

Now lets go to the other end of the spectrum with a 50+ person development group.  There are some real issues with communication on that size development group which is why many companies shy away from large development groups.  I know of many companies that are afraid to go over more than 7-10 developers per group.

There should be no reason why a small or large development group cannot adopt a simple and affordable software configuration management strategy.  The next section will help with the planning of that strategy.

Software Configuration Management Planning