Configuration Management Plan
The Configuration Management Plan defines the
implementation of configuration management of a particular software project. The
Configuration Management Plan describes the concepts, processes, and procedures for an IT
development project.
What is it?
The Configuration Management Plan provides a framework within which the four primary
Configuration Management functions (configuration identification, configuration control,
status accounting, and audits and reviews) are managed. The CMP documents the plans for
performing configuration management on an IT project.
[Download Sample Chapters]
Who uses it?
Configuration Manager, Development Manager, Project Manager, IT Manager, System
Administrator, Test Manager, Documentation Manager.
When is it used?
The Configuration Management Plan identifies the configuration of a software system at
defined points in order to maintain the traceability of the system configuration
throughout the project.
When is it used?
The acquisition plan is used to analyze the technical options and the lifecycle plans for
development, production, training, and support related items. It also assists IT Managers
and Procurement Officers when making procurement decisions; ensuring the availability of
funding; providing technical evaluation personnel with data for analyzing and evaluating
vendor proposals; ensuring that vendors have adequate information for preparing bids and
adequate information on which to base a selection.
Table of Contents
1 Introduction
1.1 Purpose
1.2 Background
1.3 Document Overview
1.4 Scope
1.5 Benefits
1.6 Reference Documents
1.7 Key Stakeholders
1.8 Sign-Off Criteria
1.9 Points of Contact
2 Configuration Management
2.1 Roles and Responsibilities
2.1.1 Configuration Management Team (CMT)
2.1.2 Configuration Control Board (CCB)
2.1.3 Interface Control
2.1.4 Methodology, Tools, and Techniques
2.2 Resources
2.3 Policies, Directives and Procedures
3 Configuration Management
Tasks
3.1 Configuration Identification
3.2 Configuration Items
3.3 Configuration Item Identifier
3.4 Baseline Management
3.4.1 Functional Baseline
3.4.2 Design Baseline
3.4.3 Development Baseline
3.4.4 Product Baseline
3.5 CM Repositories
3.6 Support Software
3.7 Vendor Control
4 Configuration Control
4.1 Change Control
4.2 Change Classifications
4.3 Change Control Forms
4.4 Problem Resolution Tracking
4.5 System Change Requests
4.6 System Change Requests Priorities
4.7 Configuration Management Libraries
4.8 Release Management
4.9 Version Control
5 Project Management
5.1 Schedule
5.2 Configuration Plan Milestones
5.3 Risks
5.4 Constraints
5.5 Issues
5.6 Assumptions
5.7 Dependencies
6 Project Team
6.1 Roles and Responsibilities
6.2 Responsibilities
6.3 Resources
6.4 Software Tools
7 Configuration Plan
Maintenance
8 Configuration Status
Accounting
8.1 Audit Trail
8.2 Status Summary Reports
9 Configuration Audits and
Reviews
9.1 Functional Configuration Audits
9.2 Physical Configuration Audits
9.3 Peer Reviews
9.4 Tools
10 Archive and Retrieval
11 Training
12 Appendices
12.1 Glossary of Terms
12.2 Acronyms and Abbreviations
Index of Tables
Table 1 Sign-off Criteria
Table 2 Configuration Management Team (CMT)
Table 3 Configuration Control Board (CCB)
Table 4 Schedule
Table 5 Milestones
Table 6 Risks
Table 7 Constraints
Table 8 Issues
Table 9 Assumptions
Table 10 Dependencies
Table 11 Roles and Responsibility
Table 12 Glossary of Terms
Table 13 Acronyms and Abbreviations
Page Count: 26
Download Now - Buy Here!
|
60-day Money-Back Guarantee
Secure Online
Order Form
Supports Windows
98, Me, 2000, 2003, XP, Vista. 
