This preview shows the full document, but with content partially hidden.
If you are logged in
, your referral link [?]
is automatically included below.
EMBED CODE (Copy and Paste)
This is a Change and Configuration Management Plan form built in MS Word. The form contains the following sections:
A. General Information – Basic information that identifies the project.
* Project Title – The proper name used to identify this project.
* Project Working Title – The working name or acronym used to identify the project. If an acronym is used, define the specific meaning of each letter.
* Proponent Secretary – The Secretary to whom the proponent agency is assigned or the Secretary that is sponsoring an enterprise project.
* Proponent Agency – The agency that will be responsible for the management of the project.
* Prepared by – The person(s) preparing this document.
* Date/Control Number – The date the plan is finalized and the change or configuration item control number assigned.
B. Change Control Items – List those components of the project plan governed by this change control process. Change control items include the scope, schedule, budget, and performance Plans.
C. Change Control Process – Describe or diagram the flow of a change request through the change process. Provide a “step-by-step” guide on how changes to the change control items are made.
D. Configuration Management Control Items – Describe the method of selecting each configuration management control items and list the configuration management control items for the project.
E. Configuration Management Control Process – Describe or diagram the process for making configuration changes to configuration management controlled items. Provide a “step-by-step” process on how changes to a configuration management control item are made.
F. Naming and Marking Methods – Describe how documents, components, revisions, and releases are consistently named and marked.
G. Submission and Retrieval of Control Items – Describe the process for submission and retrieval of a controlled item from the Project Repository to prevent the unauthorized modification of the controlled item.
H. Version Control – Define the document version control and release approval procedure. (Version control is not the same as naming and marking methods). Address the release and approval procedures for any new version of a document, software, database, or other similar item under configuration control.
I. Storage, Handling, and Disposition of Project Media - Describe storage, handling, and disposition requirements for project media (both automated and paper). The information in this paragraph is included in the communications plan. Verify there is no conflict in the plans for storage, handling, and disposition of project documentation.
J. Change Management Responsibilities - Identify project stakeholders with specific change management responsibilities. Describe the change management responsibilities of the stakeholders in the second column.
K. Configuration Management Responsibilities - Identify project and configuration team members with configuration management responsibilities. Describe the configuration management responsibilities of the project and configuration team members in the second column.
Got a question about the product? Email us at firstname.lastname@example.org. If you cannot view the preview above this document description, go here to view the large preview instead.
Source: Change and Configuration Management Plan Word document
FlevyPro is a subscription service for on-demand business frameworks and analysis tools. FlevyPro subscribers receive access to an exclusive library of curated business documents—business framework primers, presentation templates, Lean Six Sigma tools, and more—among other exclusive benefits. Click here to learn more about FlevyPro and its benefits.
Change and Configuration Management Plan
Sold by Flevy (view author profile)
Sorry, this document is currently only available to FlevyPro subscribers.
Report this Document
Please explain why the content is inappropriate and provide as much detail as possible. Possible reasons include, but are not limited, to the following:
- Copyright Violation