Level 2 Project Management Plan Template

Table 1. Document version

Document Number 1.0

Revision Number 1.0
Effective Date
Owner
Approver

Table 2. Document revision history

Version Date Revision Description

1.0 dd/mm/yyyy Initial Draft Release

Introduction: How to Use This Template

To use this template, simply replace the text in dark grey with information customized to your organization. When
complete, delete all introductory or example text and convert all remaining text to black prior to distribution.

1
Info-Tech Research Group
Contents
1 INTRODUCTION.............................................................................................................................. 3
1.1 ABOUT THIS DOCUMENT.................................................................................................................3
1.2 TERMS AND DEFINITIONS...............................................................................................................3
1.3 PROJECT CHARTER.......................................................................................................................3
1.4 OVERVIEW OF THE PROJECT MANAGEMENT PLAN............................................................................3
2 PROJECT SCOPE........................................................................................................................... 4
2.1 FEATURE REQUIREMENT................................................................................................................4
2.2 PROJECT DELIVERABLES AND ACCEPTANCE CRITERIA.....................................................................4
2.3 PROJECT EXCLUSIONS...................................................................................................................4
2.4 PROJECT CONSTRAINTS AND ASSUMPTIONS....................................................................................4
2.5 HIGH-LEVEL WORK BREAKDOWN....................................................................................................5
2.6 BENEFITS......................................................................................................................................5
3 TEAM, SCHEDULE AND BUDGET.................................................................................................6
3.1 PROJECT TEAM AND ROLES MATRIX...............................................................................................6
3.2 PROJECT SCHEDULE......................................................................................................................6
3.3 PROJECT BUDGET.........................................................................................................................6
4 MONITORING AND CONTROL.......................................................................................................7
4.1 STAKEHOLDER AND COMMUNICATION MANAGEMENT.......................................................................7
4.2 STATUS REPORTING......................................................................................................................7
4.3 CHANGE CONTROL GUIDELINES......................................................................................................7
4.4 QUALITY MANAGEMENT..................................................................................................................8
4.5 RISK MANAGEMENT.......................................................................................................................9

2
Info-Tech Research Group
1 Introduction
1.1 About this document
This Level 2 Project Management Plan documents all required aspects of [Organization name]’s project
management planning for Level 2 projects.

1.2 Terms and definitions

Terms Definitions

PMO Project management office

SME Subject matter expert

SOP Standard operating procedure

1.3 Project charter

Insert a hyperlink to the project charter.
Please refer to the linked document
Project Charter [Insert file name with hyperlink]

1.4 Overview of the project management plan

A project management plan can and should address the following topics of project management:
 Scope  Schedule  Cost
 Stakeholder  Quality  Risk
 Human resources  Communication  Procurement

For Level 2 project (for definition, please refer to the SOP and the Project Level Definition Matrix/Assessment
Tool) a high-level description of these areas should suffice the planning and visibility needs. Using data from the
project charter, this template offers an opportunity for the project manager to efficiently address the planning
needs of a mid-sized project.

3
Info-Tech Research Group
2 Project Scope
2.1 Feature requirement
Write a brief description of the product’s or service’s features, and describe the dependency of each feature.
Feature Dependencies

2.2 Project deliverables and acceptance criteria

The deliverables section should include both product and service outputs. This includes all documentation that is
produced through project work. Each deliverable should have a corresponding acceptance criteria and a
designated stakeholder responsible for final sign-off of the deliverable.
Deliverable Acceptance Criteria Final Sign-Off – Owner

2.3 Project exclusions

List everything that is not in scope for this project.
Scope Item Details

2.4 Project constraints and assumptions

List all the constraints affecting this project, with the corresponding assumption. Provide a brief assessment of the
impact of this assumption changing. Validating these assumptions should be completed as part of the project
planning process.
Constraint Assumptions Impact If Assumption Is False

4
Info-Tech Research Group
2.5 High-level work breakdown
Provide a high-level list of work involved required to deliver a product or service that meets the scope outlined
above. Dividing work into lists may be based on deliverables and the tasks necessary to create them. In project
management, a structured tree of work breakdown is called work breakdown structure (WBS). For Level 1
projects, a detailed WBS is not necessary; however, a brief list of work breakdown may still be helpful for project
scheduling, status report and work delegation.
ID Description Deliverable Notes
1
2
3
4
5
6

