Project Management Plan details how a project will be executed, monitored, and controlled. In general, it should include at least: 1. Scope, Schedule, and Cost Baseline. 2. Subsidiary plans for each knowledge area. 3. Additional information on project nature and life cycle. Here I describe the possible amount of information a project management plan may include. The slides are an integral part of a post on Project Management Plan from Project Management Basics. Find the post here: http://pmbasics101.com

1. Practical Guide to Useful
Project Management Plan

2. Project Management Plan
Describes how the project will be executed, monitored, and controlled.
Should be appropriately detailed for the project.
May be summary level or very detailed.
May include one or many subsidiary plans.
Subsidiary plans are detailed to the necessary extent. They
may be informal.
May include a description of selected life cycle.

3. Scope Management Plan
Describes how scope will be defined, developed, monitored and controlled.
Strongly depends on project life cycle.
Describes how to:
Define scope;
Validate deliverables;
Prepare Project Scope Statement;
Create and maintain a Work Breakdown Structure
(templates, tools, techniques and practices);
Obtain formal approval of deliverables;
Monitor and control scope.
Project
21 3
1.1
1.2
1.3
2.1 3.1
3.2
3.3
3.4

4. Requirements Management Plan
Describes processes to analyze, document, and manage requirements.
Strongly depends on project life cycle.
Describes:
How to plan, track and report requirements activities.
How to priorities requirements.
Timing, document formats and approvals needed.

5. Scope Baseline
Formally fixed and documented amount of work that
is planned for the project.
Consists of:
Project Scope Statement;
Work Breakdown Structure (WBS);
WBS Dictionary.

6. Schedule Management Plan
Describes criteria and activities for creating, monitoring and
controlling schedule.
May include:
Schedule methodology (Critical Path, Critical Chain, Sprints);
Schedule tools (Network Diagram, Gantt Chart, etc.);
Level of accuracy, units of measurement;
Integration of WBS, activities and estimates;
How to measure performance, Control Thresholds;
Reporting formats.
2.2
Start
1.1
1.2
2.1
Finish

7. Schedule Baseline
Formally approved and documented final version of
the project schedule.
May include:
Project Schedule;
Start and Finish dates for each activity.
Mar
29

8. Cost Management Plan
Describes how the project costs will be planned, structured and controlled.
May include:
Level of accuracy for estimates;
Level of precision;
Units of measurement;
Integration with WBS, activities and estimates;
Control thresholds;
How to measure performance;
Reporting formats.
$$$

9. Cost Baseline
Formally approved and documented version of the
project budget.
May include:
Calendar based cost budget;
Deadlines for funding.

10. Change Management Plan
Documents how changes will be processed, monitored, and
controlled.
May include:
Plan to prevent changes proactively;
Process of creating, reviewing, approving and monitoring of
change requests;
Change Log;
Description of Change Control Board activities.

11. Configuration Management Plan
Describes the ways to log changes made in project documentation and deliverables.
Ensures that composition of a project item configuration is correct.
Defines the latest version of project management
plan, processes and deliverables.
Logs changes made to project documentation,
processes and deliverables.
##

12. Risk Management Plan
Describes how risk management activities are structured and performed.
May include:
Methodology (approaches, tools, sources of data);
Ways to prevent risks;
Budgeting and timing;
Roles and responsibilities;
Risk Categories;
Descriptions of risk probability and impact, probability and impact matrix;
Tracking and reporting.
!

13. Quality Management Plan
Is closely related to organization’s quality policies.
It should be created early during project planning as it is
beneficial to build it into project scope.
May include:
Identified quality requirements.
How to implement processes that comply with quality policies.
How to demonstrate compliance with the quality policies.

14. Process Improvement Plan
Defines ways to analyze processes on the project to identify
opportunities to enhance their value.
Describes how to:
Improve project management processes.
Improve product development processes.
Plan
Do
Check
Act

15. Procurement Management Plan
Describes how a project team will acquire goods and services
from external sources.
May include:
Description of procurement processes.
Procurement documentation to be used.
Best practices.
Types of contracts to be used.

16. Human Resources Management Plan
Describes how project human resources should be defined, staffed, managed and released
from the project.
May include:
Roles and responsibilities;
Project organization charts;
Staffing management plan:
Staff acquisition and Resource calendar;
Training needs and Staff release plan;
Recognition and rewards system;
Safety.

17. Communication Management Plan
Describes how project communication will be planned, structured and controlled.
May include:
Stakeholder communication requirements;
Information to be communicated and why;
Methods and technology to be used;
Escalation process;
Communication constraints;
Glossary of common terminology.
bla-bla?
bla-
bla-bla

18. Summary
Create a Project Management Plan for each project.
Collaborate with the project team.
Reuse subsidiary plans.
Keep Project Management Plan usable.
Keep it detailed on appropriate level.

19. Become a better project manager
at
Project Management Basics