Exploring trends and developments
in project management today.

Project Smart Logo

Subscribe to RSS Feed Get the Latest Articles

Project Planning A Step by Step Guide

By Duncan Haughey, PMP
Project Plan Gantt Chart

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.

This article looks at a simple practical approach to project planning. On completion of this guide you should have a sound project planning approach that you can use for future projects.

Step 1 Project Goals

A project is successful when the needs of the stakeholders have been met. A stakeholder is anybody directly or indirectly impacted by the project.

As a first step it is important to identify the stakeholders in your project. It is not always easy to identify the stakeholders of a project, particularly those impacted indirectly. Examples of stakeholders are:

  • The project sponsor
  • The customer who receives the deliverables
  • The users of the project outputs
  • The project manager and project team

Once you understand who the stakeholders are, the next step is to establish their needs. The best way to do this is by conducting stakeholder interviews. Take time during the interviews to draw out the true needs that create real benefits. Often stakeholders will talk about needs that aren't relevant and don't deliver benefits. These can be recorded and set as a low priority.

The next step once you have conducted all the interviews and have a comprehensive list of needs is to prioritise them. From the prioritised list create a set of goals that can be easily measured. A technique for doing this is to review them against the SMART principle. This way it will be easy to know when a goal has been achieved.

Once you have established a clear set of goals they should be recorded in the project plan. It can be useful to also include the needs and expectations of your stakeholders.

This is the most difficult part of the planning process completed. It's time to move on and look at the project deliverables.

Step 2 Project Deliverables

Using the goals you have defined in step 1, create a list of things the project needs to deliver in order to meet those goals. Specify when and how each item must be delivered.

Add the deliverables to the project plan with an estimated delivery date. More accurate delivery dates will be established during the scheduling phase, which is next.

Step 3 Project Schedule

Create a list of tasks that need to be carried out for each deliverable identified in step 2. For each task identify the following:

  • The amount of effort (hours or days) required to complete the task
  • The resource who will carryout the task

Once you have established the amount of effort for each task, you can workout the effort required for each deliverable and an accurate delivery date. Update your deliverables section with the more accurate delivery dates.

At this point in the planning you could choose to use a software package such as Microsoft Project to create your project schedule. Alternatively use one of the many free templates available. Input all of the deliverables, tasks, durations and the resources who will complete each task.

A common problem discovered at this point is when a project has an imposed delivery deadline from the sponsor that is not realistic based on your estimates. If you discover that this is the case you must contact the sponsor immediately. The options you have in this situation are:

  • Renegotiate the deadline (project delay)
  • Employ additional resources (increased cost)
  • Reduce the scope of the project (less delivered)

Use the project schedule to justify pursuing one of these options.

Step 4 Supporting Plans

This section deals with plans you should create as part of the planning process. These can be included directly in the plan.

Human Resource Plan

Identify by name the individuals and organisations with a leading role in the project. For each describe their roles and responsibilities on the project.

Next, describe the number and type of people needed to carryout the project. For each resource detail start dates, estimated duration and the method you will use for obtaining them.

Create a single sheet containing this information.

Communications Plan

Create a document showing who needs to be kept informed about the project and how they will receive the information. The most common mechanism is a weekly/monthly progress report, describing how the project is performing, milestones achieved and work planned for the next period.

Risk Management Plan

Risk management is an important part of project management. Although often overlooked, it is important to identify as many risks to your project as possible and be prepared if something bad happens.

Here are some examples of common project risks:

  • Time and cost estimates too optimistic
  • Customer review and feedback cycle too slow
  • Unexpected budget cuts
  • Unclear roles and responsibilities
  • Stakeholder input is not sought or their needs are not properly understood
  • Stakeholders changing requirements after the project has started
  • Stakeholders adding new requirements after the project has started
  • Poor communication resulting in misunderstandings, quality problems and rework
  • Lack of resource commitment

