Exploring trends and developments
in project management today.

Project Smart Logo

Subscribe  Follow Project Smart on Twitter!

Project Planning in a Nutshell

By Thomas Pyzdek
Gantt Chart

Improvement happens one project at a time. But often projects fail because they are poorly planned, or even completely unplanned. This article provides an overview of why it is important to prepare a project plan. It also shows what elements a good project plan will include.

Why Create a Project Plan?

There are several reasons why one should plan carefully before starting a project:

  1. The plan is a simulation of prospective project work, which allows flaws to be identified in time to be corrected.
  2. The plan is a vehicle for discussing each person's role and responsibilities, thereby helping direct and control the work of the project.
  3. The plan shows how the parts fit together, which is essential for co-ordinating related activities.
  4. The plan is a point of reference for any changes of scope, thereby helping project managers deal with their customers.
  5. The plan helps everyone know when the objectives have been reached and therefore when to stop.

Elements of a Good Project Plan

The project plan shows the "why" and the "how" of a project. A good project plan will include the following elements:

  • Statement of the goal.
  • Cost/benefit analysis.
  • Feasibility analysis.
  • Listing of the major steps to be taken.
  • Timetable for completion.
  • Description of the resources required (including human resources) to carry out the project.

The plan will also identify objective measures of success that will be used to evaluate the effectiveness of the proposed changes, these are sometimes called the "deliverables" of the project.

Project Decomposition

Most projects important enough to have a significant impact on quality are too large to tackle all at once. Instead, large projects must be broken down into smaller projects and, in turn, into specific work elements and tasks. The process of going from project objectives to tasks is called decomposition. Project decomposition begins with the preparation of a preliminary plan. A preliminary project plan will identify, in broad high-level terms, the objectives of the project and constraints in term of time and resources. The work to be performed should be described and precedence relationships should be sketched out. Preliminary budgets and schedules will be developed. Finally, subplans will be developed for each subproject for the following:

  • Control plans.
  • Quality control plans.
  • Cost control plans.
  • Schedule control plans.
  • Staffing plans.
  • Material plans.
  • Reporting plans.
  • Other plans as deemed necessary.

These subplans are developed in parallel for the various subprojects.

Improvement happens one project at a time, but without proper planning these project may well fail to deliver their objectives.

Thomas Pyzdek wrote the Six Sigma Handbook, The Quality Engineering Handbook and The Handbook of Quality Management. His works are used by thousands of universities and organisations around the world to teach Quality, Lean, and Six Sigma. Get more Six Sigma Training informationExternal Link

Comments page 1 of 1
Click here to add a comment
Chris Bishop
Posted 236 days ago
I think that Bill has raised an interesting point about some people´s perceptions of planning being ´bad´when it needs to change part way through. I believe that colleagues throughtout any working team need to be fully aware from the start that their project plan is simple and flexible enough to cater for necessary adjustments and changes that will inevitably evolve.
Arnel Guanlao
Posted 266 days ago
I agree with Pradeep's comment about risk identification, but I would extend it to include a mitigation or contingency plan for each major risk identified. Also, the farther out in time you go, the leaner I would make the plan. While there is value in having a general understanding of where we would like to be six or twelve months out, any highly detailed planning that far out is likely to be wasted effort - too many factors can and will change those details.
Billy Gee
Posted 266 days ago
I would also add that you need to obtain FULL management buy-in and commitment prior to proceeding. Often IT projects span different departments and it is amazing how change is feared and opposed. I.e. just because the finance department could benefit it does meet production are going to buy in to change.

http://www.trainingconnection.com/project-management-training.php
Veronica Brown
Posted 273 days ago
Often projects fail because Project Managers dont bother to communicate the objectives and KPIs (in addition to the schedule) to the team members. Also, a lot of team members dont really care about getting the big picture.

Thanks,
Veronica
Pradeep Bhanot
Posted 280 days ago
Thomas, risk identification is an essential element that your proposed plan does not include. I agree with the comments from Bill and Diwant that changes to the plan should be expected and a leaner plan is a good thing.
Diwant Vaidya
Posted 284 days ago
@Bill yes, plan changes are good, and @Thomas while these steps may be necessary for huge projects (more control), going through this much effort will make it difficult to bring changes that happen back into the plan. I have seen 300 line Gantt charts that are monsters to update and are simply curious artifacts that the project eventually leaves behind.

So while I agree very strongly with the need for a plan, I think the amount of detail that goes into the plan should be limited. My group believes that the limit should be 7 things because that is how much the human brain can handle at a time (http://paradigmpop.com/node/46 for more on that idea). We allow each of these 7 things to have a further plan. The plans stay simple and they stay updated.
Bill Duncan
Posted 286 days ago
There are three key things missing from this article that are absolutely fundamental to project planning.

First, there is no mention of the project life-cycle. Some of the sub-plans mentioned are neither necessary nor appropriate in the earliest phases of the project.

Second, the list of planning elements does not include project success criteria. Without these, you won't know whether you have done a good job or not.

Finally, there is no discussion of WHY teams resist planning. In my experience, there are three main reasons:
-- They don't understand that planning still provides enormous value even if the plan itself changes. When it comes to the plan, change is good. Many team members think that they did a bad job of planning if the plan changes.
-- Because of the first reason, they think they are bad planners, and people tend to avoid doing things they think they are bad at.
-- They don't understand that good planning ensures that they will have the resources to do good technical work.

Duncan
 

Article Categories

Related Articles

Project Planning A Step by Step Guide
The key to a successful project is in the planning. Creating a project plan is the first thing you should do when undertaking any kind of project. Often project planning is ignored in favour of getting on with the work. However, many people fail to realise the value of a project plan in saving time, money and many problems.

17 "Must Ask" Questions for Planning Successful Projects
Why do some projects proceed without a hitch, yet others flounder? One reason could be the type and quality of the questions people ask at the very start. This article suggests 17 insightful queries that can expose the uncertain aspects of your project, and thereby help you avoid expensive surprises later. You can thus achieve your project goals with much less guesswork and far fewer problems than you may have experienced in the past.

Project Plans: 10 Essential Elements
A project plan is more than just a Gantt chart, but do you know what you must have in your plan? This article takes you through the 10 essential elements your project plan has to have to help you achieve project management success.

How to Create a Gantt Chart Using Microsoft Excel
A Gantt chart is a popular bar chart that aims to show the timing of tasks or activities as they occur across time. Although the Gantt chart did not initially indicate the relationships between activities, this has become more common in current use as both timing and interdependencies between tasks can be identified.

21 Ways to Excel at Project Management
The popular project management e-book now fully updated and available as a website for the first time.