Project Management Plan Template

This document is an annotated outline for a Project Management Plan, adapted from the PMI Project Management Body of Knowledge (PMBOK) and I !tandard for Project Management Plans" The Project Management Plan is considered to #e a $Best Practice% template #y the T! nterprise Program Management Office ( PMO)" The template is designed to address items for all si&es of projects" 'or small projects, it may #e appropriate to omit sections" 'or uni(ue projects, you may need to add sections" Tailor as appropriate" )here you decide to omit a section, you might *eep the header, #ut insert a comment saying why you omitted the element" + suggested method is to lea,e the header and place the comment $-ot +pplica#le%" This demonstrates you ha,e thought through the project" Items in italic red te.t should #e remo,ed and replaced with your project wording" The items in italic red are remar*s designed to e.plain and gi,e guidance on what should #e in that section" If you ha,e a document already addressing a section, reference that document and where that document resides" -ote /0 The Project Management Plan guidelines were deri,ed and de,eloped from I !tandard /123"/ !tandard for Project Management Plans (+-!I) and the PMI Project Management Body of Knowledge (PMBOK)" -ote 40 The ordering of Project Management Plan elements is not meant to imply that the sections or su#sections must #e de,eloped or presented in that order" The order of presentation is intended for ease of use, not as a guide to preparing the ,arious elements of the Project Management Plan"

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page / of 47

45/4541/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

(Agency) (Project) Project Management Plan

Version: (n)

Date: (mm/dd/yyyy)

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 4 of 47

45/4541/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

Document History and Distribution

1. Revision History
Revision # /"1 Revision Date 13541518 Description of Change Initial 9ocument Author +" :utler

2. Distri !tion
Recipient Name Recipient Organization Distribution Method

".

Plan A##rovers
Identify the plan approvers. List the name, signature and date the plan was approved. Approver Name Approver Signature Approval Date Approval roup !epresented

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page ; of 47

45/4541/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan Approver Name Approver Signature Approval Date Approval roup !epresented

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 8 of 47

45/4541/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

$A%&' () *(+$'+$,

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page / of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

"# $%ecutive Summary

The .ecuti,e !ummary of the Project Management Plan pro,ides an o,er,iew of the project and the product, a list of deli,era#les, reference material, and agency definitions and acronyms used throughout the <ife :ycle of the project"

Project Overview
Provide a concise summary of the project objectives, scope, out of scope, the product to be delivered, major work activities, major work products, major milestones, required resources, and master high level schedules and budget requirements. !he Project "verview describes the relationship of this project to the agency mission, other projects, and business impact.

Scope
#efine the work that must be completed to deliver the product or service with the specified features and functions. $%ample &' (odifications to software as stated in the requirements document approved on ))*))*)). $%ample +' !his is a new web application requiring hosting at ,,, agency.

Out Of Scope
#efine the work outside of this project. $%ample &' $%ternal interface modifications will not be part of this project but will be addressed with future projects. $%ample +' !his project is already being hosted by ,,, agency and does not havee any additional hosting requirements.

Project Deliverables
Below is a list of artifacts to #e deli,ered to the customer or deli,ered to the PMO for project certification. Based upon the si-e of your project .small, medium, or large/ you will decide which artifacts are relevant to your project 0ot all projects will create all of the artifacts listed. If you have additional items, add them to the list. (ark the column appropriately to indicate if your project will or will not be producing
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page 4 of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan the artifact.

A!T&'A(T
+gency !ystems 9e,elopment <ife :ycle Methodology (!9<:) +pplication Technical +rchitecture Budget Build ,s" Buy +nalysis for !oftware Business :ase Business 'unctional =e(uirements :hange :ontrol Process :ommunication Plan :onfiguration Management Plan :ritical !uccess 'actors 9eli,era#le +cceptance :riteria 9isaster =eco,ery 5 Business :ontinuity Plan >ardware Procurement <ist Issue <og <essons <earned Maintenance ? !upport Plan Organi&ational Brea*down !tructure Performance 5 !cala#ility Test Plan Practices ? Techni(ues Project :harter Project Management Plan Project Milestones Project !chedule Project !uccess Measurements Project Test Plan @uality +ssurance Plan
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page ; of 47

)es * No

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

A!T&'A(T
=egression Test Plan =is* +ssessment 5 Profile =oles ? =esponsi#ilities !ecurity +rchitecture !er,ice le,el +greements !oftware 9eployment Plan !oftware Procurement <ist !oftware Aser 9ocumentation !oftware Berification ? Balidation Plan !O) (!tatement of )or*) !taffing Plan Tas* stimates Training Plan A+T Test Plan Anit Test Plan )or* Brea*down !tructure ()B!)

)es * No

Project Management Plan Updates

The Project Management Plan will #e created and maintained using standard ,ersion control processes" Page; of this document outlines the 9ocument >istory, 9istri#ution <ist, and Plan +ppro,ers"

Definitions and Acronyms

+ list of terms and agency acronyms used for this project are listed in the $Clossary of Terms% in !ection 3 of this document" Please add any terms unique to your project to the 1lossary of !erms.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 8 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

+# Project ,rgani-ation
#escribes the project organi-ational structure, identifies organi-ational boundaries and interfaces, and defines individual responsibilities for the various project elements.