2.6 Benefits
Provide a high-level list of benefits to be realized by the delivered product or service that meets the scope outlined
above.
ID Benefit Description Metric Notes
1
2
3
4
5
6

5
Info-Tech Research Group
3 Team, Schedule and Budget
3.1 Project team and roles matrix
ID Name Position Email Address Role
1 Project Owner
2 PMO Director
3 Project Manager
4
5
6

Roles

PMO Director

PMO Staff

Manager
Project

Cheryl

David

Edith
Alice
CIO

Bob
Work
1
2
3
4
5
6

3.2 Project schedule

Insert a hyperlink to the project schedule.
Please refer to the linked document
Project Schedule [Insert file name with hyperlink]

3.3 Project budget

Insert a hyperlink to the project budget.
Please refer to the linked document
Project Budget [Insert file name with hyperlink]

6
Info-Tech Research Group
4 Monitoring and Control
4.1 Stakeholder and communication management
List the stakeholders and the deliverable.
ID Stakeholder Name of Document or Contact person Due / Recurrence
Deliverable
1
2
3
4
5
6

4.2 Status reporting

A status report will be populated using the template linked below every [occurrence].
Please refer to the linked document
Status Report Template [Insert file name with hyperlink]

4.3 Change control guidelines

Define the criteria for the escalation of change requests. Suggested guidelines are provided below, but should be
reviewed and altered to match organizational standards.
The Project Manager has the authority to release contingency funds and change milestone dates.
Decision Rests with Project Escalate to Steering
Impact Category
Manager Committee Escalate to Sponsor
Change is within original Change is out of
Scope
project scope. scope.
Change can be absorbed into Change will require
current project budget. additional funds,
Budget Contingency funds might need exceeding any
to be released to contingency reserves.
accommodate change.
Change can be absorbed into Change will require
current project schedule. the final project close
Schedule
Milestones may shift to date to be delayed.
accommodate change.
Change can be linked to an Change will require a
existing business requirement. change to business
Requirements
requirements, or a new
business requirement.

7
Info-Tech Research Group
4.4 Quality management
If the project requires a high rigor of quality management, use the Quality Management Workbook to develop a
full quality management plan.
Please refer to the linked document
Quality Management Workbook [Insert file name with hyperlink]

Otherwise, specify the metrics with which to manage and ensure quality of the deliverable. At least one quality
metric must be associated with each project deliverable.
ID Deliverable Quality Metric Method Metric Owner
(what to measure) (how to measure) (who to measure)
1
2
3
4
5
6

In the table below, specify the frequency of measurement for each metric whose IDs correspond to the above
table, the target result and the acceptable range of deviation. Each quality metric should be accompanied by at
least one related risk item. If the actual result deviates beyond the acceptable range, the mitigation plan for the
risk items should execute.
ID Frequency Target result Acceptable deviation Related risk item ID
(when to measure)
1
2
3
4
5
6

8
Info-Tech Research Group
4.5 Risk management
If the project requires a high rigor of risk management, use the Risk Management Workbook to develop a full risk
management plan.
Please refer to the linked document
Risk Management Workbook [Insert file name with hyperlink]

Otherwise, specify the risk items to manage below.

ID Risk Event Risk Cause/source Impact/consequence Probability
(low | moderate | high)
1
2
3
4
5
6

In the table below, specify the risk owner and the mitigation of plan for each risk item whose IDs correspond to the
above table. Specify any deliverables and the resources required for putting the mitigation plan into action.
ID Risk owner Mitigation plan Deliverable Required resources

1
2
3
4
5
6

Risk items are to be monitored and their statuses reported at each project status report.

_____________________________________________________

For acceptable use of this template, refer to Info-Tech's Terms of Use. These documents are intended to supply
general information only, not specific professional or personal advice, and are not intended to be used as a
substitute for any kind of professional advice. Use this document either in whole or in part as a basis and guide for
document creation. To customize this document with corporate marks and titles, simply replace the Info-Tech
information in the Header and Footer fields of this document.

9
Info-Tech Research Group