Schedule Network Analysis, Critical Path, and EVM

Introduction: Quantitative Project Forecasting

Project leadership requires moving beyond subjective gut feelings and static Gantt chart displays. When executive stakeholders ask, “Are we on schedule?” or “Will this project finish within budget?”, professional project managers do not provide vague assurances. They deploy mathematical network analysis and objective performance indices.

Two mathematical disciplines form the core of predictive project control: the Critical Path Method (CPM) for deterministic schedule calculation, and Earned Value Management (EVM) for integrated cost and schedule performance measurement. Mastering these computational models is mandatory for PMP certification and enterprise project success.

Core Concepts: The Critical Path Method (CPM)

The Critical Path is the sequence of dependent activities that represents the longest path through a project network diagram, determining the shortest possible duration to complete the project. Activities on the critical path have Zero Total Float (Slack); any delay in a critical path activity immediately delays the project completion date.

Schedule calculation uses a two-pass algorithm across the Precedence Diagramming Method (PDM) network:

1. Forward Pass (Calculates Early Dates): Traverses the network from start to finish, calculating the Early Start (ES) and Early Finish (EF) dates:

   $$ ext{EF} = ext{ES} + ext{Duration} – 1$$

   When multiple predecessors converge, the successor’s Early Start is the latest EF of all converging predecessors.

2. Backward Pass (Calculates Late Dates): Traverses the network from finish to start, calculating the Late Finish (LF) and Late Start (LS) dates:

   $$ ext{LS} = ext{LF} – ext{Duration} + 1$$

   When multiple successors converge backward, the predecessor’s Late Finish is the earliest LS of all converging successors.

3. Total Float (TF): The amount of time an activity can be delayed from its early start without delaying the project finish date:

   $$ ext{Total Float} = ext{LS} – ext{ES} = ext{LF} – ext{EF}$$

Deep Dive: Schedule Compression Techniques

When external market pressures or delays require shortening the project schedule, managers evaluate two distinct compression techniques:

• Crashing: Adding resources to critical path activities for the least incremental cost (e.g., approving overtime, hiring specialized contractors). Crashing always increases project costs.
• Fast Tracking: Taking activities that were originally planned in sequence and performing them in parallel (e.g., beginning software development before architectural design is 100% signed off). Fast tracking does not increase cost, but it dramatically increases project risk and frequently triggers expensive rework.

Deep Dive: Earned Value Management (EVM) Computational Models

Earned Value Management integrates three fundamental dimensions of project health:

1. Planned Value (PV): The authorized budget assigned to scheduled work to be completed by a given date.
2. Earned Value (EV): The measure of work performed expressed in terms of the budget authorized for that work ($$ ext{EV} = ext{BAC} imes % ext{Completed}$$).
3. Actual Cost (AC): The total realized cost incurred in accomplishing the work that the EV measured.

Performance Variances & Indices

Forecasting Future Performance (EAC)

If current cost variances are expected to continue at the current rate of efficiency throughout the remainder of the project, the projected Estimate at Completion (EAC) is calculated as:

$$ ext{EAC} = rac{ ext{BAC}}{ ext{CPI}}$$

Case Study: Recovering an At-Risk Infrastructure Project Using EVM Forecasting

To appreciate how Earned Value Management drives executive decisions, consider a major cloud datacenter expansion project with an approved Budget at Completion ($$text{BAC} = $2,000,000$$) and an 18-month duration. At the end of Month 6, the executive sponsor reviewed accounting ledger statements showing total expenditures of $$text{AC} = $800,000$$, while the baseline schedule indicated that 40% of the project should have been finished ($$text{PV} = $800,000$$). Based on costs matching planned value, the sponsor assumed the project was healthy.

However, the project manager conducted formal EVM physical progress inspections and discovered that the team had only completed 30% of the physical deliverables ($$text{EV} = text{BAC} times 30% = $600,000$$). Calculating the diagnostic indices revealed severe distress:

• $$text{Schedule Variance (SV)} = text{EV} – text{PV} = $600,000 – $800,000 = -$200,000$$ ($$text{SPI} = 0.75$$, project is 25% behind schedule)
• $$text{Cost Variance (CV)} = text{EV} – text{AC} = $600,000 – $800,000 = -$200,000$$ ($$text{CPI} = 0.75$$, project is consuming $1.33 for every $1.00 of deliverable value)
• $$text{Estimate at Completion (EAC)} = frac{text{BAC}}{text{CPI}} = frac{$2,000,000}{0.75} = $2,666,667$$ (projected $666,667 cost overrun!)

Armed with objective EVM data, leadership immediately instituted targeted critical path crashing and reorganized vendor contracts, arresting cost leakage and preventing complete project cancellation.

Common Mistakes & Practical Pitfalls

• Assuming Positive SV at Project End Indicates Early Completion: At the final conclusion of any project, 100% of planned work is finished, meaning $$ ext{EV} = ext{PV}$$ and Schedule Variance becomes zero. SV is a monetary proxy for schedule progress, but near project completion, it loses diagnostic sensitivity.
• Crashing Non-Critical Path Activities: Adding resources to an activity that has 15 days of float spends money without reducing total project duration by even one minute. Schedule compression must always focus exclusively on critical path activities.
• Confusing Total Float with Free Float: Total Float is the delay permitted without impacting the project finish date. Free Float is the delay permitted on an activity without delaying the Early Start of any immediate successor activity.

Exam Connection: Certification Blueprint Alignment

This module aligns directly with competencies evaluated on the Project Management Professional Practice examination:

• Executing two-pass network diagram calculations to find the Critical Path and Float.
• Computing Cost Variance, Schedule Variance, CPI, and SPI from scenario numbers.
• Calculating Estimate at Completion (EAC) and Estimate to Complete (ETC).
• Recommending between Fast Tracking and Crashing under budget vs. schedule constraints.

Key Takeaways

• The Critical Path is the longest path through the network and possesses zero total float.
• $$ ext{CPI} = ext{EV} / ext{AC}$$; values below 1.0 indicate cost overruns.
• $$ ext{SPI} = ext{EV} / ext{PV}$$; values below 1.0 indicate schedule delays.
• Crashing increases cost; Fast Tracking increases risk of rework.

Knowledge Check

1. A project has a Budget at Completion (BAC) of $500,000. At milestone check, the Earned Value (EV) is $200,000 and the Actual Cost (AC) is $250,000. What is the Cost Performance Index (CPI) and is the project under or over budget?
   Answer: $$ ext{CPI} = rac{$200,000}{$250,000} = 0.80$$. Since $$ ext{CPI} < 1.0$$, the project is over budget (spending $1.00 to receive $0.80 of value).
2. If an activity has an Early Start of Day 4, an Early Finish of Day 9, a Late Start of Day 10, and a Late Finish of Day 15, what is its Total Float?
   Answer: $$ ext{Total Float} = ext{LS} – ext{ES} = 10 – 4 = 6 ext{ days}$$ (or $$ ext{LF} – ext{EF} = 15 – 9 = 6 ext{ days}$$).
3. Which schedule compression technique should be selected if the project is severely delayed, no additional budget is available, but the team is willing to accept increased execution risk?
   Answer: Fast Tracking.

Next Step in Curriculum

Advance to the final module: Risk Management, Quality Control, and Agile Hybrid Delivery, or practice network calculations in the assessment track.