Configuration Mgt Strategy - Best Practice LMS



CONFIGURATION MANAGEMENT STRATEGY

Version: #

Date: #

Authors: #

Project Executive: #

Customer/User: #

Document Number: #

|CONFIGURATION MANAGEMENT STRATEGY |Document Ref & Version No: |

|Programme: |Project: |

|Author: |Date: |

Purpose:

This Configuration Management Strategy has been produced to define how, and by whom, the project’s products will be controlled and protected throughout the project. It outlines guidance on the following:

o How and where the project’s products will be stored

o What storage and retrieval security will be put in place

o How the products and the various versions and any variants of the products will be identified and version numbered

o How changes to the products will be controlled

o Who is responsible for configuration management

Introduction:

Configuration Management Procedure:

Planning

Identification

Control

Status Accounting

Verification and Configuration Audit

Issue and Change Control Procedure:

o Capturing

o Examining

o Proposing

o Deciding

o Implementing

Scales for Priority and Severity:

Tools and Techniques:

Records:

Reporting:

Timing of Configuration Management and Issue and Change Control Activities:

Roles and Responsibilities:

|Role |Responsibility |

|Corporate or Programme Management | |

|Executive | |

|Senior User | |

|Senior Supplier | |

|Project Manager | |

|Team Manager | |

|Project Assurance | |

|Project Support | |

The undersigned have checked this document against the following Quality Criteria:

1. The responsibilities are clear and understood by both user and supplier.

2. There is a clear definition of the unique coding (identifier) scheme for the products.

3. The procedure and method for version control is clear.

4. The strategy will provide all the information required by the Project Manager to keep control of the products.

5. Existing corporate / programme management configuration management / change control procedures have been considered.

6. The project filing system will provide information necessary for any audit requirements.

7. The project files will provide the historical records required to support any lessons identified.

8. The chosen configuration management strategy is appropriate to the size and nature of the project.

9. There are sufficient resources in place to administer the chosen configuration management method.

10. The requirements of the group who will be operate/maintain the product in its useful life have been considered.

Project Manager’s Signature:

Executive Approval:

Senior User(s) Approval:

Senior Supplier(s) Approval:

Date:

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download