<PROJECT NAME> PROJECT MANAGEMENT PLAN

Version <1.0> <mm/dd/yyyy>

[Insert appropriate disclaimer(s)]

<Project Name>

VERSION HISTORY
[Provide information on how the development and distribution of the Project Mana ement Plan !emplate was controlled and trac"ed. #se the table below to provide the version number$ the author implementin the version$ the date of the version$ the name of the person approvin the version$ the date that particular version was approved$ and a brief description of the reason for creatin the revised version.%
Version # 1.0 Implemented B <&uthor name> Re!ision "#te <mm/dd/yy> Appro!ed B <name> Appro!#l "#te <mm/dd/yy> Re#son <reason>

UP Template Version: 11/30/06

Page 1 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

Note to the Author

[!his document is a template of a Project Mana ement Plan document for a project. !he template includes instructions to the author$ boilerplate te't$ and fields that should be replaced with the values specific to the project. (lue italici)ed te't enclosed in s*uare brac"ets +[te't%, provides instructions to the document author$ or describes the intent$ assumptions and conte't for content included in this document. (lue italici)ed te't enclosed in an le brac"ets +<te't>, indicates a field that should be replaced with information specific to a particular project. !e't and tables in blac" are provided as boilerplate e'amples of wordin and formats that may be used or modified as appropriate to a specific project. !hese are offered only as su estions to assist in developin project documents- they are not mandatory formats.

.hen usin this template for your project document$ it is recommended that you follow these steps/ 1. 0eplace all te't enclosed in an le brac"ets +e. .$$ <Project 1ame>, with the correct field values. !hese an le brac"ets appear in both the body of the document and in headers and footers. !o customi)e fields in Microsoft .ord +which display a ray bac" round when selected,/ a. 2elect 3ile>Properties>2ummary and fill in the !itle field with the 4ocument 1ame and the 2ubject field with the Project 1ame. b. 2elect 3ile>Properties>5ustom and fill in the 6ast Modified$ 2tatus$ and 7ersion fields with the appropriate information for this document. c. &fter you clic" 89 to close the dialo bo'$ update the fields throu hout the document with these values by selectin :dit>2elect &ll +or 5trl;&, and pressin 3<. 8r you can update an individual field by clic"in on it and pressin 3<. !his must be done separately for =eaders and 3ooters. >. Modify boilerplate te't as appropriate to the specific project. ?. !o add any new sections to the document$ ensure that the appropriate header and body te't styles are maintained. 2tyles used for the 2ection =eadin s are =eadin 1$ =eadin > and =eadin ?. 2tyle used for boilerplate te't is (ody !e't. @. !o update the !able of 5ontents$ ri ht;clic" and select A#pdate fieldB and choose the option; A#pdate entire tableB C. (efore submission of the first draft of this document$ delete this A1otes to the &uthorB pa e and all instructions to the author$ which appear throu hout the document as blue italici)ed te't enclosed in s*uare brac"ets.%

Page 2 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

TABLE O$ CONTENTS
% INTRO"&CTION''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''( 1.1 Purpose of Project Management Plan.................................................................................4 ) E*EC&TIVE S&MMARY O$ PROJECT CHARTER'''''''''''''''''''''''''''''''''''''''''''''''''''''''''( 2.1 Assumptions/Constraints....................................................................................................4 + SCOPE MANAGEMENT''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''( 3.1 Work reak!o"n #tructure................................................................................................4 3.2 $eplo%ment Plan................................................................................................................4 3.3 C&ange Control Management.............................................................................................4 ( SCHE"&LE,TIME MANAGEMENT'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''( 4.1 Milestones...........................................................................................................................' 4.2 Project #c&e!ule.................................................................................................................' 4.2.1 $epen!encies...........................................................................................................' - COST,B&"GET MANAGEMENT''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''. /&ALITY MANAGEMENT''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''0 H&MAN RESO&RCE MANAGEMENT''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''1 COMM&NICATIONS MANAGEMENT''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''(.1 Communication Matri)......................................................................................................' 2 RIS3 MANAGEMENT'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''*.1 +isk ,og.............................................................................................................................' %4 ISS&E MANAGEMENT''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''. 10.1 -ssue ,og........................................................................................................................... %% PROC&REMENT MANAGEMENT'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''. %) COMPLIANCE RELATE" PLANNING''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''. APPEN"I* A5 PROJECT MANAGEMENT PLAN APPROVAL'''''''''''''''''''''''''''''''''''''''''0 APPEN"I* B5 RE$ERENCES'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''1 APPEN"I* C5 3EY TERMS'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''2 APPEN"I* "5 S&MMARY O$ SPEN"ING'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''%4

Page 3 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

%
%'%

INTRO"&CTION
P&RPOSE O$ PROJECT MANAGEMENT PLAN [Provide the purpose of the project charter.% /&e inten!e! au!ience of t&e <Project 1ame> PMP is all project stake&ol!ers inclu!ing t&e project sponsor0 senior lea!ers&ip an! t&e project team.

E*EC&TIVE S&MMARY O$ PROJECT CHARTER

[Provide an e'ecutive summary of the approved project charter. Provide a reference to the approved Project 5harter. :laborate on any sections within the Project 5harter that need further detail contained within the PMP.%

)'%

ASS&MPTIONS,CONSTRAINTS [Dnsert summary of any chan es from the project assumptions and/or constraints that were ori inally outlined in the project charter.%

+
+'%

SCOPE MANAGEMENT
[Dnsert the projectEs scope mana ement plan or provide a reference to where it is stored.% 6OR3 BREA3"O6N STR&CT&RE [Dnsert the projectEs wor" brea"down structure or provide a reference to where it is stored.%

+')

"EPLOYMENT PLAN [:'ample/ !he project involves deployin an application to state health partners. !his section would discuss the approach for rollin out the application to the end users$ includin conductin environment assessments$ developin memorandums of understandin s$ hardware/software installation$ data conversion.%

+'+

CHANGE CONTROL MANAGEMENT [:'ample of 5han e 5ontrol/ Df a development server for your project is administered by another or ani)ation that is responsible for installin machine up rades and there are scheduled outa es that will impact your project schedule. 5han es to the project will need to be made to deal with the potential impact of the scheduled outa e.%

SCHE"&LE,TIME MANAGEMENT
[:'ample of schedule mana ement approach/ :stablish a baseline within the first two wee"s of the project and monitor pro ress a ainst the baseline on a wee"ly basis. !he Project Mana er will be responsible for ensurin the project schedule is updated with the latest information and never more than three business days out of date. 3or variances on e'ecutive milestones reater than 10F$ the project may choose to use uidance specified by 5PD5. 2ee the 545 #P Project 2chedule document for more uidance on project schedules and for Project 2chedule templates.%

Page 4 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

('%

MILESTONES /&e ta1le 1elo" lists t&e milestones for t&is project0 along "it& t&eir estimate! completion timeframe.
Milestones Estimated Completion Timeframe

[Dnsert milestone information +e. .$ Project planned and authori)ed to proceed,% [&dd additional rows as necessary% (') (')'% PROJECT SCHE"&LE

[Dnsert completion timeframe +e. .$ !wo wee"s after project concept is approved,%

[Dnsert the projectEs schedule or provide a reference to where it is stored.% "ependen7ies [Dnsert the schedule/project dependencies +both internal and e'ternal,.%

COST,B&"GET MANAGEMENT
[Dnsert the projectEs cost mana ement plan or provide a reference to where it is stored.%

/&ALITY MANAGEMENT
[:'ample/ 3or an information system$ controllin the consistency of screen layouts would include reviewin all screens to ma"e sure they match the standards. Guality measures may be no bu s or defects for certain critical re*uirements$ consistent screen layouts$ or correctly calculatin variables. Guality may be ensured throu h inspections$ audits$ formal testin and documentation of defects in a defect trac"in system to ensure defects are fi'ed$ retested and closed. 2ome projects may choose to use a traceability matri' to determine if critical re*uirements have been met.%

H&MAN RESO&RCE MANAGEMENT

[Dnsert the projectEs human resource mana ement plan or provide a reference to where it is stored.%

COMM&NICATIONS MANAGEMENT
[Dnsert the projectEs communication mana ement plan or provide a reference to where it is stored.%

1'%

COMM&NICATION MATRI* [Dnsert the projectEs communication matri' or provide a reference to where it is stored.%
Stakeholder Messages Vehicles Frequency Communicators Feed ack Mechanisms

2
2'%

RIS3 MANAGEMENT
[Dnsert the projectEs ris" mana ement plan or provide a reference to where it is stored.% RIS3 LOG
Page 5 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

[!he 0is" 6o is normally maintained as a separate document. Provide a reference to where it is stored.%

%4 ISS&E MANAGEMENT
[Dnsert the projectEs issue mana ement plan or provide a reference to where it is stored.% %4'% ISS&E LOG [!he Dssue 6o is normally maintained as a separate document. Provide a reference to where it is stored.%

%% PROC&REMENT MANAGEMENT
[:'ample/ !his can include information such as ensurin project team members are assi ned computers$ how development and test servers are procured or can o into more detail and include an ac*uisition strate y that details how the project will be staffed +e. .$ performance based fi'ed price contract$ 5D!2 contractors,.%

%) COMPLIANCE RELATE" PLANNING

[Dnsert a list of compliance related processes the project must adhere to. 3or assistance with determinin which compliance processes need to be followed visit http///www>.cdc. ov/cdcup/documentHlibrary/projectHassessment.asp%

Page 6 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

Appendi8 A5 Pro9e7t M#n#:ement Pl#n Appro!#l

/&e un!ersigne! ackno"le!ge t&e% &a2e re2ie"e! t&e <Project 1ame> Pro9e7t M#n#:ement Pl#n an! agree "it& t&e approac& it presents. C&anges to t&is Pro9e7t M#n#:ement Pl#n "ill 1e coor!inate! "it& an! appro2e! 1% t&e un!ersigne! or t&eir !esignate! representati2es. [6ist the individuals whose si natures are desired. :'amples of such individuals are (usiness 2teward$ Project Mana er or Project 2ponsor. &dd additional lines for si nature as necessary. &lthou h si natures are desired$ they are not always re*uired to move forward with the practices outlined within this document.% #ignature3 Print 4ame3 /itle3 +ole3 #ignature3 Print 4ame3 /itle3 +ole3 #ignature3 Print 4ame3 /itle3 +ole3 $ate3 $ate3 $ate3

Page 7 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

APPEN"I* B5 RE$ERENCES
[Dnsert the name$ version number$ description$ and physical location of any documents referenced in this document. &dd rows to the table as necessary.% /&e follo"ing ta1le summari5es t&e !ocuments reference! in t&is !ocument. "o7;ment N#me #nd Version <4ocument 1ame and 7ersion 1umber> "es7ription [Provide description of the document% Lo7#tion <#06 or 1etwor" path where document is located>

Page 8 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

APPEN"I* C5 3EY TERMS

[Insert terms and definitions used in this document. Add rows to the table as necessary. Follow the link below to for definitions of project management terms and acronyms used in this and other documents. http !!www".cdc.go#!cdcup!library!other!help.htm /&e follo"ing ta1le pro2i!es !efinitions for terms rele2ant to t&is !ocument. Term [Insert $erm] [Insert $erm] [Insert $erm] "e<inition [%ro#ide definition of the term used in this document.] [%ro#ide definition of the term used in this document.] [%ro#ide definition of the term used in this document.]

Page 9 of 12 [Insert appropriate disclaimer(s)]

<Project Name>

APPEN"I* "5 S&MMARY O$ SPEN"ING

[Iou may double;clic" on the table to edit it accordin to the information applicable to this project.%
!udget "tem Planning:
!udgetary *esources +utlays

P#$%

P#

C#

!#

!# & %
$ $ -

!# & '
$ $ -

!# & (
$ $ -

!# & )
$ $ -

Total $0.00 $0.00

,e-elopment . "mplementation of Pro/ect:

!udgetary *esources +utlays $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ -

$0.00 $0.00 $0.00 $0.00

Total0 sum of stages: !udgetary *esources +utlays +perations . Maintenance:

!udgetary *esources +utlays

$ $ $ $ $

$ $ $ $ $

$ $ $ $ $

$ $ $ $ $

$0.00 $0.00 $0.00 $0.00 $0.00

Total0 all stages: !udgetary *esources +utlays

1o-ernment FTE cost

P63 Pre2ious 6ear7 C63 Current 6ear7 63 u!get 6ear

Page 10 of 12 [Insert appropriate disclaimer(s)]