Establish policies and processes for controlling product change
Document this information in the Configuration Management Plan (included
in Software Development Plan)
The purpose of having standard, documented change control
processes is to ensure that changes are made within a project in a consistent
manner and the appropriate stakeholders are informed of the state of the
product, changes to it and the cost and schedule impact of these changes.
The CM Plan describe all CM related activities to be performed during the
course of the product/project lifecycle. It documents how product related CM
activities are to be planned, implemented controlled and organized.
How to Staff
The Configuration Manager needs to be an organized soul, and has to be
accountable for all project artifacts. The Configuration Manager needs to ensure
the project policies are enabled for software developers such that artifacts
only go through given gates once they have been approved in accordance with the
defined development practices. The Configuration Manager needs to make sure that
the CM Plan is followed, and that audit reporting is occurring on a regular
basis, and that backups are in safe-keeping offsite, and that software licenses
are maintained up-to-date.
Disciplines >
Configuration & Change Management >
Workflow >
