Free Configuration Management Training

Configuration control is concerned with the procedures for the issue and submission of configuration items. These procedures should address both physical and electronically stored configuration items.

Configuration audits consist of cross checking the configuration item description records with the current version of the configuration item as held in its development folder.

In the first instance, a configuration item should be created and documented as the first version. The configuration item may then undergo a number of modifications as it is tested and errors corrected, or as changes are requested and these subsequent submissions should be reflected by an increasing version number.

The first baseline for a configuration item will be established when the specification of the item has been prepared, reviewed and agreed. Subsequent baselines will normally be established at points at which the Configuration item is ready to be used as a basis for further work in which a major transformation of it will take place.

A ‘Release’ consists of a specified set of products from one or more base-lined configuration items, which are issued as a set for a specific purpose. Releases should be authorized by the project or sub-project manager.

The configuration management plan should be produced as part of the project initiation document, for approval by the project owner at project initiation. Where appropriate configuration management should continue throughout the life of the delivered end-product, and therefore the approach adopted should be transferable to the client organizations operational and maintenance sections at the end of the project.

If other projects within the organization are using a configuration management method then this should be seriously considered for the current project, particularly if the two projects share any areas of interest.

The following typifies recommended minimum scope required of a configuration management method. However, this should be adjusted to suit the needs of each particular project.

Synopsis & Purpose
This should provide a brief overview of the plan and highlight any differences in approach to existing site standards - with a justification thereof. It should also explain the aim of the activities defined in the plan. Any dependencies on configuration management plans from other projects should be identified.

References
This serves to identify all other standards to be used by the configuration management method.

Configuration Item Identification
This section should specify the naming and numbering conventions to be used for all types of configuration items.

Scope
This should outline the full range of tasks in the plan, in particular it should consider all areas that have links with associated projects or that may be bringing in prefabricated components. Any special operating requirements should also be considered. It should also define which items are to be managed under the plan and which are outside the plans control.

Definitions and Abbreviations
This is a short glossary that should be produced to support the plan, if necessary.

Responsibilities
The clearest representation is a responsibility matrix, showing which role should carry out each activity in the plan. The role of administrator will feature often.

Filing
This section defines in detail the filing structure to be used for each category of configuration item. This should cover hardware, software, documentation, human and machine readable items.

Document Issue Procedures
This should define the procedures to be used for issuing and distributing copies of all managed documents.

Security
This should define the access security measures for the master copies of all configuration items.

TOP