Project Configuration Management Plan Template
Project Configuration Management Plan Template
Contents of this document are proprietary and may not be distributed without the prior written consent of <Consultant> and <Client Name>.
Charlotte-Mecklenburg Schools – Managing for Performance Project Configuration Management Plan
Table of Contents
1 Introduction........................................................................................................................... 2
1.1 Purpose.......................................................................................................................... 2
1.2 Scope............................................................................................................................. 2
1.3 Definitions....................................................................................................................... 2
1.4 References..................................................................................................................... 2
2 Management......................................................................................................................... 2
2.1 Roles and Responsibilities..............................................................................................2
2.2 Milestones...................................................................................................................... 3
2.3 Applicable Policies, Directives and Procedures..............................................................3
3 Configuration Identification....................................................................................................3
3.1 Conventions....................................................................................................................3
3.2 Baselines........................................................................................................................ 4
3.2.1 Baseline 1................................................................................................................4
3.2.2 Baseline 2................................................................................................................4
3.2.3 Time-shift................................................................................................................. 4
4 Configuration Control............................................................................................................4
4.1 Access Rights................................................................................................................. 4
4.2 Root Folders...................................................................................................................5
4.3 Document Control...........................................................................................................5
4.4 Code Control................................................................................................................... 5
4.5 Media Control................................................................................................................. 5
4.6 Change Control...............................................................................................................5
4.6.1 Levels of Authority....................................................................................................5
4.6.2 Change Procedures.................................................................................................6
4.6.3 Review Board...........................................................................................................6
4.6.4 Interface Control.......................................................................................................6
4.6.5 Support Software Change Procedures.....................................................................6
5 Configuration Status Accounting...........................................................................................6
6 Tools Techniques and Methods for SCM..............................................................................6
7 Supplier Control.................................................................................................................... 6
8 Records Collection and Retention.........................................................................................6
Appendix A - Definitions.............................................................................................................. 7
Appendix B - References............................................................................................................. 8
Appendix C - Configuration Items................................................................................................9
1 Introduction
1.1 Purpose
Application configuration management is the discipline of applying technical and administrative
direction and administration to:
Identify and document the functional and physical characteristics of a configuration item
Control changes to those characteristics
Record and report change processing and implementation status
Verify compliance with specified requirements
This document describes how this discipline will be applied to the <Clinet Org.> <Project Name>
Project.
1.2 Scope
This document applies to all configuration items as defined in Appendix C. In general, any
document, set of files or system configurations can be considered to be under control of this
plan, and therefore, in scope.
1.3 Definitions
Please refer to Appendix A, for a list of definitions and terms.
1.4 References
Please refer to Appendix B, for a list of references.
2 Management
Role Responsibility
Project Manager Develop the Configuration Management Plan
Work with the Software Librarian to manage and execute this plan
Software Librarian Manage all configuration items as defined within this plan
Provide procedures and processes for project team members to
facilitate execution of this plan
manage the configuration management library
train project team members on configuration management processes
resolve configuration management problems
report status to the Project Manager
Role Responsibility
DBA Support Provide and maintain configuration definitions for databases used by
the project
IT Operations Lead Maintain the media from the vendor in an organized manner
System Support Provide and maintain configuration definitions for systems used by
the project
Provide regular backup of all project assets under configuration
management
Technical Analyst Apply the appropriate configuration management policies and
procedures as they apply to the documents, scripts and code that the
analyst is responsible for.
1.6 Milestones
Milestone Description
CM Plan Adopted This plan will be accepted as ready for application and is put into practice.
CM Environment Ready The CM Environment is fully defined and ready to be put into service.
Baselines Established The baseline application environment is in Production and captured and
under control in the CM Environment.
Release of Product The latest version of the application environment has been deployed to
Production, and a new baseline has been established in the CM
Environment.
3 Configuration Identification
1.8 Conventions
<Naming conventions for CI’s>
1.9 Baselines
3.1.1 Baseline 1
Testing of the existing system prior to remediation to prove the test scripts exercise the system
sufficiently to prove functionality of the system
3.1.2 Baseline 2
Testing of the system after remediation to ensure that functionality of the system has not been
impaired by the remediation.
3.1.3 Time-shift
Testing of the system through each of the Y2K defined date events that are significant to the
system.
4 Configuration Control
All documents and code within the scope of
configuration management will be maintained in
the version control system (VCS). The version
control system for this project will be <Microsoft
Visual SourceSafe (VSS); Team Foundation
Server; other>.
All user accounts will have Read permissions to all folders. They will have Read, Check-
In/Check-Out, and Add/Delete Privileges for folders as required by their roles in the project
team.
Code This folder, and its sub-folders is intended to hold SQL Server test objects.
Documents This folder and its sub-folders is intended to hold project documents such as test plans,
manual test scripts and other related documents.
Sites This folder and its sub-folders is intended to hold site specific documents such as test
plans, manual test scripts and other related documents
Public This folder will be set up with a shadow folder on <Server Name>. The shadow folder
will be visible to all domain members of trusted domains of the <TBD> domain such as
_______. The intent is to allow non VSS users to view project documents that are
The process for managing the environments that support each state, and the conventions for
promoting (deploying) code from one state to another, is described in another document(s).
Tapes, disks and documents provided by AspenTech will be managed by the IT Lead. These
items shall remain in the <TBD Ops Team environment> , available to the project. The
Software Librarian is responsible for receiving and logging the receipt of new copies of these
items before handing them over to the IT Lead.
Final distribution of production tapes will be executed as per <TBD Ops Team> Technical
Services procedures.
Tool Description
Microsoft Office 2007 Microsoft suite of products consisting of: Word, Excel, PowerPoint
and Access for the creation and maintenance of documents.
Microsoft Project 2007 Microsoft project management software
Microsoft Team A Microsoft Visual Studio Suite team collaboration platform that
Foundation Server combines team portal, version control, work-item tracking, build
management, process guidance, and business intelligence into a
unified server.
Microsoft Visual Studio Database Edition helps you manage database change. It supports
Database Edition database deployment, database change management, database
testing, and database test data generation.
Sybase PowerDesigner PowerDesigner combines several standard modeling techniques
(UML, Business Process Modeling and market-leading Data
Modeling) together with leading development platforms, such as
.NET, WorkSpace, PowerBuilder, Java and Eclipse, to bring
business analysis and formal database design solutions to the
enterprise.
7 Supplier Control
Appendix A - Definitions
CMI Configuration Management Item
Any object of item which is considered within scope of this plan
CMP Configuration Management Plan
Appendix B - References
1. Retention policy
2. <XYZ> document memo