Project Plan

Description

The Project Plan answers the question how something will be achieved, usually in response to a document that describes what is wanted, such as the Mandate or Requirements.

Each phase will include an update (or complete revision) to a previous Project Plan. The plan will typically be of increasing detail as the project progresses into its more complex and resource-hungry stages. The Project Plan for Discovery may be thus relatively simple, whilst the Delivery phase may involve significant change management aspects. Every project is different, however, and plans may vary significantly from project to project.

Project plans often have a false certainty that, given a set of actions, a defined result will occur. Particularly with change projects this is seldom true and significant effort should be put into considering risks, mitigation and contingencies. Scenario planning may also be employed, where different paths of events are considered and preparation made for these differing eventualities.

Template

Introduction

Briefly give contextual information so the reader can make sense of the following information. Reference the documents that give detail of 'what' is required.

Objectives

Describe the intent in the project, including outcomes and deliverable outputs that lead to those outcomes. This may also include targets, such as what should be delivered when, and constraints, which limit the approaches that may be used.

In effect, this section is usually a summary or replacement of the Requirements document.

Approach

Describe the overall approach being taken to the project and the reason for this. Also mention other approaches and reasons why these are not being used (for example why a slow and careful approach is being used over a quick and forced change).

Activities

Detail major activities that will be undertaken. This is typically in more detail for the near term and broader action for the future.

Risks

Describe key risks and what will be done about these, such as early actions to reduce probability of them occurring and plans to manage them should they occur.

Risk	Analysis	Action

Dependencies

Describe dependencies on other projects or other activities.

Also note projects or activities that are dependent upon this project.

Project/activity	Relationship	Notes

Management

Describe the methods by which the project will be managed, including reporting structures, meetings, documentation, etc.

Resources

Describe the resources that will be needed for the project. This should include accurate detail for the near term. Longer-term resources may be more of an estimate.

Activity	Resource	Notes

Timescales

Show the overall timescales of the overall project and the detail of the next phase. This beings together the activities and resources above, and may include contingency for identified risks.

Note that this section may include a cut-and-paste diagram from a spreadsheet or project management software.

Costs

List the costs of completing both the next phase and the overall project. Depending on how the project is resourced, this may include time costs of internal people and expenditure on external consultants, as well as any further costs such as for printing or computer hardware.

Project Plan

Description

Template

Introduction

Objectives

Approach

Activities

Risks

Dependencies

Management

Resources

Timescales

Costs

See also

Site Menu

You can buy books here

Quick links

Disciplines

Techniques

Principles

Explanations

Theories

And