Document

Filename

Length

Code

Why do we need to plan?

Why plan v1

4 pages

PM0501

Description

Outlines the case for planning, and why it needs to be carried out carefully and methodically.

The basic case for planning is presented, including a checklist for planning and a discussion of the limitations and things to look out for. As part of Starting the Project and probably within the Terms Of Reference) the Project Manager will need to sit down and work through this process. A process that will take time and effort, which he or she may need to justify as an investment in the project. Use the lists in this document to explain why Planning needs to be done, and done well

Includes

Eight Key Questions About Planning

Document

Filename

Length

Code

Tools and techniques

Elements of Planning v3

8 pages

PM0502

Description

Outlines the tools and techniques commonly used for planning.

The basic tools of planning are described including a highly simplified breakdown structure and a pair of documents that can be used to record information about tasks,  and a checklist for estimation.

In particular this document introduces the concept of the Breakdown Structure – a tool for reducing large complex issues and processes into constituent parts. It also discusses dependencies and the inter-relationship between tasks.

Includes

Project Task Description Sheet

Project Task List Record Sheet

Checklist for Estimation

Document

Filename

Length

Code

GANTT and bar charts

GANTT and Bar Charts v1

4 pages

PM0503

Description

Describes how to represent the schedule of activities that comprise a project plan.

Two basic techniques are discussed, the GANTT chart, or bar chart approach and activity networks. It shows how activities, resources, dependencies and milestones can be represented on the GANTT chart. It also introduces the concept the Critical Path.

Includes

Diagrams for basic Gantt Chart Layout

Document

Filename

Length

Code

Networks and Schedules

PM0504 Networks v1

5 Pages

PM0504

Description

Describes how to represent the schedule of activities that comprise a project plan.

This document discusses how to represent the activities in a project in a network diagram, what the basic building blocks are and how it can be used to determine the Critical Path, with a simple ‘10 Simple Steps to Determining the Critical Path for a Project’

Includes

10 Simple Steps to Determining the Critical Path for a Project’

Document

Filename

Length

Code

Change management

Change Management  v3

3 Pages

PM0505

Description

Describes how to control changes to the plans and objectives of a project

This document discusses how to handle changes to the requirements of a project, the use of Change Management, including the escalation procedures. A checklist for managing the acceptance or rejection of the Change request is presented. Requests for changes should be handled as Issues on the Issue Log

Includes

Change Checklist