ClearPM

When someone asks for a "project plan" are they expecting to see a document detailing the plan for successful completion of the project?  Or do they just want to see the schedule?  Many project managers believe this confusion comes from under educated customers; many customers believe project managers are overly literal.  What do you think?  Is there a critical difference?  Does it really matter what you call it if everyone knows what you're talking about?

As a professional PM I believe there's a substantial difference between the two.  I can't remember ever saying "plan" when I meant "schedule."  I have had customers mix the terms and although it was initially confusing, a simple exchange clarified their intent.  Since I had both, no biggie.  I feel fortunate that this type of mix up is rare for me.  In fact, the project management processes defined at my place of employment make it pretty clear to all stakeholders that the two artifacts are significantly different. 

When we say "project plan" we mean one thing.  "Project schedule" means something else entirely.  The contents of the project plan are clearly defined and the schedule, in the form of milestones or just a high-level overview, is but one part of it.  Team composition, communications management, change control, risk management, supplier management, and deliverables are some of the other parts.  In addition, depending on the size and complexity and level of risk associated with the project, the project plan document can take different forms.  If the project is small, straightforward, and low risk, the project plan can be a simple, almost fill-in-the-blank type of Excel workbook with tabs corresponding to the different plan components.  Larger, more complex, and riskier projects will have project plans in the form of a multiple page document with as many pages as required devoted to each of the components.  Both are good tools and suit their purpose well.

According to the PMBOK Guide, the project management plan consists of "the actions necessary to define, prepare, integrate, and coordinate all subsidiary plans.  The project management plan becomes the primary source of information for how the project will be planned, executed, monitored and controlled, and closed."  It goes on to delineate exactly what the "subsidiary plans" are, states that "each is detailed to the extent required by the specific project," and explains that the baseline schedule is an output of the "Develop Schedule" process and an input to the project management plan.  It seems clear from the Guide's description that the "project plan" and "project schedule" are two different things.

I think some of the confusion comes from Microsoft (yes, let's blame Microsoft for this, too!).  The standard file extension for Microsoft Project files is .mpp which stands for Microsoft Project Plan.  On the other hand, maybe it's a result of too many PMs shortening the name of the PMBOK Guide's "project management plan" to just "project plan."  Whatever the cause and regardless of our reasoning, people will persist in referring to the schedule as the plan.  I know the world has bigger problems so I'm not overly concerned.  Let's just try to make it clear what we mean when we say "plan" or "schedule."