Organizational Structure
#escribes the internal management structure of the project. 1raphical devices such as hierarchical organi-ation charts or matri% diagrams may be used to depict the lines of authority, responsibility, and lines of communications within the project. 2how an organi-ational chart for each agency, team, or consultants involved with the project.

Organizational Boundaries and nterfaces

If your project involves more than one team, another agency, or consultants it is important to describe the boundaries of each of those organi-ations. !he establishment of boundaries early in the project will give guidance to all teams working on the project and promote clear communication. #escribe the administrative and managerial boundaries between the project and the following entities' the agency, the custom organi-ation, subcontracted organi-ations, quality assurance, or any other organi-ational entity interfacing with the project.

!oles " !esponsibilities

Briefly describes the responsibilities of project team members. 3 matri% of functions and activities versus responsible individuals may be used to depict project responsibilities. 3n e%ample of the 4oles 5 4esponsibilities template 5 436I template is listed below.

"Roles & "RACI Template Responsibilities Template 20040722.doc" 20040722.xls"

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 2 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

.# Management Process
!his section describes project assumptions, dependencies, and constraints, risk management techniques, monitoring and control practices, staffing plan, communication plan, and escalation procedures.

Assumptions# Dependencies# and $onstraints

!his section will state the assumptions on which the project is based, the e%ternal events the project is dependent upon, and the constraints under which the project is to be conducted. 3ssumptions DDD

#ependencies DDD

6onstraints DDD

!is% Management
Identify and assess the risk factors associated with the project. #escribe the prescribed mechanisms for tracking the various risk factors .e.g., 2elf 3ssessment and risk statistical analysis .43(P/ and implementing contingency plans. 4isk factors that should be considered include contractual risk, technology risk, si-e and comple%ity risks, personnel acquisition and retention risks, and risks to achieving customer acceptance of the product.

Monitoring and $ontrol Mec&anisms

$%plains the reporting mechanisms, report formats, information flows, review and audit mechanisms, and other tools and techniques to be used in monitoring, tracking, and controlling adherence to the Project (anagement Plan. !he relationship of monitoring and control mechanisms to project support functions .e.g., I!2, $P("/ shall be delineated in this section. #etail the schedule and use of the $P(" Project 2tatus 4eport .attached as 2ection
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page E of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan ) 3ppendices/.

Staffing Plan
2pecify the numbers and types of personnel required to conduct the project. .!his includes staffing requirements from your team, vendors, contractors or outside agencies if the information is obtainable./

$ommunication Plan
#escribe the communication plan to be used during the project. 3lso describe the frequency of planned meetings needed for the project. 3n e%ample of a 6ommunication Plan, (eeting (inutes document, Issue Log, 2tatus 4eport 5 2ign in 2heet are listed below. #escribe how these and other documents will be used to properly communicate meetings, report distributions, issues, risk management and project status to various people associated with the project.
"Communication Plan "Meetin Minutes "Issue !o Template ""ee#l$ P%o&ect Template 2004.08.27.doc" Template 20040722.doc" 20040722.xls" 'tatus Repo%t Template 20040722.doc"

"'i n In '(eet Template 2004.08.20.doc"

'scalation Procedures
#escribe the escalation procedures to be used during the project.

/# Tec0nical Process
#escribes the technical methods, tools, and techniques to be used on the project. In addition, the plan for software documentation shall be specified, and plans for project support functions such as quality assurance, configuration management, and verification and validation shall be identified.

Met&ods# (ools# and (ec&ni)ues

2pecifies the computing system, development methodology, team structure, programming language, and other notations, tools, techniques, and methods
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page F of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan to be used to specify, design, build, test, integrate, document, deliver, modify, or maintain the project deliverables. In addition, the technical standards, policies, procedures, and guidelines governing development shall be included or by reference to other documents.

Arc&itecture Plan
4eference the 3rchitecture Plan by specifying or attaching a copy of the 3rchitecture Plan document.

Software Documentation
2pecify directly, or by reference, the documentation plan for the software portion of the project. !he documentation plan shall specify configuration management and version control requirements along with storage and media requirements.

*ardware Documentation
2pecify the hardware needed to support the application in production.

Security
2pecify security requirements needed to support the application. 3lso specify security requirements needed to access the application.

Project Support +unctions

!his section shall contain, either directly or by reference, plans for the supporting functions of the software project. 2upporting functions include .but may not be limited to/' 6onfiguration management, 2oftware quality assurance, 7erification and validation plans, Production support and operational support functions.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 3 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

1# 2or3 Pac3ages4 Sc0edules4 and 5udget

!his section of the Project (anagement Plan will specify the work packages, identify the dependency relationships among them, state the project resource requirements, provide the allocation of budget and resources to work packages, and establish a project schedule.

,or% Pac%ages
!his subsection will define the work packages .work breakdown structure .8B2// for the activities and tasks that must be completed in order to satisfy the project agreement. $ach work package must be uniquely identified9 identification may be based on a numbering scheme and descriptive title. 3 diagram depicting the breakdown of activities .1antt 6hart/ may be used to depict a hierarchical relationship among work packages.

Dependencies
!his section will state the ordering relations among work packages to account for interdependencies among them and dependencies on e%ternal events. !echniques such as dependency lists, activity networks, and the critical path method may be used to depict dependencies among work packages.

!esource !e)uirements
Identifies, as a function of time, estimates of total resources required to complete the project. 0umbers and types of personnel, computer time, hardware, software, office facilities, travel, training, and maintenance requirements are typical resources that should be specified.

Budget !e)uirements
Identifies, as a function of time, estimates of total budget dollars required to complete the project.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 7 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

