Configuration Management Plan Free Document Template
What is Configuration Management Plan?
The overall objective of the Configuration Management Plan is to document and inform project stakeholders about Configuration Management with the project, what Configuration Management tools will be used, and how they will be applied by the project to promote success.
This free document template scope is to detail the configuration management procedure, describe the tools and procedures used to version control configuration items generated throughout the project or product lifecycle.
This document defines the project’s structure and methods for:
- Identifying, defining and base lining configuration items (CI)
- Controlling modifications and releases of CIs
- Reporting and recording status of CIs and any requested modifications
- Ensuring completeness, consistency, and correctness of CIs
- Controlling storage, handling, and delivery of the CIs.
Configuration Management Plan Template Structure
The free Configuration Management Plan template covers the following topics:
- Purpose – This section, provide a clear and intelligible statement as to the intent or objective of the plan; the goal or intended outcome of someone reading this document.
- Scope – Description of the organizations, functions, or personnel affected by the plan. The scope shall define the subject of the document as well as its applicability and any possible exclusion. The scope shall be succinct, so that it can be used as a summary for bibliographic purposes if required.
- Definitions and acronyms – Explain any unique or special words, acronyms, or terms contained in the document. It is a good practice to list acronyms in alphabetical order.
- Referenced and Supplementary Documents – Identify any external objects, which directly support and are used to sustain the given document, examples include; Forms, URL’s, and Multimedia files such as Audio and or Video.
- Roles and Responsibilities – Define the person(s), function(s), or organization(s), which are responsible for performing or accomplishing the objectives described in the purpose of this document.
- Tools, Environment, and Infrastructure – Describe the computing environment such as the number of desktops and their configuration that will be used in the project or product lifecycle. Describe the network infrastructure used to access the customer repository. Describe the tools and procedures required used to version control configuration items generated throughout the project or product lifecycle. Issues involved in setting up the CM environment include:
- Anticipated size of product data
- Distribution of the product team
- Physical location of servers and client machines and the nature of their access>
- The Configuration Management Program which provides configuration identification as follows:
- Identification Methods – Describe how project or product artifacts are to be identified. The identification scheme needs to cover system software, Third Party & Open Source products and solutions, and all application development artifacts listed in the product directory structure; for example, plans, models, components, test software, results and data, executables, and so on.
Opportunity ID-Project Short Name or abbreviation-Type-Document Short Name
Documents are classified as Configurable items, Managed and Records
Configurable items are documents and artifacts that once baseline cannot be changed or updated without going through a formal approval process for e.g. Design Documents, Requirements specifications, Test Plans, code, CM plan etc.
Managed documents are those that evolve during the course of the project. Earlier versions of such documents are maintained for the purposes of ensuring that there exists traceability of events and activities. For e.g. Project Plans (Typically all project management plans fall under this category).
Records are documents that depict outcomes of events or activities. Such documents have only one instance and cannot be modified. For e.g. Test results, minutes of meetings, review reports etc.
The naming convention for all the documents shall follow the scheme mentioned in this section.
- Configuration Baselines – Describe at what points during the project or product life cycle the baselines are to be established. Baselines provide an official standard on which subsequent work is based and to which only authorized changes are made.
- Branching and merging strategies – Identify the Branching and Merging strategy for the project
- Release Plan – Describe how each release is to be identified.
- Project Media Storage – Describe retention policies, and the back-up, disaster, and recovery plans. Also describe how the media is to be retained—online, offline, media type, and format. In case back up is taken by internal IS team, plan for verification of the backups shall be include
- Configuration Audits and Reviews – List the Configuration Management audit activities and re4sponsibles.