Configuration management (software change management) controls, audits and organises all changes that occur in the software lifecycle, also aiming to improve cross-project communication.

Organisations with weak configuration management practices typically suffer from:

• Unstable software including re-introduction of previously resolved defects.
• Little or no visibility and auditability of changes.
• Inability to define release contents and communicate effectively with the customer.
• Increased support costs coupled with low customer satisfaction.
• Increased design and development times, heavy maintenance costs.
• Little or no design documentation, no correlation between design and test stages.
• Information and skill silo's leading to complete dependence on specific staff.
• Poor project planning, frequently missed and extended deadlines, lack of cross project communication.

Configuration management is essential for all businesses that depend on software. It is a fundamental component of software industry standards such as the Software Engineering Institute's "Capability Maturity Model Integration" (CMMI), Rational IBM's "Rational Unified Process" (RUP) and the Office of Government Commerce's "IT Infrastructure Library" (ITIL).

There are a number of tools and methods with which to implement CM. The choice of tool will depend upon your budget, the specific issues you wish to overcome and company specific factors such as whether your developers are distributed between various locations.

Following purchase of the correct tool for your business it is essential that you define clear processes, tailor your CM tool to accurately follow those processes and clearly communicate the new working methods to your staff.

If you would like to understand more about the benefits to your business of a CM system or discuss which tools are best suited for your needs then please contact Clearvision.