Activity Network: The Essential Guide to Planning, Scheduling and Optimisation

Owner Other 2. April 2025 | 0

In programme management and project delivery, an Activity Network sits at the heart of how teams turn ideas into reality. From the earliest planning sessions to the final handover, the activity network provides a clear map of tasks, dependencies, durations and milestones. This comprehensive guide explains what an activity network is, why it matters, and how to build, analyse and optimise one for robust project results.

What is an Activity Network?

An Activity Network is a graphical representation of the sequence and interdependencies of activities needed to complete a project. It shows how activities relate to one another, which tasks must precede others, and where buffers or float can be allocated. In practice, the activity network helps project managers determine the earliest possible finish date, identify the critical path, and manage risk across the timeline.

There are two primary ways to structure an activity network: Activity-on-Node (AON) and Activity-on-Arrow (AOA). Each format has its own strengths, and the choice often depends on industry tradition, software capability, or personal preference. In the AON approach, the nodes represent activities and the arrows denote dependencies. In AOA, arrows depict activities and nodes represent events or milestones. Both methods yield the same essential insights about sequencing and timing, but the notation can influence the ease of communication with stakeholders.

Historical Context: From CPM to PERT and Beyond

The modern activity network owes much to early work on project management methods. The Critical Path Method (CPM) emerged in the 1950s as a means to identify the longest chain of dependent tasks and thus the minimum project duration. Later, the Programme Evaluation and Review Technique (PERT) added probabilistic time estimates to better handle uncertainty. Today, the activity network has evolved with digital tools, enabling dynamic scheduling, resource levelling, and scenario modelling. Regardless of the terminology, the underlying idea remains the same: map, measure and optimise the sequence of work to deliver outcomes on time and within budget.

Key Components of an Activity Network

Activities – discrete tasks with defined durations and resource requirements.
Dependencies – logical relationships that determine the order of activities (finish-to-start, start-to-start, finish-to-finish, start-to-finish).
Durations – the estimated time required to complete each activity, expressed in days or hours.
Milestones – significant points in the project, such as design release or user acceptance.
Critical Path – the longest path through the network, representing the minimum project duration.
Slack/Float – the amount of time an activity can be delayed without affecting the overall project end date.
Early Start/Finish (ES/EF) and Late Start/Finish (LS/LF) – timing windows that determine flexibility and risk.

Understanding these components in the Activity Network framework allows managers to prioritise work, allocate resources efficiently and anticipate bottlenecks before they become costly delays.

Types of Activity Network Diagrams

Activity-on-Node (AON)

The AON model places each activity on a node. Arrows indicate dependencies from one activity to another. This approach is widely taught in UK project management courses and is favoured for its straightforward, intuitive layout. AON diagrams lend themselves well to advanced timing calculations, critical path analysis, and software implementations that rely on node-based sequencing.

Activity-on-Arrow (AOA)

Constructing an Effective Activity Network

Step 1: Define the Scope and Break Down Work

Step 2: Identify Dependencies

Dependencies capture the sequencing constraints. Common relationships include:

Finish-to-Start (FS): A must finish before B can start.
Start-to-Start (SS): A and B start together or in a linked fashion.
Finish-to-Finish (FF): A must finish before B finishes.
Start-to-Finish (SF): A must start before B finishes (less common in traditional CPM/PERT planning).

Capturing accurate dependencies is crucial, as the entire network hinges on the logic chain created by these relationships.

Step 3: Estimate Durations

Assign durations to each activity, using historical data, expert judgement or a combination of both. In some projects with high uncertainty, probabilistic estimates (e.g., optimistic, pessimistic, most likely) can provide a more realistic view of possible outcomes and help in risk analysis.

Step 4: Build the Network Diagram

Create the diagram in the chosen notation (AON or AOA). Ensure all activities are connected logically with the appropriate dependencies. Include start and finish milestones for traceability and to support later calculations.

Step 5: Analyse the Network

Compute the Early Start, Early Finish, Late Start and Late Finish for each activity. Identify the critical path—the sequence of activities with zero slack that determines the project duration. Use this information to focus management attention where it matters most.

Critical Path, Float and Timing Calculations

What is the Critical Path?

The critical path is the longest path through the activity network, measured in duration. It represents the chain of activities that cannot be delayed without extending the project end date. Any delay on a critical path activity directly impacts the project’s completion time.

Slack and Float

Slack (or float) is the amount of time an activity can be delayed without delaying the project finish date. Activities on the critical path have zero slack. Others may have positive slack, offering scheduling flexibility and a cushion against uncertainty.

Forward and Backward Passes

The standard method to compute ES/EF and LS/LF is through two passes across the network: a forward pass to establish ES/EF, and a backward pass to determine LS/LF, factoring in dependencies and durations. Integrated with the activity network, these calculations yield a complete timetable, resource plan and risk profile.

Practical Applications of the Activity Network

Beyond theoretical scheduling, the activity network supports several practical objectives:

On-time delivery – by highlighting the critical path, managers can prioritise tasks that would otherwise delay the project.
Scenario planning – compare “what-if” scenarios, such as accelerated pace or scope changes, to see how the end date shifts.
Resource optimisation – align resource availability with task timing to avoid over-allocation or idle periods.
Risk management – identify where delays will cascade and implement mitigations in advance.
Communication clarity – a shared, visual model helps stakeholders understand sequencing and constraints quickly.

Resource Constraints and the Need for Leveling

Crashing and Optimising the Schedule

Crashing involves adding resources or increasing work effort to shorten the duration of critical path activities. While it can accelerate delivery, it comes with higher cost and potential quality or risk implications. The activity network framework helps quantify those trade-offs, enabling decision-makers to select the most cost-effective crashing options while preserving project objectives.

Common Pitfalls in Activity Network Management

Even with a sound diagram, several pitfalls can undermine the benefits of an activity network:

Incomplete dependencies – missing links can yield unrealistic schedules and hidden risks.
Inaccurate durations – optimistic estimates lead to an overoptimistic timetable and surprise delays later.
Ignoring resources – a plan that looks perfect on paper may collapse if staff or equipment are unavailable.
Overcomplication – adding unnecessary detail can obscure the critical path and reduce clarity.
Static plans in dynamic environments – failure to update the network as conditions change diminishes usefulness.

Tools and Software for Activity Network Planning

Microsoft Project and Project Online, with built-in CPM/PERT capabilities and Gantt views.
Primavera P6, widely used in engineering, construction and large-scale programmes for complex networks.
Open-source and cloud-based alternatives offering AON and AOA support and scenario modelling.
Specialist network diagram software that emphasises dependencies, critical paths and float analysis.

When selecting a tool, focus on how well it supports the core activity network workflow: defining tasks, modelling dependencies, calculating ES/EF/LS/LF, identifying the critical path and enabling what-if analyses. A tool that integrates with resource calendars, financial data and risk registers will deliver the most value for robust project governance.

Practical Examples: A Simple Activity Network in Action

Consider a small project with five activities:

A: Requirements Gathering (4 days)
B: System Design (5 days) – depends on A
C: Hardware Procurement (3 days) – depends on A
D: Implementation (6 days) – depends on B and C
E: User Acceptance Testing (2 days) – depends on D

In this network, the critical path runs from A to B to D to E, totaling 4 + 5 + 6 + 2 = 17 days. Activity C runs in parallel with B and may offer some flexibility, but because D depends on both B and C, C’s timing still influences the overall finish. By calculating ES/EF and LS/LF, the project manager can determine which activities require closest attention and where resource adjustments could shave days off the schedule without compromising quality.

Activity Network: The Essential Guide to Planning, Scheduling and Optimisation