« Project Manager Meets The Steering Committee
How to Create a Project Schedule »

The Project Schedule and The Project Plan

September 8, 2010 | Author: PM Hut | Filed under: Project Plan Development, Scheduling

The Project Schedule and The Project Plan
By Ann Drinkwater

A project schedule is not the same as the project plan. Repeat after me, the schedule is not the project plan. As the name suggests, the project plan is a collection of documents used to manage the execution of a project. The schedule includes dates for tasks and milestones in the project plan and is an element of the plan, but is not comprehensive enough to be considered a plan. The project plan goes much deeper than a timeline and is the overall blueprint for the project. According to the PMBOK, the project plan may include the following:

  • Project charter
  • Description of project management approach or strategy
  • Scope statement
  • Work breakdown structure
  • Cost estimates
  • Performance measurement baselines
  • Major milestones and target dates
  • Key or required staff
  • Risk management plan
  • Subsidiary management plans:
  • Scope management
  • Schedule management
  • Cost management
  • Quality management
  • Staffing management
  • Communication management
  • Risk response
  • Procurement management
  • Supporting detail
  • Outputs from other planning processes
  • Constraints and assumptions
  • Technical documentation
  • Standards documentation

You should determine the level of detail needed, based on the size of the project. From the list above you can see this list is quite extensive and much more encompassing than a list of tasks, assignments and expected dates. I often hear companies and individuals refer to the schedule as the overall plan for the project, which is inaccurate and a risk for your projects and organizations. Without capturing and managing the information above, you are not truly planning for and managing the outcome of your projects.

I previously wrote about areas to be aware of when selecting a vendor, including their ability to plan. Planning is fundamental to project success. The ability to plan and to derive what is important from vast amounts of information and stakeholders is essential. We all know the saying “if we don’t have a clear plan on where we are going we won’t know when we get there”, but if we don’t have a clear understanding on the other areas listed above; our projects and teams will flounder. Not properly addressing and continuously managing the items above will create significant concern from executives and others funding the project, as well as those the project is being designed for.

While we may not have all the answers when we start planning the project, we need to remember that planning is iterative and these plans are not created in a one-time session. The act of creating these guides will require you to think through the necessary factors and truly analyze the situation, creating a response to all possible scenarios.

Ann’s professional focus is information technology project and program management. She is a certified Project Manager (PMP), a certified ScrumMaster (CSM) and a member of the Washington D.C. Chapter of the Project Management Institute. Educationally she holds an MS in Technology Management and a BA in Organizational Leadership and Development.

© Copyright 2005 - 2010 Ann E. Drinkwater. All Rights Reserved.

Share this article:
  • Facebook
  • LinkedIn
  • TwitThis

This entry was posted on Wednesday, September 8th, 2010 and is filed under Project Plan Development, Scheduling. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 people have left comments

Fully agree - good post to remind folk! I just wish that senior managers would read this and understand. The amount of times I have seen projects going wrong purely because the senior stakeholders just want the PM to ‘get on with it’, when what is really required is an appropriate project plan, along with a schedule.

Dr. Edward Wallington wrote on September 11, 2010 - 9:52 am | Visit Link

You are right. The worst argument that I’ve had, in support of Project Schedule being same as Project Plan, is the extension “MPP”… which stands for Microsoft Project Plan. Ah well.

Cheers,
Nitin Malhotra

Nitin Malhotra wrote on September 24, 2010 - 9:00 am | Visit Link

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

The Stevens Enterprise Project Management Master's Program

Project Management Categories