Configuration Management and Change Control   Configuration Management and Change Control are concerned with managing the actual changes of a programs baseline documents, schedules, or cost. Configuration Management and Change Control Checklist Develop a Configuration Management Plan. The Configuration Management plan defines the program's application inventory and establishes the approved configuration baseline. The plan ensures that each document or software under its control can be reproduced and used to create or modify executable code or documents such as specifications and plans. Develop a Change Management Plan. Develop a change management plan that manages each request for change. The plan should keep the scope of the project under control and fully traceable. The plan should: Have project stakeholders assess each request for change Ensure each assessed change request is accepted (or rejected or deferred) by the appropriate authority Enable the orderly implementation of each accepted change Allow the impact of all changes to be understood, documented, and managed Obtain Baseline Change Approvals. Obtain the designated approvals identified on the Project Initiation Form (PIF) prior to changing the program plan baseline. Provide a description of the proposed baseline change and the reason for the change. The project should establish a configuration control board (CCB) to review the baseline and proposed changes The CCB should represent all affected parties, including representatives from other baseline CCBs and groups that use configuration items changed/deleted by this baseline. The CCB primarily should be drawn from application development and system support (data center) personnel. Maintain Project Archives. Maintain records for all contract documents, approved changes to contract documents, or statements of work, invoices, status reports, and project deliverables.