Risks can be tracked using a simple risk log. Add each risk you have identified to your risk log and write down what you will do in the event it occurs and what you will do to prevent it from occurring. Review your risk log on a regular basis adding new risks as they occur during the life of the project. Remember, when risks are ignored they don't go away.

Congratulations. Having followed all the steps above you should have a good project plan. Remember to update your plan as the project progresses and measure progress against the plan.

Comments page 1 of 1
Click here to add a comment
Ram Kishor Sankhla
Posted 7 days ago
It's really very excellent material for better understaning of project planing. I'm thankful to you for providing nice matter.
md gayasuddin
Posted 17 days ago
this is a good learning material.
Prashant Aherkar
Posted 20 days ago
Thank you..This will help me lot for Project Planning.
rwgreen1173
Posted 65 days ago
I thought this was a good framework... but the hardest part is lacking something.

Estimate - The amount of effort (hours or days) required to complete the task.

I guess you are just guessing or asking the people required to do the work for how long they think it will take?

From a project management perspective how do you know they aren't padding or grossly underestimating?
Denny Joseph
Posted 68 days ago
Thank you for this excellent tutorial!
Mpumelelo Sibanda
Posted 95 days ago
Coming across this was impeccable for me when I was under pressure of an IT Project Management module assignment. It merged very well with other components of my resources for the assignment. I am very grateful.
Craig Brown
Posted 110 days ago
In response to the comment "Don't try this with software."

In fact, a project manager taking an agile approach still has to address these issues, and this template can assist in framing the approach.

As you note, Agile delivers iteratively, and the deliveries are planned in detail in small increments, but there still needs to be a higher level plan dealing with resources, risks and so on.

Agile doesn't mean no planning.

Craig Brown
James Craig
Posted 162 days ago
I found this more than interesting in completing a college assignment in Media, i had to talk about "Project planning" and this was fantastic. Thank You!
Duncan
Posted 238 days ago
This doesn't only apply to software development. It could be used for many other types of project.

The main point I'm trying to get across here is, do some planning before you start the work. Think about what it is you're going to deliver, how you're going to deliver it and what risks and issues might occur along the way.

I'm interested in the fact the word "Agile" has come up again when discussing planning. In his recent article "The Elements of a Good Feasibility Study" Tim Bryce says, "I have read where some people in the IT field, such as the "Agile" methodology proponents, consider Feasibility Studies to be a colossal waste of time."

I'd like to know what Agile development guys think and how they plan, if they plan and if not what issues they face and how they overcome them.
ep
Posted 238 days ago
So what do you suggest?
Don't try this with software
Posted 238 days ago
Iterative software planning does not work this way. In fact, neither does any type of effective software planning work this way - but we like to think that it does - don't try the above process if you want to become an agile software development manager.
 

Article Categories

Related Articles

Developing the Project Plan
Whether you call it a project plan or a project timeline, it is absolutely imperative that you develop and maintain a document that clearly outlines the project milestones and major activities required to implement your project.

Demand a Strong Project Plan
You've engaged a reputable consulting firm to perform a large systems project. You've prepared an RFP, carefully reviewed the responses, scrutinised the consultancy's oral presentation, and ultimately negotiated and signed a well-written statement of work (SOW). Don't stop there.

Technology Technology Project Planning: Too Much of a Good Thing
When it comes to any technology project, you cannot plan enough, or so we have been led to believe. The experts advice over the years to plan more and better is what most of us needed to hear, but it may be time to reconsider our conditioned response to project planning. You truly can have too much of a good thing.

How to Plan and Schedule More Complex Projects
Gantt charts are useful tools for analysing, planning and controlling projects. When a complex or multi-task project is under way, Gantt charts assist in monitoring whether the project is on schedule, or not. If not, the Gantt chart allows you to easily identify what actions need to be taken in order to put the project back onto schedule.

GenSight Project Portfolio Management

Get Project Management Templates
Project Smart is selling project management templates and tools developed and refined in a real project environment.