Unified Configuration Management

Home |  CM Survival | The CM Portal  | CM About Us | Email

 Configuration Management Plan  

1 Introduction

The obligatory fluffy introduction.

Example: This document constitutes the Configuration Management (CM) Plan for the consulting services division of UCMcentral. The methods are based on established CM practices recommended by leading organisations including the ANSI-IEEE and the ISO.
1.1 Purpose of CMP

Summarise what a CMP is (or means to your organisation)
1.2 Scope of Document

Summarise the scope of the document. i.e. Identification, Control, Status Accounting and Audit.
1.3 Definitions, Acronyms and Abbreviations

Clarify Abbreviations e.g. CCB (Change Control Board)
1.4 Document References

Reference the key CM, QA and Project Documents.
1.5 Document Overview

Use this overview to summarise the key direction of the strategy. Hint: A few activity diagrams would help.

  
2 The Organisations CM Framework

Section to describe the key players and environment
2.1 Organisation 

Describe the CCB structure

Describe CM Team 
2.2 Responsibilities

Define Roles and responsibilities 
2.3 Tools & Infrastructure

Summarise the CM environment and CM specific tools. Consider CM Servers, Build and Packaging Systems etc

 
3 The CM Process

Section to describe how each of the key CM dimensions will be achieved.

3.1 Identification

Explain how you will identify the current state of your products and systems. Note: This can be done in various ways including use of formal configuration documentation, use of version control tools, use of baselining (snapshot) tools etc.
3.2 Management and Control

Describe the procedures and quality gates employed within the organisations CM life cycle. Consider Tools and Practices for: Development, Engineering, Build, Deployment, Change Requests, Defect Tracking, System Management.
3.3 Configuration Status Accounting

Define what status updates you will provide and how. Consider: Change Request Reports, Build Reports, Defect Reports, Bill of Materials and Release Reports.
3.4 Auditing

Articulates how your solution will carry out Configuration Management Audits. Things to consider: Functional Audits, Physical Audits and Process Audits.

4 Project Schedules – CM Milestones

Provide project planning support/guidelines for CM activities. Ensuring these activities are scheduled in the Project Management plan will ensure that CM is a cultural focus within the team and best practices are followed throughout the life cycle.
  

5 Project Resources

Identifies resources. 

6 Plan Optimisation

Clarify how this plan will be maintained and mature. This will prevent the plan becoming redundant and outdated. Note: An excellent way to ensure CM maturation is by having "critical" reviews planned at key milestones.

Appendix
Relevant support material e.g. Release Request Forms, Sign-Offs

Copyright © 2002 SnuffyBear Company (Sydney Australia).