Use this for all of your project management plan needs!

1. Author:[Type the authorname]
Last Updated:May 8, 2018
Project Management
Plan
[Insert Project Name]

2. ProjectManagement Plan – [InsertProjectName]
Page | 1
File Location:[optiontoenterfile storage location]
Purpose of Project Management Plan
The project management plan is a single, formal, dynamic document that outlines how the project is to be managed, executed,
and controlled. It contains the overall project governance and related management plans and procedures, timelines, and the
methods and accountabilities for planning, monitoring, and controlling the project as it progresses. This document evolves with
the project and will be updated to reflect any relevant changes throughout project execution. This document should ensure
there are no surprises through execution on how the project is managed or decisions are made.
This document is also the final source of all approved changes to budget, schedule, scope, success criteria, and benefits when
it comes time to close the project and assess project success. The project management plan is part of the Portfolio Management
Group’s project planning phase of the life cycle and is required for all large sized projects.
Project Management Plan Participants and Approvers
Input into the project management plan maycome from many different sources including, but not limited to, Sponsor, senior
leadership, project intake proposal, project charter(s) and business case(s), initial analysis/research done when proposing the
project, subject matter experts within business unit(s), governance bodies, and other stakeholders (such as staff, students,
faculty).
The author is the Project Manager for the project. The document should initiallybe reviewed by and approved by the Project
Sponsor (recorded in the revision history) and governance.
Instructions
1. Write preliminaryproject management plan and create required baselines (budget, scope, schedule). Obtain
agreement from teams and governance, and approval from sponsor. Record revisions and approvals in the Revision
History
2. Execute the document according to the documented management plans.
3. Update the document, as required, to reflect approved project changes as the project evolves.
4. Before project completion, make any final updates and use the final schedule, budget and expenditures, success
criteria, benefit, scope, et cetera to assess project success during project closure.
5. Upload to the Knowledge Base
Next Steps
Execute the project according to the strategies and plans laid out in this document. Update this document to reflect any
approved changes during project execution. Reflect final project results in this document at the end of the project and use this
document during project closure to assess project success.

3. ProjectManagement Plan – [InsertProjectName]
Page | 2
File Location:[optiontoenterfile storage location]
Table of Contents
Project Definition ...............................................................................................................................4
Project Description .........................................................................................................................4
Project Purpose...........................................................................................................................4
Project Outcome and Deliverables................................................................................................4
Project Scope..................................................................................................................................4
Project Dependencies .....................................................................................................................4
Project Constraints.............................................................................Error! Bookmark not defined.
Project Success Criteria...................................................................................................................5
Project Methodology ......................................................................................................................5
Project Management Plans .................................................................................................................6
Schedule Management ...................................................................................................................6
Schedule Management................................................................................................................6
Baseline Schedule........................................................................................................................6
Current Schedule.........................................................................................................................6
Budget and Cost Management.........................................................................................................6
Cost Management.......................................................................................................................6
Baseline Budget..........................................................................................................................6
Current Budget...........................................................................................................................6
Other Management Plans................................................................................................................7
Scope Management.....................................................................................................................7
Change Management..................................................................................................................7
Stakeholder Management............................................................................................................7
Communication Management......................................................................................................7
Procurement Management..........................................................................................................8
Staffing Management..................................................................................................................8
Risk & Issue Management............................................................................................................8
Project Governance............................................................................................................................8
Governance Committee(s)...............................................................................................................8

4. ProjectManagement Plan – [InsertProjectName]
Page | 3
File Location:[optiontoenterfile storage location]
Governance Decision Making Approach ...........................................................................................9
Governance Reviews.......................................................................................................................9
Revision History..................................................................................................................................9

5. ProjectManagement Plan – [InsertProjectName]
Page | 4
File Location:[optiontoenterfile storage location]
Project Definition
Project Sponsor: [insertname,title]
Project Manager: [insertname]
Estimated ProjectStart Date: [insertdate] Actual Project Start Date: [insertdate]
Estimated ProjectEnd Date: [insertdate] Actual Project End Date: [insertdate]
Project Description
The overviewof the project should bedocumented in the project charter,businesscase,and/orintake
proposal,so a link to thosedocumentscould beprovided. While the ProgramCharter, intakeform,
and/orbusinesscasearegood referencesforthis section,initially, this information may haveto be
changed in this section and keptup to date asthe project evolves.
Project Purpose
[Describe the projectandthe benefit(s)itistodeliver]
Project Outcome and Deliverables
[InsertProjectOutcome andDeliverables]
Project Scope
Statethe scopeof theproject (whatis in and out of scope). Notethata final scopeincludes
requirementsand a breakdown of thework(e.g.a WBS) so links on whereto find these should be
included. The scopestatementin the Project Chartercan be used as a starting point. This section
providestheopportunity to expand upon thecharterscopein moredetail, and record approved changes
to scopeas theproject evolves. This section will alwayscontain theup to date scope,with changes
recorded in the revision history of this document. Approvedscopechangeswillalso havebeen
documented on ChangeRequests.
[InsertProjectScope]
Project Dependencies
This section should contain thelist of projectdependencies. Projectworkpackageand/ortask
dependenciesshould bedocumented (hereora link to where they are documented),aswellas any
externaldependenciesthatmay affecttheproject. Information in thissection will changeand haveto be
updated astheproject evolves.
[InsertProjectDependencies]
Project Constraints
List the constraints(restrictions thatcould affectthe performanceof theproject thatlimit resources
(peopleand budget),schedule, orscopeand could affectquality) of theproject.