Budget and !esource Allocation

2pecify the allocation of budget and resources to the various project functions, activities, and tasks.

Sc&edule
2pecify the schedule for the various project functions, activities, and tasks, taking into account the precedent relations and the required milestone dates. 2chedules may be e%pressed in absolute calendar time or in increments relative to key project milestones.

6# Project Success (riteria

#escribes the project milestones and checkpoints, key deliverables, acceptance criteria, and management approval process for project and product deliverables.

-etwor% Diagram
!his subsection will define the project network diagram, including the critical path. !he network diagram may be included as an 3ppendi%.

Project Milestones
!his section will identify the project milestones. 3 milestone is a clearly identifiable point in time that summari-es the completion of a related or important set of tasks .e.g., design, testing/. (ilestones are commonly used as a reference point or summary of important events in a project.

Approval Process
Identifies the management process for obtaining approval of project deliverables, as well as any :go: * :no go: decision points in the project. !his should also include any approvals needed from anyone outside the agency or group. !he approval process should also outline the gate decision process for the :go: * :no go: decision points in the project.

Acceptance $riteria
Identifies the customer acceptance criteria for project implementation.
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page /1 of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

$ritical Success +actors

#escribes critical success factors .such as within budget, on schedule, &;;< functionality/ identified by the client as well as the project quality goals. Identify and quantify all project goals. Prioriti-e the project goals' cost, schedule, or functionality.

7# Data (onversion * Data Migration

!his section will describe how data will be converted or migrated to production prior to the application being deployed into production.

8# Test Strategy
!his section will describe how =nit !esting, >unctional !esting, 2ystem !esting, =ser 3cceptance !esting, 4egression !esting, and Performance * 2calability !esting will be accomplished. !he test strategy should also include #ata 7erification.

Unit (esting +unctional (esting System (esting User Acceptance (esting !egression (esting Performance . Scalability (esting Data /erification

9# Deployment Plan
!his section will describe how the product will be deployed into production.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page // of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

":# System Transition * !ollout Plan

!his section will describe the knowledge transfer needed for software components, hardware components, and transition knowledge from developer to maintenance support.

""# Training Plans

!his section will describe

"+# Procurement Plans

!his section will describe how hardware, software, license, or any components will be procured for the project. !he items may be procured by purchase, leased, or borrowed.

".# Maintenance ; Support Plans

!his section will describe how the product will be maintenanced 5 supported. 3ll access requirements needs to be addressed here.

"/# Additional (omponents

6ertain additional components may be required. !hese may be included by appending additional sections to the Project (anagement Plan. 3dditional items of importance may include subcontractor management plans and 2L3?s.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page /4 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

"1#

lossary o< Terms

(A- -D'0 O! 12OSSA!3 O+ ('!MS O! A$!O-3MS# US'D (*!OU1*OU( (*' P!O4'$( MA-A1'M'-( P2A- S OP( O-A2 BU( !'$OMM'-D'D (O MP!O/' USAB 2 (3 A-D P!O/ D' D'+ - ( O-S O+ $OMMO('!MS US'D (*!OU1*OU( (*' S3S('M D'/'2OPM'-( 2 +' $3$2'56

A Acceptance $riteria ) T(e list o* %e+ui%ements t(at must be satis*ied p%io% to t(e custome% acceptin deli,e%$ o* t(e p%oduct. Acceptance (est ) -o%mal use% pe%*o%med testin pe%*o%med p%io% to acceptin s$stem .sometimes called client acceptance test o% use% acceptance test/. t(e

Ac)uisition ) 0ene%ic te%m *o% (a%d1a%e2 so*t1a%e2 o% se%,ices ac+ui%ed *%om an outside ,endo% o% cont%acto%. Action Plan 3 A plan t(at desc%ibes 1(at needs to be done and 1(en it needs to be completed. P%o&ect Mana ement Plans a%e action plans. Activity 3 A speci*ic p%o&ect tas#2 o% %oup o* tas#s2 t(at %e+ui%e %esou%ces and time to complete. Adaptive System ) 4esc%ibes so*t1a%e t(at (as *lexibilit$ as t(e p%ima%$ desi n point. Application ) 0ene%ic te%m *o% a p%o %am2 o% s$stem2 t(at (andles a speci*ic business *unction. Application Software ) A complete2 sel*3contained p%o %am t(at can pe%*o%m 1o%# *o% a use%. T(is is in cont%ast to s$stem so*t1a%e suc( as an ope%atin s$stem2 se%,e% p%ocesses2 and lib%a%ies t(at exist in suppo%t o* application so*t1a%e. Approval $ycle ) P%ocess o* ainin *undin and mana ement app%o,al p%io% to p%o&ect initiation. Arc&itecture ) Imposes o%de% and ma#es inte%connections possible. 0ene%all$ de*ined as an inte%mediate step bet1een initial %e+ui%ements and business *unctional speci*ications du%in 1(ic( t(e enti%e complex o* (a%d1a%e2 so*t1a%e2 and desi n conside%ations a%e ,ie1ed as a 1(ole. Re*e%s to a bluep%int *o% e,ol,in a tec(nical in*%ast%uctu%e. Assessment ) A ene%al te%m *o% t(e *o%mal mana ement %e,ie1 o* a p%ocess. Audit 3 A *o%mal and detailed examination o* t(e p%o %ess2 costs2 ope%ations2 %esults2 o% some ot(e% aspect o* a p%o&ect o% s$stem pe%*o%med b$ an independent pa%t$.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page /; of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

Availability T(e po%tion o* time t(at a s$stem t(at is sc(eduled to ope%ate actuall$ can be used as expected.

Clossary of TermsG (continued)

% Bac%bone ) A (i (3speed compute% net1o%# desi ned to inte%connect lo1e%3speed net1o%#s o% cluste%s o* dispe%sed use% de,ices. Baseline ) A speci*ication2 o% p%oduct2 t(at (as been *o%mall$ a %eed upon 1(ic( se%,es as t(e sta%tin point a ainst 1(ic( p%o %ess 1ill be &ud ed. Baseline Plan 3 T(e initial app%o,ed plan to 1(ic( de,iations 1ill be compa%ed as t(e p%o&ect p%oceeds. A 1o%# p%oduct t(at (as been *o%mall$ app%o,ed and t(at can be c(an ed onl$ t(%ou ( *o%mal c(an e cont%ol p%ocedu%es. Batc& ) A te%m desc%ibin a met(od o* ope%atin compute%s. T(is met(od ta#es %oups o* t%ansactions2 executes t(em2 and %etu%ns t(e %esults2 all 1it(out (uman inte%,ention. Benc& Mar% ) A standa%d *i u%e o* me%it 1(ic( measu%ements o% compa%isons ma$ be made. Bridge ) 4e,ices t(at connect t1o sepa%ate net1o%#s. 5nce b%id in is accomplis(ed2 t(e b%id e ma#es inte%connected net1o%#s loo# li#e a sin le net1o%#. Budget ) A planned se+uence o* expenditu%es o,e% time 1it( costs assi ned to speci*ic tas#s and acti,ities. * $AS' ) *om#!ter Aided ,o-t.are 'ngineering 3 '$stems t(at attempt to automate some o% all o* t(e tas#s in,ol,ed in mana in 2 desi nin 2 de,elopin 2 and maintainin so*t1a%e s$stems. $&ange Management ) T(e *o%mal p%ocess o* %eco%din 2 anal$6in 2 estimatin 2 t%ac#in and %epo%tin o* c(an es to t(e p%o&ect baseline business *unctional %e+ui%ements. $&ec%point ) A point in t(e de,elopment p%ocess at 1(ic( p%o&ect state2 status2 and %esults a%e c(ec#ed2 %eco%ded2 and measu%ed. $lient.Server System ) P%ima%il$ a %elations(ip bet1een p%ocesses %unnin on sepa%ate mac(ines. A client initiates t(e dialo b$ sendin %e+uests to t(e se%,e% as#in *o% in*o%mation o% action. $onfidence 2evel 3 A le,el o* con*idence2 stated as a pe%centa e2 *o% a bud et o% sc(edule estimate. T(e (i (e% t(e con*idence le,el2 t(e lo1e% t(e %is#.
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page /8 of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

$onfiguration Management ) Met(odical sto%a e and %eco%din components and deli,e%ables du%in de,elopment.

o* all so*t1a%e

$onnectivity ) Re*e%s to t(e abilit$ to send and %ecei,e in*o%mation bet1een locations2 de,ices2 and business se%,ices.

Clossary of TermsG (continued)

$ontingency Plan 3 An alte%nati,e *o% action i* t(e p%o&ect does not p%oceed acco%din to plan o% i* t(e expected %esults a%e not ac(ie,ed. $ontrol H A p%ocess *o% assu%in t(at %ealit$2 o% actual pe%*o%mance2 meets expectations o% plans. $ooperative Processing ) Computin t(at %e+ui%es t1o o% mo%e distinct p%ocesso%s to complete a sin le t%ansaction. $ost . Benefit Analysis ) A *o%mal stud$ in 1(ic( t(e de,elopment2 execution2 and maintenance costs *o% a p%o&ect a%e matc(ed a ainst t(e anticipated ,alue o* t(e p%oduct. $ritical Activity 3 A tas#2 acti,it$2 o% e,ent t(at2 i* dela$ed2 1ill dela$ anot(e% impo%tant e,ent 3 p%obabl$ t(e completion o* t(e p%o&ect o% a ma&o% milestone in t(e p%o&ect. $ritical Pat& ) 4e%i,ed *%om t(e P7RT met(od2 t(is te%m implies t(e set o* acti,ities t(at must be completed in se+uence and on time i* t(e enti%e p%o&ect is to be completed on time. A missed tas# on t(e c%itical pat( 1ill cause a p%oduct deli,e%$ dela$. T(is is t(e lon est time *o% t(e p%o&ect *%om be innin to end. $ritical Pat& Met&od 7$PM6 3 5ne o* t(e t1o most common *o%ms o* net1o%#in s$stems. CPM uses a one3time estimate *o% c%eatin a p%o&ect sc(edule. $ustomer 3 T(e indi,idual o% o% ani6ation t(at speci*ies and accepts t(e p%o&ect deli,e%ables. D Data ) 4esc%ibes t(e numbe%s2 text2 %ap(ics2 ima es2 and ,oice sto%ed in a *o%m t(at can be used b$ a compute%. Data ,are&ouse ) "(e%e $ou consolidate and sto%e data *%om man$ sou%ces. Deliverable ) A tan ible2 p($sical ob&ect t(at is t(e output o* a so*t1a%e de,elopment tas#.
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page /2 of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

Dependency Diagram 3 Anot(e% name *o% a net1o%# o% p%ecedence dia %am t(at s(o1s t(e dependencies amon tas#s. Design ) T(e tas#s associated 1it( speci*$in and s#etc(in t(e *eatu%es and *unctions o* a ne1 application p%io% to codin . Development Project ) T(e sum o* all tas#s and acti,ities necessa%$ to build a so*t1a%e p%oduct. Document of Understanding ) A *o%mal a %eement bet1een t1o pa%ties. A cont%act t(at is sometimes %e*e%%ed to as a 'tatement o* "o%# .'5"/.

Clossary of TermsG (continued)

Documentation ) T(e p%inted and displa$ed mate%ials t(at explain an application to a use%. Duration 3 T(e pe%iod o* time o,e% 1(ic( a tas# ta#es place. 4u%ation establis(es t(e sc(edule *o% a p%o&ect. ' 'ffectiveness 3 A measu%e o* t(e +ualit$ o* attainment in meetin ob&ecti,es. 'fficiency 3 A measu%e o* t(e ,olume o* output %ecei,ed *o% t(e input used. 'ffort 3 T(e amount o* 1o%# o% labo% .in (ou%s o% 1o%#da$s/ %e+ui%ed to complete a tas#. 'nvironment ) T(e set o* tools and p($sical su%%oundin s in 1(ic( so*t1a%e is de,eloped. 'PMO 8 7nte%p%ise P%o&ect Mana ement 5**ice. 'stimate ) A p%edicted total o* expenditu%es %e+ui%ed to complete a tas#2 acti,it$2 o% p%o&ect. '9it $riteria ) T(e set o* conditions t(at must be met p%io% to completin a p%o&ect p(ase o% application. ) +easibility Project ) A p%o&ect desi ned to p%o,e2 o% disp%o,e2 t(e app%op%iateness o* t(e tec(nolo $ solution unde% existin const%aints .sometimes called 8p%oo*3o*3concept9 p%o&ect/. +loat 3 T(e amount o* time *o% a tas# to be *%eel$ sc(eduled 1it(out a**ectin ot(e% tas#s in t(e p%o&ect.
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page /E of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

+unction 3 An acti,it$ t(at spans t(e enti%e du%ation o* a so*t1a%e p%o&ect .e. .2 status %epo%tin 2 +ualit$ assu%ance2 ,e%i*ication and ,alidation/. / 1antt $&art ) A met(od o* displa$in o,e%lapped and pa%tiall$ concu%%ent acti,ities b$ usin (o%i6ontal lines to %e*lect t(e time %e+ui%ed b$ eac( acti,it$. T(e c(a%t2 named *o% :en%$ !a1%ence 0antt2 consists o* a table o* p%o&ect tas# in*o%mation and a ba% c(a%t t(at %ap(icall$ displa$s t(e p%o&ect sc(edule to be used in plannin and t%ac#in . 1ateway ) :a%d1a%e o% so*t1a%e t(at t%anslates bet1een t1o dissimila% p%otocols. 1ranular ) 4esc%ibes t(e a%t o* 1%itin small modules o* code and ; o% ob&ects. 1rap&ical User nterface 71U 6 ) A manne% o* p%esentation t(at ma#es use o* 1indo1s2 icons2 menus2 pointe%s2 and sc%oll ba%ds.

Clossary of TermsG (continued)

H *ardcode ) An in*o%mal te%m t(at desc%ibes a p%o %ammin tec(ni+ue 1(e%e data o% p%ocedu%es a%e speci*icall$ 1%itten into t(e p%o %am inst%uctions. *ardware ) P($sical e+uipment used to p%ocess2 sto%e2 o% t%ansmit compute% p%o %am data. 0 ndependent !eview ) A *o%mal examination o* a p%o&ect conducted b$ an o% ani6ation ot(e% t(an t(e de,elopment o% ani6ation. nformation ) T(e meanin *ul inte%p%etation o* data. !M$ ) In*o%mation Resou%ce Mana ement Commission. ntegration ) 4esc%ibes t(e 1o%#2 o% de,ice2 %e+ui%ed to connect t1o di**e%ent s$stems t(at 1e%e not o%i inall$ desi ned to 1o%# to et(e%. ntegration (est ) Testin in 1(ic( so*t1a%e components2 (a%d1a%e components2 o% bot( a%e combined and tested to e,aluate t(e inte%action bet1een t(em. nterface ) A connection bet1een t1o de,ices o% s$stems. nteroperability ) T(e abilit$ to (a,e applications and compute%s *%om di**e%ent ,endo%s 1o%# to et(e% on a net1o%#.
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page /F of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

ntranet ) An Inte%net net1o%# be(ind a *i%e1all. ssue ) A p%oblem to be sol,ed o% a decision t(at (as not been made. 1 4oint Application Design 74AD6 2 T(e combined e**o%t o* client2 p%o %am2 and de,elopment sta** to de*ine and elicit %e+ui%ements *o% a s$stem .<AR/ o% desi n a s$stem .<A4/. 3 & 2ag 3 T(e amount o* time a*te% one tas# is sta%ted o% *inis(ed be*o%e t(e next tas# ma$ be sta%ted o% *inis(ed. 2ead 3 T(e amount o* time t(at p%ecedes t(e sta%t o* 1o%# on anot(e% tas#. 2ocal Area -etwor% 72A-6 ) A communications s$stem con*ined to a limited a%ea2 t$picall$ a buildin 2 occasionall$ a %oup2 and lin#in compute%s to et(e% ,ia cable.

Clossary of TermsG (continued)

M Maintenance ) Re*e%s to t(e on oin acti,it$ t(at #eeps so*t1a%e *unctionin tec(nical and business en,i%onment .p%oduction/. Met&odology ) A set o* *o%mal p%otocols *ollo1ed 1(en pe%*o%min a tas#. Middleware ) 'o*t1a%e t(at (ides t(e complexit$ o* t(e net1o%#ed computin en,i%onment *%om t(e use%s and application p%o %amme%s. Milestone ) A ma&o% c(ec#point in t(e acti,ities in,ol,ed in a p%o&ect. A clea%l$ de*ined point in a p%o&ect t(at summa%i6ed t(e completion o* a %elated set o* tas#s. Model 3 A 1a$ o* loo#in at %ealit$2 usuall$ *o% t(e pu%pose o* abst%actin and simpli*$in it to ma#e it unde%standable in a pa%ticula% context. Modular Programming ) P%o %ammin t(at (as as its *undamental assumption t(at a la% e piece o* so*t1a%e s(ould be sepa%ated into its constituent pa%ts o% modules t(e%eb$ ma#in *o% easie% and *aste% de,elopment and maintainabilit$. Modules 1e%e t%aditionall$ called sub%outines o% *unctions and no1 a%e o*ten called ob&ects. + in a

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page /3 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

-etwor% ) 4esc%ibes t(e p($sical (a%d1a%e and so*t1a%e connections bet1een compute%s allo1in in*o%mation to be s(a%ed and elect%onic communications to ta#e place. -etwor% Diagram 3 T(e lo ical %ep%esentation o* tas#s t(at de*ines t(e se+uence o* 1o%# in a p%o&ect. -:tier Arc&itecture ) 4esc%ibes a met(od *o% di,idin an application into a se%ies o* distinct la$e%s to p%o,ide *o% ease o* maintenance and *lexibilit$. ( Operating System ) '$stem so*t1a%e t(at cont%ols data sto%a e2 input and output to and *%om t(e #e$boa%d2 and t(e execution o* applications 1%itten *o% it. It pe%*o%ms base se%,ices= p%io%iti6in 1o%#2 sc(edulin 2 memo%$ mana ement2 etc. P Pac%age Ac)uisition ) T(e pu%c(ase2 o% lease2 o* so*t1a%e *%om an outside sou%ce. Padding 3 A standa%d p%o&ect mana ement tactic used to add ext%a time o% mone$ to estimates to co,e% *o% t(e unce%taint$ and %is# o* p%edictin *utu%e p%o&ect acti,ities. Pat& 3 A se+uence o* lines and nodes in a p%o&ect net1o%#.

Clossary of TermsG (continued)

P'!( 8 Project 'valuation and !eview (ec&ni)ue 3 T(e P7RT met(od uses t(e concepts o* milestones2 acti,ities2 and slac# time to calculate t(e c%itical pat(. T(e c(a%t2 1(ic( %esembles a *lo1 c(a%t2 depicts a box to %ep%esent eac( p%o&ect tas# and a line connectin t1o boxes to %ep%esent t(e %elations(ip bet1een tas#s. P&ases ) T(e di,isions o* a so*t1a%e de,elopment li*e c$cle into disc%ete sta es .e. .2 %e+ui%ements2 desi n2 code2 test2 etc./. Planning Project ) A p%o&ect intended to at(e%2 o% p%edict2 t(e se+uence o* acti,ities and %esou%ces needed to complete a 1o%# e**o%t. Platform ) T(e (a%d1a%e and suppo%t so*t1a%e 1it( 1(ic( a p%o %am is intended to ope%ate. Precedence 3 "(en one tas# must be completed be*o%e anot(e% tas# can be sta%ted2 t(e *i%st tas# is said to (a,e p%ecedence o,e% t(e ot(e%. Process ) T(e step3b$3step se+uence o* acti,ities .s$stematic app%oac(/ t(at must be ca%%ied out to complete a p%o&ect.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page /7 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

Programming ) T(e a%t o* 1%itin 2 in a compute% unde%standable lan ua e2 a set o* inst%uctions t(at p%oduces so*t1a%e. Project ) T(e combined %esou%ces .people2 mac(ines2 mate%ials/2 p%ocesses2 and acti,ities t(at a%e dedicated to buildin and deli,e%in a p%oduct to a custome%. Project Duration 3 T(e time it ta#es to complete t(e enti%e p%o&ect. Project Management 3 T(e combination o* s$stems2 tec(ni+ues2 and people %e+ui%ed to success*ull$ complete a p%o&ect on time and 1it(in bud et. Project Manager ) T(e senio% pe%son %esponsible *o% t(e enti%e p%o&ect. Project Management Plan ) A *o%mal document t(at desc%ibes t(e tec(nical and mana ement app%oac( to be *ollo1ed *o% a p%o&ect. Project Sponsor ) T(e depa%tment 8custome%9 1(o 1ill aut(o%i6e p%o&ect initiation2 and 1(o 1ill %ecei,e2 accept2 and use t(e so*t1a%e p%oduct o% se%,ice. Protocol ) A set o* %ules and speci*ications t(at desc%ibes (o1 a piece o* so*t1a%e 1ill be(a,e and (o1 ot(e% pieces o* so*t1a%e must be(a,e in o%de% to 1o%# 1it( t(e *i%st piece o* so*t1a%e. 4 ;uality .P%oduct/ H Con*o%mance to business *unctional %e+ui%ements 1it( de*ect3*%ee p%oducts. >ualit$ %e*lects bot( t(e completeness o* so*t1a%e o% s$stem *eatu%es and *unctions2 and e%%o%3*%ee ope%ation.

Clossary of TermsG (continued)

;uality .P%ocess/ I ?e%i*ication and ,alidation to establis(ed policies2 standa%ds2 p%ocedu%es and uidelines *o% so*t1a%e de,elopment. ;uality Assurance ) "it(in t(e 'tate o* @o%t( Ca%olina2 t(e p%ocess t%ac#in and o,e%si (t *unction *o% monito%in p%o&ect pe%*o%mance2 ad(e%ence to commitments2 and bud et %e+ui%ements. Pe%*o%med unde% t(e cont%ol o* t(e 5**ice o* In*o%mation Tec(nolo $ 'e%,ices .IT'/2 7nte%p%ise Tec(nolo $ 't%ate ies .7T'/ sta**. R !egression (est ) 'electi,e %e3testin modi*ication o* a s$stem. to detect e%%o%s o% *aults int%oduced du%in

!elational Database ) A collection o* data t(at is o% ani6ed into tables so t(at %elations(ips bet1een and amon data can be establis(ed.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 41 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

!esource 2eveling 3 T(e p%ocess o* s(i*tin %esou%ces to e,en out t(e 1o%#load o* team membe%s. !+P : !e)uest for Proposal 3 -o%mal statement b$ a depa%tment t(at t(e$ a%e solicitin ente%p%ises to bid on a cont%act *o% a p%o %am2 s$stem o% se%,ice" !e)uirements ) T(e statement o* needs b$ a use% t(at t%i e%s t(e de,elopment o* a p%o %am2 s$stem2 o% p%o&ect. Ma$ be called business *unctional %e+ui%ements o% %e+ui%ement speci*ications. !esearc& and Development Project ) A de*inition o* a p%o&ect t$pe essentiall$ explo%in options *o% de,elopin ne1 s$stems o% 1o%# p%oducts. !is% ) T(e p%obabilit$ t(at a p%o&ect 1ill expe%ience undesi%able e,ents2 1(ic( ma$ c%eate2 cost o,e%%uns2 sc(edule dela$s2 o% p%o&ect cancellation. T(e identi*ication2 miti ation2 t%ac#in 2 and mana ement o* t(ose elements c%eatin t(e %is# situation. !is% Analysis 3 An e,aluation o* t(e *easibilit$ o% p%obabilit$ t(at t(e outcome o* a p%o&ect 1ill be t(e desi%ed outcome. , Scalable ) A te%m desc%ibin an a%c(itectu%e o% so*t1a%e t(at can (andle expansion in t(e use as t(e need a%ises 1it(out ad,e%sel$ impactin s$stems mana ement and ope%ations. Scope 3 T(e ma nitude o* t(e e**o%t %e+ui%ed to complete a p%o&ect. Server ) A compute% on a net1o%# t(at ma#es applications2 p%int se%,ices2 data2 and communications a,ailable.

Clossary of TermsG (continued)

Slac% 3 see *loat. Software ) Compute% p%o %ams2 s$stems2 and t(e associated documentation t(at desc%ibes t(em. SD2$ : Software Development 2ife $ycle ) T(e pe%iod o* time t(at be ins 1it( t(e decision to de,elop a so*t1a%e p%oduct and ends 1(en t(e so*t1a%e is deli,e%ed. Software Development Process ) T(e p%ocess b$ 1(ic( use% needs a%e t%anslated into a so*t1a%e p%oduct.
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page 4/ of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

Project Management Plan 3 T(e cont%ollin document *o% mana in a so*t1a%e p%o&ect. T(e PP de*ines t(e tec(nical and mana e%ial p%o&ect *unctions2 acti,ities2 and tas#s necessa%$ to satis*$ t(e %e+ui%ements o* a so*t1a%e p%o&ect. Specifications ) 0ene%al te%m *o% t(e 1ide ,a%iet$ o* pape%3based desc%iptions o* a p%o %am o% s$stem. Sta%e&olders 3 People 1(o (a,e a pe%sonal o% a enc$ inte%est in t(e end %esults o* a p%o&ect. Standalone ) 4esc%ibes a compute% 1o%#station 1(e%e t(e compute% is not connected to an$ ot(e% compute% on a net1o%#. Statement of ,or% 7SO,6 3 An inte %ated set o* tas# desc%iptions2 oal desc%iptions2 %is#s2 and assumptions t(at accompan$ t(e e,ol,in maste% P%o&ect Mana ement Plan du%in de,elopment. Strategic Plan ) T(e lon 3%an e plan 1(e%e t(e (o%i6on is usuall$ t(%ee to *i,e $ea%s time span. Subcontract 3 4ele atin tas#s o% sub3p%o&ects to cont%acto%s o% ot(e% o% ani6ations. System ) A lin#ed collection o* p%o %ams2 o% components2 t(at pe%*o%m a business o% tec(nical *unction. ene%ic

System (est ) T(e *inal sta e o* testin on a completed p%o&ect .p%io% to client acceptance test/ 1(en all (a%d1a%e and so*t1a%e components a%e put to et(e% and tested as a 1(ole. SD2$ : System Development 2ife $ycle 3 T(e complex o* tas#s and deli,e%ables t(at a%e o% ani6ed to1a%d de,elopin so*t1a%e s$stems.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 44 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

0lossa%$ o* Te%msA .continued/ $ (actical Plan ) 'peci*ic imp%o,ements2 o% c(an es2 t(at 1ill be ca%%ied out in a *ai%l$ s(o%t time span .usuall$ t1el,e .B2/ mont(s/. (as% 3 A co(esi,e unit o* 1o%# on a p%o&ect .usuall$ 40 to 80 (ou%s o* e**o%t/. (as% Description 3 A desc%iption t(at de*ines all t(e 1o%# %e+ui%ed to complete a p%o&ect tas# o% acti,it$ includin input2 output2 expected %esults2 and +ualit$ speci*ications. (est Plan ) A document t(at desc%ibes t(e scope2 app%oac(2 %esou%ces2 and sc(edule o* intended test acti,ities. (esting ) T(e set o* de*ect %emo,al tas#s t(at include execution o* all2 o% pa%t2 o* an application on a compute%. (opology ) T(e map o% plan o* a net1o%#. 5 Unit (est code. 3 T(e testin ca%%ied out pe%sonall$ b$ indi,idual p%o %amme%s on t(ei% o1n

= 2 ,ide Area -etwor% 7,A-6 ) A net1o%# 1(e%e t(e compute%s a%e sepa%ated b$ si ni*icant distances and telecommunications lin#s a%e implemented. ,or% Brea%down Structure 7,BS6 ) A *o%mal anal$sis o* t(e acti,ities2 tas#s2 and sub3 tas#s t(at must be accomplis(ed to build a so*t1a%e p%o&ect. A p%oduct o% acti,it$ o%iented (ie%a%c($ t%ee depictin t(e elements o* 1o%# t(at need to be accomplis(ed in o%de% to deli,e% a p%oduct. ,or% Pac%age 3 A speci*ication *o% t(e 1o%# to be accomplis(ed in completin an acti,it$ o% tas#. ,or% Product 3 An$ tan ible item t(at %esults *%om a p%o&ect *unction2 acti,it$2 o% tas#. ,or%station ) An$ mac(ine 1it( all o* its installed sto%a e2 p%ocessin 2 and communications t(at can be eit(e% standalone o% net1o%#ed.
5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc Page 4; of 47 145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

0lossa%$ o* Te%msA .continued/ 6 7 8

A 4e*initions 1e%e ext%acted *%om Assessment and *ontrol o- ,o-t.are Ris9s b$ Cape%s <ones .BCC4/D Managing ,o-t.are Develo#ment Projects (,econd edition) b$ @eal "(itten .BCCE/D 0''' ,tandards *ollection: ,o-t.are 'ngineering .BCC7 7dition/D %est Practices in 0$ Arc:itect!re Planning and 0m#lementation b$ !a%%$ 4eFoe,e%D 7ssential *lient/,erver ,!rvival /!ide b$ Robe%t 5%*aliD and $:e *om#lete 0diot;s /!ide to Project Management b$ 'unn$ and Gim Fa#e%.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 48 of 47

145/45/8 /8043 +45P4

(Agency Name Project Name) Project Management Plan

1<. APP'+D0*',
Appendices may be included, either directly or by reference, to provide supporting details that could aid in the understanding of the Project Management Plan.

5,ar5www5apps5con,ersion5tmp5scratch6/54/17813/2"doc

Page 42 of 47

145/45/8 /8043 +45P4