Project Management Plan: The Basics

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog

RSS

View Posts By:

Cameron McGaughy
Marian Haus
Lynda Bourne
Lung-Hung Chou
Bernadine Douglas
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Roberto Toledo
Vivek Prakash
Cyndee Miller
Shobhna Raghupathy
Wanda Curlee
Rebecca Braglio
Rex Holmlin
Christian Bisson

Recent Posts

How to Spot a Top-Shelf Project Manager

3 Lessons From My First Project Manager Job

3 Strategic Resolutions For The New Year

Knowledge Management: More Than Simply Learning Lessons

Want to Start a PMO? Make Sure You Answer These Questions First


Categories: Project Planning


In a previous post, 7 Essential Project Planning Documents, I referred to the "Project Management Plan" as one of the key planning documents that fosters project success. 

Sometimes people confuse the project management plan with the schedule or the scope plan. But it's more than that. 

A project management plan is the planning document, capturing the entire project end-to-end, covering all project phases, from initiation through planning, execution and closure. 

A comprehensive plan covers at least the followings areas and components: 
(Note: A Guide to the Project Management Body of Knowledge (PMBOK® Guide -- Fourth Edition) covers these in Chapter 3. Instead of putting the elements one by one, I grouped them by purpose/meaning.)

  • Overview: Why the project is being conducted and its primary objectives 
  • Scope: Business needs, requirements, deliverables, constraints and work breakdown structure 
  • Schedule: Activities schedule and project milestones 
  • Costs: Project budget and its funding approach
  • Quality: Quality measurement and control approach
  • Project team: The people working on the project, their roles and responsibilities 
  • Communication: Communication type, channels and the reporting approach 
  • Risks: Risk index, methods to identify and evaluate risks, risk mitigation and contingency planning
  • Procurements: Required procurements and purchase processes
  • Closure: Closure approach, including the deliverables hand-off protocol 
  • Changes: Procedures used to track changes in the project 
  • Baselines: Scope, schedule and budget baselines
When writing a project management plan, the approach depends again
on the project's size and context. I personally use the following approaches:

  • The master document approach is where the entire project, with all the underlying planning details, is documented within the same master plan.
  • The index approach, when all subsidiary planning documents are written as separated documents and linked or referenced in an index-like plan.
What approach do you use when crafting a project management plan? What elements do you use?

Posted by Marian Haus on: December 23, 2011 11:44 AM | Permalink

Comments (3)

Please login or join to subscribe to this item
Scott Cosgrove
Agreed, this is critical. Just as important is sponsor/stakeholder buy-in to the Project Management Plan. The longer and more complex the project, the more likely there will be "drift" in the understood requirements of the project. Having this solid framework to reference is a must.There are few activities more pointless than drafting the Project Management Plan after the project is in full swing.

Satish M Seetharam
Agree, Project management plan is very critical to any project. As is like any customer/stakeholder etc., to a project without which you cannot execute a project.

Network:8



I have been on projects where we have NOT drawn out a PM Plan, and there always came a day where the team will ask eachother (with bewildered faces) what the shcedule maintainance procedures or deliverable acceptance protocol is. Many hours have been wasted on debate.

I´ve since then made it a "step one" in the planning phase to bring out a PM Plan template I´ve written and complete the document with the team.

I like to include

- how de WBS will be built
- how the Schedule will be maintained
- change request/control procedures
- how Project documents will be archived

I personally use the Index approach on most projects.

thanks Marian Haus!

Please Login/Register to leave a comment.

ADVERTISEMENT

Sponsors

>