6. ProjectManagement Plan – [InsertProjectName]
Page | 5
File Location:[optiontoenterfile storage location]
It is importantforthe Project Managerto understand which of the resources($$ and
people)/schedule/scopeconstraintsaremostto least flexible within the project. Includethis information
by making one‘x’on each row in the Triple ConstraintFlexibility Matrix below. This information provides
guidanceon the Project Sponsor’slevelof flexibility in these areaswhen determining trade-offsin
planning and changecontrol.
The projectcharteris a good referenceto start this section. Information in thissection will changeand
haveto be updated astheproject evolves.
[InsertProjectConstraints]
Triple Constraint Flexibility Matrix
FLEXIBILITY: LEAST SOMEWHAT MOST
Resources($$ and
people)
Schedule
Scope
Project Success Criteria
Whatis required for thesuccess of this project,accounting forfactorsthatcontributetowardsthe
realization of thebenefitsand goals/objectives? Thesuccesscriteria should be unambiguous,observable
and traceableback to the projectgoalsand benefits. The project charteris a good referenceto start this
section on somepotentialcriteria thatmay havebeen identified during initiation. It is likely that
measureswill haveto be furtherdefined during planning and execution,so information in thissection
will changeand haveto be updated astheproject evolves.
[InsertProjectSuccessCriteria]
Project Methodology
This section should contain a description of the methodology (waterfall,iterative,incremental,agile,
hybrid) thatwill befollowed forthis projectand why this methodology hasbeen chosen. If iterative,
incremental,agile, or a hybrid approach ischosen,thissection should include detailson iteration lengths,
incrementalreleases, etc. Describe howthe methodology willbe managed and whetherpilots,
prototypes,focusgroups,et cetera will be used.
[InsertProjectDependencies]

7. ProjectManagement Plan – [InsertProjectName]
Page | 6
File Location:[optiontoenterfile storage location]
Project Management Plans
Schedule Management
Schedule Management
This section should describethe approach for creating, updating,and monitoringtheprojectschedule.
This section should also includeinformation on thescheduling tools/formatsto beused,and schedule
developmentrolesand responsibilities.
[InsertProjectScheduleManagement]
Baseline Schedule
Insertor link to the baseline(initial) scheduledeveloped forthe project. The scheduleshould accountfor
tasks,priorities,dependencies,and milestones.
[InsertProjectBaseline Roadmap]
Current Schedule
Insertor link to the current, updated version of theprojectschedulethat reflectsany approved changes
during projectexecution. The scheduleshould accountfortasks,priorities,dependencies,and
milestones.
[InsertCurrentProjectSchedule]
Budget and Cost Management
Cost Management
Providea description of howthe costsof the project will be managed. Itshould include:who is
responsibleformanaging costs,who hastheauthority to approvechangesto theprojectorits budget,
whetherand howcostperformanceisquantitatively measured and reported upon,and any report
formats/frequenciesand to whomthey arepresented.
[InsertCostManagementPlan]
Baseline Budget
Insertor link to the baseline(initial) budgetdeveloped fortheproject.
[InsertProjectBaselineBudget]
Current Budget
Insertor link to the current,updated version of theproject budgetand expendituresthatreflectsany
approved budgetchangesduring project and componentexecution,aswellas expendituresto date.
[InsertCurrentProjectBudgetandExpenditures]

