The configuration management plan (CMP) is a document that can be used to help track changes to project documents, deliverables, and resources over the course of the project life cycle.
The configuration management plan typically includes an itemized list of documents, deliverables, and resources that will change during the project, along with the planned changes to each one throughout the project life cycle. In order to manage a project efficiently, it is important to have a configuration management plan in place. This document will outline how changes to the project's components will be tracked and managed.
The goal of configuration management is to identify project artifacts that can change over time (for example, files or documents), control when they change (that is, record any changes made to those artifacts), determine which ones have changed over time (for example, comparing them at different points in time) and ultimately report on those changes. It is important to remember that the configuration management plan is a living document, and it should be updated as the project progresses.
Why Configuration Management Plan is Needed?
A configuration management plan is an essential component of your project, and if you don’t have one—or worse, it’s non-existent—you could end up in a sticky situation. Plus, more importantly, it can protect you from not only financial liability but also safety issues that could arise should your team be unprepared. It is used generally in
Specifically, it is recommended to be used while planning risk management, doing the project work, managing knowledge, controlling scope of the project and conducting procurements.
When is Configuration Management Developed?
A configuration management plan is created during the project planning phase and outlines how to manage all of your changes throughout development. It is a natural output of develop project management plan process and it is a subplan of the project management plan. Having a well-defined configuration management plan helps ensure that all stakeholders have a clear understanding of how the project's configurations will be managed, and that changes are made in a coordinated and consistent manner.
The Components of Configuration Management Plan
It doesn’t need to be complicated or lengthy—it just needs to cover what information needs to be collected; who will gather it; how often; where it will be stored (this varies between companies); and whom each piece of information must be approved by before going into production. It also includes a process for approving or denying changes based on pre-determined criteria such as: compliance with standards, testing requirements and schedule restrictions.
The configuration management plan should include the following:
- A description of the project's components,
- How changes to these components will be tracked,
- Who can request changes, how they are prioritized,
- Who will be responsible for each type of change?
- What tools and processes will be used?
- The approval process for changes