Вы находитесь на странице: 1из 9

PROJECT CONFIGURATION MANAGEMENT PLAN TEMPLATE

This Project Configuration Management Template is free for you to copy and use on your project
and within your organization. We hope that you find this template useful and
welcome your comments. Public distribution of this document is only permitted
from the Project Management Docs official website at:
www. P roject M anagement D ocs.com
CONFIGURATION MANAGEMENT PLAN
<PROJECT NAME>
COMPANY NAME
STREET ADDRESS
CITY, STATE ZIP CODE
DATE
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
TA*LE OF CONTENTS
!T"#D$CT#!.................................................................................................................................%
"#&'( )!D "'(P#!(*&T'(.........................................................................................................%
C#!+,$")T#! C#!T"#&..............................................................................................................-
C#!+,$")T#! M)!),'M'!T D)T)*)(' .CMD*/.....................................................................0
C#!+,$")T#! (T)T$( )CC#$!T!,...........................................................................................1
C#!+,$")T#! )$DT(..................................................................................................................2
3
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
INTRODUCTION
The purpose of the Configuration Management Plan is to describe how configuration
management .CM/ will be conducted throughout the project lifecycle. This includes
documenting how CM is managed4 roles and responsibilities4 how configuration item .C/
changes are made4 and communicating all aspects of CM to project sta5eholders. Without a
documented configuration management plan it is li5ely that Cs may be missed4 incomplete4 or
unnecessary wor5 is done because of a lac5 or 6ersion and document control. While a
configuration management plan is important for all projects4 this is especially so for software and
other information technology .T/ projects.
The !e7,en Project will utilize e7isting (mith Company networ5 infrastructure and add
numerous capabilities in order to allow for remote access4 direct ability to modify &)!8W)!
en6ironments4 and impro6ed monitoring of networ5 tools and de6ices. )s a result4 (mith
Company9s ability to perform networ5 maintenance and updates will be significantly impro6ed.
)dditionally4 (mith Company will impro6e its ability to monitor all networ5 diagnostics in real
time and streamline wor5force efficiency. Cost sa6ings will be realized by greatly reducing the
amount of time associated with competing networ5 tas5s and allowing (mith Company
employees to perform wor5 that was pre6iously outsourced.
n order to effecti6ely manage the !e7,en Project4 a coordinated Configuration Management
.CM/ Plan is needed. This plan will establish CM roles and responsibilities and describe how the
!e7,en Project team will trac54 implement4 and communicate configuration items .Cs/ and
changes throughout the project lifecycle.
ROLES AND RESPONSI*ILITIES
"oles and responsibilities is an important part of any plan. n order to communicate a clear
understanding of e7pectations4 these roles and responsibilities must be clearly defined. )ny
wor5 that will be performed as part of the plan must be assigned to someone and this section
allows us to illustrate who owns these tas5s and to communicate them to all project sta5eholders.
The following roles and responsibilities pertain to the CM Plan for (mith Company9s !e7,en
Project.
Configuraion Conro# *oar+ ,CC*-
The CC* is comprised of the !e7,en Project (ponsor4 Project Manager4 Configuration
Manager4 and the &ead 'ngineer for the configuration item .C/ under consideration. The CC*
is responsible for the following:
"e6iew and appro6e8reject configuration change re:uests
'nsure all appro6ed changes are added to the configuration management database
.CMD*/
(ee5ing clarification on any Cs as re:uired
Pro'!( S$on)or
%
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
The Project (ponsor is responsible for:
Chairing all CC* meetings
Pro6iding appro6al for any issues re:uiring additional scope4 time4 or cost
Pro'!( Manag!r
The Project Manager is responsible for:
#6erall responsibility for all CM acti6ities related to the !e7,en project
dentification of Cs
)ll communication of CM acti6ities to project sta5eholders
Participation in CC* meetings
"e;baselining4 if necessary4 any items affected by CM changes
Configuraion Manag!r
The Configuration Manager will be appointed by the Program Management #ffice .PM#/. The
Configuration Manager is responsible for:
#6erall management of the CMD*
dentification of Cs
Pro6iding configuration standards and templates to the project team
Pro6iding any re:uired configuration training
L!a+ Engin!!r)
)ll identified Cs will be assigned to a &ead 'ngineer. The assigned &ead 'ngineer is
responsible for:
Designating a focus group to de6elop the change re:uest
'nsure all change re:uests comply with organizational templates and standards prior to
the CC*
dentification of Cs
Engin!!r)
'ach C will be assigned to a focus group consisting of se6eral engineers. 'ach member of the
focus group will pro6ide input to the change re:uest prior to submitting the change re:uest to the
lead engineer for re6iew and presentation at the CC*
CONFIGURATION CONTROL
Configuration Control is the process of systematically controlling and managing all steps of
configuration throughout the project lifecycle. n order to effecti6ely handle project CM it is
important to use a process which ensures only necessary configuration changes are made.
)dditionally4 li5e any change management efforts4 configuration change decisions must be made
with the understanding of the impact of the change.
The !e7,en Project will use a standardized configuration control process throughout the project
lifecycle in order to ensure all Cs are handled in a consistent manner and any appro6ed changes
are fully 6etted regarding impact and communicated to sta5eholders.
-
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
)s Cs are identified by the project team4 the Configuration Manager will assign a C name and
the C will be entered into the CMD* in an <initiate= status. The C will then be assigned to an
engineer focus group. 'ach member of a Cs focus group will ha6e the ability to access the C
through the CMD*4 ma5e changes and edits4 and enter the C bac5 into the CMD* with a
description of the change8edit annotated in the CMD* log.
t is imperati6e that for any software changes testing is conducted by the focus group in order to
6alidate any changes made. The &ead 'ngineer assigned to manage the focus group is
responsible for ensuring that testing has been conducted4 changes are entered into the CMD*
log4 and that all changes8edits are sa6ed properly into the CMD*. The &ead 'ngineer is also
responsible for assigning new 6ersion numbers and CMD* status for any changes made by
his8her assigned focus group.
Many times a C will ha6e a relationship with one or more other Cs within a project. The &ead
'ngineer4 CM4 and Project Manager will wor5 together to ensure these relationships are fully
understood. The &ead 'ngineer and CM will then be responsible for illustrating these
relationships and co;dependencies in the CMD* to ensure a full understanding of each C and
how they relate to one another.
)ny configuration changes which are identified by the project team or sta5eholders must be
captured in a configuration change re:uest .CC"/ and submitted to the CC*. The CC* will
re6iew4 analyze4 and appro6e8deny the re:uest based on the impact4 scope4 time4 and cost of the
proposed change. f the change is appro6ed4 the project re:uirements will be re;baselined .if
necessary/ and all changes will be communicated to the project team and sta5eholders by the
Project Manager. Denied CC"s may be re;submitted with additional or new information for re;
consideration by the CC*.
CONFIGURATION MANAGEMENT DATA*ASE ,CMD*-
) Configuration Management Database .CMD*/ is where the organizations configuration
information is stored. CMD* is a term which originates from nformation Technology
nfrastructure &ibrary .T&/ which pro6ides a framewor5 for best practices in T ser6ices
management. The CMD* contains not only the configuration information for assets but also
information about the assets such as physical location4 ownership4 and its relationship to other
configurable items .Cs/.
) 5ey component to configuration management is ha6ing a well defined and followed process
for both document and data management.
The CMD* will be the centralized repository for all configuration information for the !e7,en
project. The CMD* pro6ides a common platform for the project team to edit4 change4 re6ise4
and re6iew Cs and also to ensure all documents and data are updated with the latest re6ision and
release formats.
0
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
)ccess to the CMD* will be granted and go6erned by standard $!> permissions. Two types of
CMD* access will be granted for the !e7,en project:
3/ +ull read and write access will be granted to the CM4 Project Manager4 &ead 'ngineers4
and 'ngineers. These indi6iduals will be authorized to access the CMD* to ma5e
changes4 edit documents and data4 and re6iew and appro6e 6ersions and C status.
%/ "ead only access will be granted to the Project (ponsor and all other sta5eholders. This
access will allow these indi6iduals to 6iew all Cs and C data but they will not be
authorized to ma5e any changes. f these indi6iduals identify the need for a change or
edit they will notify the CM who will re6iew the notification and pro6ide feedbac5.
The CMD* will pro6ide assurance that members of the project team are always wor5ing off of
the latest 6ersion of software4 data4 and documentation. ?owe6er4 it is important to maintain the
history of these assets throughout the project lifecycle. )s these assets are changed and updated4
the &ead 'ngineer of the C9s assigned focus group will be responsible for updating the status of
the C and pro6iding new re6ision numbering. This numbering will be done in accordance with
(mith Company9s standard re6ision control numbering process wherein higher 6ersion numbers
indicate more recent 6ersions of the software4 data4 or documentation.
CONFIGURATION STATUS ACCOUNTING
)ccounting for the status of the configuration in6ol6es the collection4 processing4 and reporting
of the configuration data for all Cs at any gi6en time. This also includes management stored
configuration information held in the Configuration Management Database .CMD*/. This may
include appro6ed configuration documents4 software4 data4 and their current 6ersion numbers@
build reports@ status of any submitted changes@ or any discrepancies and status identified through
configuration audits.
t is important that for the !e7,en Project4 the Project (ponsor and Aice President of
Technology ha6e the ability to re6iew configuration status at any gi6en time. The Project
Manager will also submit wee5ly reports4 to include configuration status4 e6ery +riday. These
reports will consist of the following information as part of the configuration status section:
3/ Change re:uests
a. )ging ; ?ow long change re:uests ha6e been open
b. Distribution B number of change re:uests submitted by owner8group
c. Trending B what area.s/ are appro6ed changes occurring in
%/ Aersion Control
a. (oftware
b. ?ardware
c. Data
d. Documentation
1
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
-/ *uild "eporting
a. +iles
b. C relationships
c. ncorporated Changes
0/ )udits
a. Physical Configuration
b. +unctional Configuration
Prior to any new software releases4 the CM will wor5 with each &ead 'ngineer to ensure all Cs
are updated with latest release 6ersions.
CONFIGURATION AUDITS
)udits are an important part of project and configuration management. The purpose of an audit
is to ensure that established processes are being followed as intended and to pro6ide an
opportunity to correct any de6iations from these processes. Many people hold a negati6e 6iew of
audits@ howe6er4 when used appropriately4 audits are an effecti6e management and :uality
assurance tool.
Configuration audits will be an ongoing part of the !e7,en project lifecycle. The purpose of the
configuration audit is to ensure all team members are following the established procedures and
processes for configuration management. Project audits for the !e7,en Project will occur prior
to any major software release or at the Project Manager or (ponsor9s discretion if they determine
the need for one.
)ll !e7,en configuration audits will be performed by the CM. Throughout the project the CM
wor5s closely with &ead 'ngineers to ensure that all configuration processes and procedures are
being followed. )s part of the configuration audit the CM will perform the following tas5s:
3/ 'stablish an audit en6ironment in the CMD*
%/ The CM will copy all of the latest software4 data4 and document 6ersions into the audit
en6ironment
-/ The CM will ensure all 6ersions are correctly numbered and that 6ersion control has been
performed properly
0/ The CM will analyze historical 6ersions and timestamps of all software4 data4 and
documents to ensure all changes8edits were properly recorded and captured
1/ The CM will copy latest software 6ersions and conduct software testing to ensure
re:uirements are being met
2/ The CM will ensure all re:uired artifacts are present and current in the CMD*
C/ The CM will ensure all appro6ed CC"s ha6e been incorporated into the project and are
recorded in the CMD*
#nce the audit has been performed4 the CM will compile his8her audit findings. +or each
finding4 the CM must wor5 with the Project Manager8Team to identify the correcti6e action.s/
necessary to resol6e the discrepancy and assign responsibility for each correcti6e action.
2
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
$pon completion of the project audit and findings4 the CM will note all discrepancies and
compile a report to be presented to the Project Manager4 (ponsor4 and AP of Technology.
C
Configuraion Manag!"!n P#an T!"$#a!
%%%&Pro'!(Manag!"!nDo()&(o"
SPONSOR ACCEPTANCE
)ppro6ed by the Project (ponsor:
DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD Date:DDDDDDDDDDDDDDDDDDDD
EProject (ponsorF
EProject (ponsor TitleF
This free Project Configuration Management Plan Template is brought to you by
www.ProjectManagementDocs.com
G

Вам также может понравиться