Page 98 - Untitled-1

CPM BASICS 77

CPM Basics

Regardless of the method used to create a project schedule, the first step is al-
ways the same. You must identify the work to be scheduled before you can deter-
mine when the work will be done. There are many ways that you can work up to
the point of developing the schedule. We recommended a few effective practices
in Chapter 2.1, Project Initiation Techniques. We will assume that you will utilize
these practices as we move to the next steps of developing the project schedule.

Reviewing these front-end steps:

• You will have identified the project objectives and constraints.
• You will have initiated strategic planning and performed a stakeholder

analysis.
• You will have developed a set of frameworks for the workscope and timing.
• You’ll use the WBS as a framework for identification of the project tasks.
• You’ll use the Project Milestone Schedule as a framework to develop the de-

tailed project schedule.

The next steps include:

• Creating a list of all the tasks to be performed.
• Estimating the probable duration of each task.
• Defining the precedence relationships between tasks.
• Identifying date constraints and imposed dates.

Let’s look at each of these in greater detail.

Defining Tasks A favored way of building the list of tasks is to use a work
breakdown structure that is based on either deliverables or phases. Actually,
where it is practical, I like to use a combined WBS, where the first level repre-
sents the phases (or project life cycle) and the next level represents the deliver-
ables within each phase. The WBS is then developed down to lower levels, such
as major components, subsets, or milestones within each deliverable, and then
further, down to groups of tasks that I like to call work packages. A work pack-
age is a set of tasks, usually under the responsibility of a single party, that repre-
sents a minor deliverable or milestone. Each task will have a single party
identified as the responsible owner. Tasks may have one or more resources as-
signed and may have budgets (later). Every task (like every project) has an iden-
tifiable start and finish.