8. ProjectManagement Plan – [InsertProjectName]
Page | 7
File Location:[optiontoenterfile storage location]
Other Management Plans
Scope Management
Providea description of the following:who hastheauthority and responsibility forscopemanagement,
howthe scopeis defined,howthescope is measured and verified (e.g.quality checklists,scope baseline,
benefitsregister, etc.), thescope changeprocess(which may already bedocumented in the change
controlprocess),and who is responsibleforapproving project scopeand accepting finalproject
deliverables.
[InsertScope ManagementPlan]
Change Management
Providea description of the project’schangecontrolprocess(thiswould beforchangesto do with the
projectscope,schedule,and budget). Project changesarenormally responsesto updatedbusiness
drivers orconstraints. This section should include: wherechangerequestsareto be stored and howthey
will be tracked & monitored,identification of who hasapprovalauthority forchanges,and who can
submitrequestsforchange. The scopeof changein this section should includechanging scopeof the
project,changing benefits orgoals/objectives,changesto budget,changesin timelines, et cetera. It is
recommended thatthePMO’s changerequesttemplatebeused for requesting and approving changes.
[InsertChange ManagementPlan]
Stakeholder Management
This section should contain thelist of stakeholders,and outlineany specificplansformanaging these
stakeholders. Insertorlink to the stakeholderregister. Stakeholderscan bemaintained within the
stakeholderregistertemplate,or the tablefromthe templatecould be copied here and maintained
during projectexecution within this document. Theprimary stakeholder(s) should beclearly identified
within theregister.
Describe howthe stakeholderswill bemanaged,including how often thestakeholderswillbe monitored
and the register updated,who isresponsible,who isinvolved in gathering information fortheregister,
and identifying strategiesformanaging stakeholdergroups.
[InsertStakeholderManagement Plan]
Communication Management
Link to the communicationsplan fortheprogram,orcopy the communicationsplan template and
maintain the communicationsplan here. Thiscommunicationsplan should beupdated regularly and be
based on expectationsof stakeholders, programgovernance,and theprojectteam.
[InsertCommunicationManagement Planlinkorinformationhere]

9. ProjectManagement Plan – [InsertProjectName]
Page | 8
File Location:[optiontoenterfile storage location]
Procurement Management
Providea description of the necessary stepsand responsibilitiesforprocurementfromthebeginning to
the end of theproject. Depending on the project,thissection may require the Project Managerto work
closely with Procurement,a Licensing Coordinator,etc. Includeinformation on who isresponsiblefor
contractnegotiations,approvals,maintaining thevendorrelationship and monitoringvendorprogress
againstcontractand statementsof work.
[InsertProcurementManagementPlan]
Staffing Management
Providea description of howthe project will bestaffed and how staff will be managed. Listkey resources
and times/durationsthey areneeded, aswell as any required project staff training to preparethem.
Includeany information on reporting relationshipsand/ordotted reporting relationships,staff
performanceissues,and howescalationswillbe handled if staff availability is an issue. Provideproject
teammemberswith the option of determining and tracking their projectgoals with the PM and their
functionalmanagersand documenthow thiswill be managed.
[InsertStaffingManagementPlan]
Risk & Issue Management
Providea description of the approach taken to identify and manageproject risks,actions,issuesand
decisions(RAID). It should includehowthey are reported,logged,tracked and monitored. Includewho
hasaccess to submitthem,who is accountablefor dealing with them,any agreed upon responsetimes
thatshould be documented,etc. Specifically identify how risk triggers are monitored and by whom,and
howa risk is converted to an issue when triggersfire. This section should clearly pointto wherethe RAID
log forthe project is stored.
[InsertRisk& Issue ManagementPlanandlinktoRAIDlog]
Project Governance
Governance Committee(s)
Describe the projectgovernancestructure(diagramsmay beused with this description). Describethe
roles and responsibilitiesof each governing group,outlining decision making authority,and overall
interest/focus/purposeof thegroup within theproject. Documenthow often thegoverning groupswill
meet, who will chair, and who attendsthemeetings(asa memberand as a reference source,when
required). If there is a terms of reference documented forthegroup,providea link to it.
[InsertGovernance Committee(s)]

10. ProjectManagement Plan – [InsertProjectName]
Page | 9
File Location:[optiontoenterfile storage location]
Governance Decision Making Approach
Describe the decision making approach thegroup(s) willfollow. Includea list of decision guidelinesand
agreed upon priorities againstwhich decisionswill be made. Outlinehow escalationsto thegroup(s)
should bebroughtforward and handled by thegroup(s), and how decisionswillbe documented and
communicated. If thedecision making authority of thegroup(s) isnotincluded in the abovesection,it
should beincluded here. If there is a standard agenda to befollowed during thesemeetingsforthe
group(s), includeithere.
[Insertgovernance decisionmakingapproach]
Governance Reviews
Stage gate/Milestone reviews
This section outlinesstagegateor milestone reviewsand their requirements. This section should outline
when the reviewswill be held,whatwill be reviewed,and the data to be reviewed prior to determining
whetherto moveon to the nextstage.
[Insertstage gate/milestone reviews]
Project performance reviews
This section outlineswhen and howoften project performancewillbe reviewed by thegroup(s),focusing
on the overall performanceand managementof theproject. Thissection should also describe the
required projectperformanceinformation thatmustbeprovided to thegroup(s) in supportof these
reviews.
[Insertprojectperformance reviews]
RevisionHistory
Change Made By Date Change
Made
Detailsof Change Change
Reviewed/
Approvedby
Date change
reviewed/approved