<PROJECT NAME>

CONFIGURATION MANAGEMENT PLAN

Version Number: 1.0
Version Date: <mm/dd/yyyy>
[Insert appropriate disclaimer(s)]
<Project Name>
Notes to the Author
[This document is a template of a Configuration Management Plan document for a project. The template
includes instructions to the author, boilerplate tet, and fields that should be replaced !ith the "alues
specific to the project.
#lue italici$ed tet enclosed in s%uare brac&ets ([tet]) pro"ides instructions to the document
author, or describes the intent, assumptions and contet for content included in this document.
#lue italici$ed tet enclosed in angle brac&ets ('tet() indicates a field that should be replaced
!ith information specific to a particular project.
Tet and tables in blac& are pro"ided as boilerplate eamples of !ording and formats that ma) be
used or modified as appropriate to a specific project. These are offered onl) as suggestions to
assist in de"eloping project documents* the) are not mandator) formats.
When using this template, the ollo!ing steps are recommen"e"#
1. +eplace all tet enclosed in angle brac&ets (e.g., 'Project ,ame() !ith the correct field
document "alues. These angle brac&ets appear in both the bod) of the document and in headers
and footers. To customi$e fields in Microsoft -ord (!hich displa) a gra) bac&ground !hen
selected) select .ile/(Properties/(0ummar) and fill in the appropriate fields !ithin the 0ummar)
and Custom tabs.
1fter clic&ing 23 to close the dialog bo, update all fields throughout the document selecting
4dit(0elect 1ll (or Ctrl/1) and pressing .5. 2r )ou can update each field indi"iduall) b) clic&ing
on it and pressing .5.
These actions must be done separatel) for an) fields contained !ith the document6s 7eader and
.ooter.
2. Modif) boilerplate tet as appropriate for the specific project.
3. To add an) ne! sections to the document, ensure that the appropriate header and bod) tet
st)les are maintained. 0t)les used for the 0ection 7eadings are 7eading 8, 7eading 9 and
7eading :. 0t)le used for boilerplate tet is #od) Tet.
4. To update the Table of Contents, right/clic& on it and select ;<pdate field= and choose the option /
;<pdate entire table=.
5. #efore submission of the first draft of this document, delete this instruction section ;,otes to the
1uthor= and all instructions to the author throughout the entire document.
Configuration Management Plan (1.0! Page 1 of 10
[Insert appropriate disclaimer(s)]
<Project Name>
VERSION HISTORY
[Pro"ide information on ho! the de"elopment and distribution of the Configuration
Management Plan !ill be controlled and trac&ed. <se the table belo! to pro"ide the
"ersion number, the author implementing the "ersion, the date of the "ersion, the name
of the person appro"ing the "ersion, the date that particular "ersion !as appro"ed, and
a brief description of the reason for creating the re"ised "ersion.]
Version
Number
Implemente
!"
Re#ision
$%te
Appro#e
!"
Appro#%l
$%te
$es&ription o'
C(%n)e
1.0 '1uthor name( 'mm>dd>))( 'name( 'mm>dd>))( 'description of change(
Configuration Management Plan (1.0! Page " of 10
[Insert appropriate disclaimer(s)]
<Project Name>
TA!LE OF CONTENTS
1 INTRODUCTION.....................................................................................................................4
1.1 Pur#ose of $%e Configuration Management Plan..............................................4
2 CONFIGURATION MANAGEMENT...................................................................................4
".1 &##roa'%...................................................................................................................4
"." (rgani)ation.............................................................................................................4
".* $raining.....................................................................................................................4
3 CONFIGURATION MANAGEMENT ACTIVITIES..........................................................4
*.1 Configuration +tems.................................................................................................4
*." Configuration +dentifi'ation....................................................................................4
*.* &rtifa't ,ife Cy'le.....................................................................................................5
*.- Configuration Control..............................................................................................5
*.. Configuration &uditing//e#orting..........................................................................5
APPEN$I* A+ CONFIGURATION MANAGEMENT PLAN APPROVAL............................6
APPEN$I* !+ REFERENCES...................................................................................................7
APPEN$I* C+ ,EY TERMS.......................................................................................................8
Configuration Management Plan (1.0! Page * of 10
[Insert appropriate disclaimer(s)]
<Project Name>
- INTRO$UCTION
1.1 PURPOSE OF THE CONFIGURATION MANAGEMENT PLAN
[Pro"ide the purpose of the Configuration Management Plan.]
$%e oerall ob0e'tie of a Configuration Management (CM! Plan is to do'ument and
inform #ro0e't sta1e%olders about CM 2it% t%e #ro0e't3 2%at CM tools 2ill be used3 and
%o2 t%ey 2ill be a##lied by t%e #ro0e't to #romote su''ess. $%e <Pro0e't Name> CM
Plan defines t%e #ro0e't4s stru'ture and met%ods for
+dentifying3 defining3 and baselining 'onfiguration items (C+!
Controlling modifi'ations and releases of C+s
/e#orting and re'ording status of C+s and any re5uested modifi'ations
6nsuring 'om#leteness3 'onsisten'y3 and 'orre'tness of C+s
Controlling storage3 %andling3 and deliery of t%e C+s
$%e intended audien'e of t%e CM Plan is t%e #ro0e't manager3 #ro0e't team3 #ro0e't
s#onsor and any senior leaders 2%ose su##ort is needed to 'arry out 'ommuni'ation
#lans.
. CONFIGURATION MANAGEMENT
./- APPROACH
[Identif) the recommended CM approach (ma&e or bu)). ?ustif) !h) one option !as
selected of the other. If purchasing a CM s)stem, identif) !hich s)stem(s) !ere
recommended as potential options and !h) one !as chosen o"er the others.]
./. ORGANI0ATION
[Identif) items such as ho! CM acti"ities !ill impact the organi$ation, definition of roles
and responsibilities for those in"ol"ed the CM acti"ities and those impacted b) them,
!hat organi$ational policies and procedures ma) be impacted, and an) interfaces
bet!een other organi$ations that ma) impact the CM effort.]
./1 TRAINING
[Identif) the &ind and amount of training necessar) to bring the performing organi$ation
up to speed on !hat configuration management is, an) tools used to perform CM
acti"ities, and !hat, if an), impact CM ma) ha"e on ho! !or& is performed. This ma)
include de"elopment team orientation, tools training, organi$ational a!areness, etc.]
1 CONFIGURATION MANAGEMENT ACTIVITIES
1/- CONFIGURATION ITEMS
[Identif) !hat items !ill and !ill not be placed under CM.]
1/. CONFIGURATION I$ENTIFICATION
[@efine ho! configuration items !ill be identified throughout the CM>Project life c)cle.
This section should define identification schemas for information such asA
Configuration Management Plan (1.0! Page - of 10
[Insert appropriate disclaimer(s)]
<Project Name>
Babeling and numbering documents and files
+elationships bet!een documents and files
1ddressing "ersions and releases
Change Control .orms
Carious baselines for the project (product "ersioning)]
1/1 ARTIFACT LIFE CYCLE
[@efine the artifact life c)cle for the different CIs under CM]
1/2 CONFIGURATION CONTROL
[@efine ho! configuration items !ill be controlled throughout the CM>Project life c)cle.
This section should define procedures for items such asA
Changing baselines
Processing and managing change re%uests and Change Control #oards (CC#s)
Communicating configuration status
Performing configuration audits
#uilding, testing, and debugging !or&spaces
-ho o!ns !hat product code and ho! to appropriatel) !or& !ith that code]
3.5 CONFIGURATION AU$ITING3REPORTING
[@efine ho! configuration items !ill be trac&ed, measured, and reported.]
Configuration Management Plan (1.0! Page . of 10
[Insert appropriate disclaimer(s)]
<Project Name>
Appeni4 A+ Con'i)ur%tion M%n%)ement Pl%n Appro#%l
$%e undersigned a'1no2ledge t%at t%ey %ae reie2ed t%e <Project Name>
Con'i)ur%tion M%n%)ement Pl%n and agree 2it% t%e information #resented
2it%in t%is do'ument. C%anges to t%is Con'i)ur%tion M%n%)ement Pl%n 2ill be
'oordinated 2it%3 and a##roed by3 t%e undersigned3 or t%eir designated
re#resentaties.
[Bist the indi"iduals !hose signatures are desired. 4amples of such indi"iduals
are #usiness 2!ner, Project Manager (if identified), and an) appropriate
sta&eholders. 1dd additional lines for signature as necessar).]
7ignature:
Date:
Print Name:
$itle:
/ole:
7ignature:
Date:
Print Name:
$itle:
/ole:
7ignature:
Date:
Print Name:
$itle:
/ole:
Configuration Management Plan (1.0! Page 8 of 10
[Insert appropriate disclaimer(s)]
<Project Name>
APPEN$I* !+ REFERENCES
[Insert the name, "ersion number, description, and ph)sical location of an)
documents referenced in this document. 1dd ro!s to the table as necessar).]
$%e follo2ing table summari)es t%e do'uments referen'ed in t%is do'ument.
$o&ument N%me $es&ription Lo&%tion
'@ocument ,ame and
Cersion ,umber(
'@ocument description( '<+B or ,et!or& path !here document
is located(
Configuration Management Plan (1.0! Page 9 of 10
[Insert appropriate disclaimer(s)]
<Project Name>
APPEN$I* C+ ,EY TERMS
$%e follo2ing table #roides definitions and e:#lanations for terms and a'ronyms
releant to t%e 'ontent #resented 2it%in t%is do'ument.
Term $e'inition
[Insert Term] 'Pro"ide definition of term and acron)ms used in this document.(
Configuration Management Plan (1.0! Page ; of 10
[Insert appropriate disclaimer(s)]