Pert & CPM Project Scheduling Techniques

Project managers use Program Evaluation Review Technique (PERT) and Critical Path Method (CPM) to organize, schedule, and control complex projects. Although they originated in different industries, the two techniques share a common logical base: a network of activities linked by precedence relationships. This page explains the fundamentals, the differences, the steps to build a network, and practical tips for applying these methods in realworld projects.

Why Use PERT/CPM?

• Visibility They turn a vague list of tasks into a clear visual map that shows which activities depend on others.
• Time prediction By estimating the duration of each activity, the methods produce a project completion date and highlight potential delays.
• Resource prioritisation The critical path identifies the tasks that directly affect the finish date, guiding where to allocate manpower, equipment, or budget.
• Risk management PERTs probabilistic estimates allow managers to assess schedule risk and build contingency buffers.

Core Concepts

Activities and Events

An activity (or task) is a work package that consumes time, cost, or resources. An event marks the start or finish of one or more activities. In a network diagram, activities are usually drawn as arrows (activityonarrow) or as boxes (activityonnode). Events are the circles or nodes that connect those arrows.

Precedence Relationships

Activities can be linked by four types of logical relationships:

Relationship	Notation	Description
FinishtoStart (FS)	A B	Task B cannot start until task A finishes.
StarttoStart (SS)	A B	Task B cannot start until task A starts.
FinishtoFinish (FF)	A B	Task B cannot finish until task A finishes.
StarttoFinish (SF)	A B	Task B cannot finish until task A starts.

Critical Path

The critical path is the longest sequence of activities from the project start to its finish. Any delay on a critical activity directly prolongs the projects overall duration. Activities not on the critical path have float (or slack), which is the amount of time they can be delayed without affecting the finish date.

PERT vs. CPM

Both methods compute the same network metrics, but they differ in how they treat activity durations:

• PERT uses three estimatesoptimistic (O), most likely (M), and pessimistic (P)to calculate an expected duration E = (O + 4M + P) / 6. This probabilistic approach is ideal for researchoriented or highly uncertain projects.
• CPM assumes a single deterministic duration for each activity, obtained from historical data or expert judgment. It is more common in construction, manufacturing, and engineering projects where task times are wellknown.

StepbyStep Guide to Building a PERT/CPM Network

1. Define the scope: List every deliverable and break it down into work packages.
2. Identify activities: Write a clear description for each activity, assign a unique ID, and estimate its duration (single value for CPM, three values for PERT).
3. Establish dependencies: Determine which activities must precede others and note the type of precedence.
4. Create the network diagram: Use the activityonnode (AoN) format for easier calculation. Each node represents an activity; arrows show the flow.
5. Calculate forward pass: Starting at the first node, compute the Early Start (ES) and Early Finish (EF) for each activity.
   • ES = maximum EF of all predecessor activities.
   • EF = ES + duration.
6. Calculate backward pass: Working from the final node, compute the Late Start (LS) and Late Finish (LF).
   • LF = minimum LS of all successor activities.
   • LS = LF duration.
7. Determine float: Float = LS ES (or LF EF). Activities with zero float belong to the critical path.
8. Analyze results: Review the critical path, identify bottlenecks, and evaluate the impact of any schedule changes.
9. Monitor and update: As the project progresses, revise actual durations and recompute the network to keep the schedule realistic.

Sample Project Building a Small Pavilion

Below is a simplified illustration of a CPM schedule for a pavilion construction. The numbers are deterministic durations expressed in days.

In this example, the longest path is A B E F D, totaling 5 + 10 + 12 + 7 + 8 = 42 days. This sequence is the critical path; any delay in excavation, foundation, walls, finishing, or roof will push the overall completion date.

Best Practices for Using PERT/CPM

• Keep the network simple. Oversplitting tasks creates a cluttered diagram and increases calculation errors.
• Validate dependencies. Talk to the team to confirm that the logical order reflects actual workflow.
• Use software wisely. Tools such as Microsoft Project, Primavera P6, or opensource alternatives automate forward and backward passes, but still require accurate inputs.
• Update regularly. Treat the network as a living document revise durations when actual performance data become available.
• Combine with resource leveling. CPM provides timing; integrating a resourceallocation module prevents overallocation and reveals realistic start dates.
• Plan for risk. In PERT, examine the variance () of each activity: = ((PO)/6). Adding standard deviations along the critical path can produce confidence intervals for the project finish date.

Common Pitfalls to Avoid

1. Ignoring float. Treating all tasks as equally critical leads to wasted effort on noncritical activities.
2. Underestimating uncertainty. Using a single deterministic duration for a highly variable task can give a false sense of security.
3. Failing to capture recurring dependencies. When a task must repeat (e.g., weekly testing), model it as a loop or separate activities to avoid hidden delays.
4. Overreliance on the tool. Software can compute numbers, but decisionmaking still requires human judgment about scope changes and resource constraints.

When to Choose PERT Over CPM (or Viceversa)

Scenario	Preferred Technique	Reason
R&D projects with high uncertainty	PERT	Threepoint estimates capture variability and give probabilistic completion dates.
Construction of a commercial building	CPM	Activity durations are wellknown from past projects; deterministic scheduling is sufficient.
Software development using agile sprints	Hybrid	Use CPM for highlevel milestones and PERT for highrisk features.
Government procurement with strict deadlines	CPM	Regulatory compliance demands precise schedule tracking.

Conclusion

Pert and CPM remain essential tools for project managers seeking to visualize work flow, estimate completion dates, and control schedule risk. By constructing a logical network, calculating early and late dates, and isolating the critical path, teams gain the insight needed to allocate resources effectively and respond to change. Whether you adopt PERTs probabilistic approach for highuncertainty environments or CPMs deterministic simplicity for welldefined tasks, the fundamental stepsdefining activities, establishing dependencies, and continuously updating the scheduleare the same. Mastering these techniques enables you to keep projects on track, meet stakeholder expectations, and deliver results on time.