Configuration Management is concerned with identifying, tracking and protecting a project’s deliverables or products from unauthorised change. The term originates from the software industry, where it was used to keep control of the various versions of programs and other files of data that were created during the course of a software development initiative. In most Programmes, management products such as the Vision Statement, the Business Blueprint and the Programme Plan are examples of documents requiring the application of Configuration Management. Project Briefs, Project Initiation Documents (PID), Business Cases, Checkpoint and Highlight Reports are examples of project documentation that usually require some form of Configuration Management.
For more information please follow the links provided.
|Purpose||Sources||Roles and Responsibilities|