The Word template can be bought through a template package. Case studies and reports are freely available in the table below.
The purpose of the CM Plan is to define, or reference, the steps and activities that describe how Configuration and Change Control Management is performed in the development of a software product.
The CM Plan is written early in the Elaboration phase once funding has been approved for the project to proceed. We recommend you revisit it at the start of each phase and update it accordingly. The CM Plan needs to be archived so it's available for post-deployment maintenance activities, particularly for guidance on where certain software assets might be stored.
The Role: Configuration Manager is responsible for the integrity of the CM Plan and for ensuring that it covers all of the following:
The Configuration Management Plan contains information that may be covered to a greater or lesser extent by other plans. The following approaches can be used to handle this potential overlap:
The following is a mapping of Configuration Management Plan sections to artifacts that may contain complementary information: