Planning & Execution

Earned Value Management: Tracking Project Performance With Data

By Vact Published · Updated

Earned Value Management (EVM) is a project performance measurement technique that integrates scope, schedule, and cost data to provide an objective assessment of project health. Unlike status reports that rely on subjective assessments (“the project is on track”), EVM uses three measurable values to calculate whether the project is ahead or behind schedule and whether it is over or under budget. It answers the question every project sponsor asks: “Are we getting what we paid for?”

Earned Value Management: Tracking Project Performance With Data

The Three Core Values

EVM revolves around three measurements taken at any point during the project:

Planned Value (PV): The authorized budget assigned to scheduled work. In other words, how much work should have been completed by now based on the project plan. PV is derived from the project timeline and budget.

Earned Value (EV): The measure of work actually performed, expressed in budget terms. If a task was budgeted at $10,000 and is 50% complete, the earned value is $5,000. EV represents the value of work delivered.

Actual Cost (AC): The total cost incurred for the work performed. This is what the project has actually spent, regardless of how much work was completed.

Key Performance Indicators

From these three values, EVM calculates indicators that reveal project health:

Schedule Performance Index (SPI)

SPI = EV / PV

SPI measures schedule efficiency. An SPI of 1.0 means the project is exactly on schedule. Above 1.0 means ahead of schedule; below 1.0 means behind schedule.

  • SPI = 1.15 → 15% ahead of schedule
  • SPI = 0.80 → 20% behind schedule

Cost Performance Index (CPI)

CPI = EV / AC

CPI measures cost efficiency. A CPI of 1.0 means the project is exactly on budget. Above 1.0 means under budget; below 1.0 means over budget.

  • CPI = 1.10 → Getting $1.10 of value for every $1.00 spent
  • CPI = 0.75 → Getting $0.75 of value for every $1.00 spent

Schedule Variance (SV)

SV = EV - PV

A positive SV means the project has completed more work than planned. A negative SV means less work than planned.

Cost Variance (CV)

CV = EV - AC

A positive CV means the project is under budget. A negative CV means over budget.

A Practical Example

Consider a website redesign project with a total budget of $100,000 planned over 20 weeks. At week 10:

MetricValue
Planned Value (PV)$50,000 (50% of budget should be spent by week 10)
Earned Value (EV)$40,000 (40% of planned work is actually complete)
Actual Cost (AC)$55,000 (actual spending to date)

Calculations:

  • SPI = $40,000 / $50,000 = 0.80 (20% behind schedule)
  • CPI = $40,000 / $55,000 = 0.73 (27% over budget)
  • SV = $40,000 - $50,000 = -$10,000 (behind schedule by $10K of work)
  • CV = $40,000 - $55,000 = -$15,000 (over budget by $15K)

This project is in trouble: behind schedule and over budget. Without EVM, the project manager might report “we are about halfway done” and hope to catch up. With EVM, the data shows clearly that the project needs intervention.

Forecasting With EVM

EVM can forecast the likely total cost and completion date:

Estimate at Completion (EAC)

EAC = BAC / CPI (where BAC is Budget at Completion)

Using the example above: EAC = $100,000 / 0.73 = $136,986

If current cost trends continue, the project will cost approximately $137,000 instead of $100,000. This forecast gives the sponsor early warning to either increase the budget, reduce scope, or accept the overrun.

Estimate to Complete (ETC)

ETC = EAC - AC

ETC = $136,986 - $55,000 = $81,986

The project needs approximately $82,000 more to complete at the current efficiency rate.

Variance at Completion (VAC)

VAC = BAC - EAC

VAC = $100,000 - $136,986 = -$36,986

The project is forecasted to be approximately $37,000 over budget.

When to Use EVM

EVM is most valuable for:

  • Large projects with significant budgets where cost overruns have serious consequences
  • Fixed-price contracts where the vendor bears cost overrun risk
  • Government and defense projects where EVM is often required by regulation
  • Projects with clear deliverables where progress can be objectively measured

EVM is less practical for:

  • Small projects where the overhead of tracking exceeds the benefit
  • Highly agile projects where scope changes frequently by design — agile metrics like velocity and burndown charts serve better
  • Research and discovery work where outcomes are unpredictable

Implementing EVM

Step 1: Create the Work Breakdown Structure

A WBS breaks the project into measurable deliverables. Each work package must be estimable in cost and duration. Without a solid WBS, EVM data is meaningless.

Step 2: Assign Budgets

Assign a budget to each work package. The sum of all work package budgets equals the Budget at Completion (BAC). Distribute the budget across the project timeline to create the Planned Value curve.

Step 3: Define Progress Measurement Rules

Decide how to measure work completion. Common methods include:

  • 0/100: Work is either not started (0%) or complete (100%). Simple but only works for small tasks.
  • 50/50: Work is 0% until started, 50% when started, 100% when complete. Reduces subjectivity.
  • Percent complete: Estimated percentage at each reporting period. Most flexible but most subjective.

Step 4: Track and Report

Collect EV, PV, and AC data at regular intervals (weekly or biweekly). Calculate the indicators and plot them on an S-curve chart. Report trends to stakeholders in status reports.

EVM Pitfalls

Garbage in, garbage out. If the baseline plan is unrealistic, all EVM calculations are misleading. Start with realistic estimates using proven estimation techniques.

Measuring effort, not value. EVM measures work completed against the plan, not whether the right work was completed. A project can have perfect EVM scores while building something nobody needs.

Overhead. Tracking EVM requires discipline and effort. For small or fast-moving projects, the overhead may not justify the insight. Consider whether simpler project metrics would suffice.

Gaming the numbers. Teams under pressure may overstate completion percentages. Use objective measurement rules and verify completion with deliverable reviews.