Earned Value Management
Also known as: EVM
Project performance measurement integrating scope, schedule, and cost; standardized in ANSI/EIA-748 and required in US federal contracting.
Earned Value Management (EVM) is the project performance measurement system integrating scope, schedule, and cost into a single set of indices used to track and forecast project performance. EVM measures three values at any reporting date: Planned Value (the budgeted cost of work scheduled), Earned Value (the budgeted cost of work performed), and Actual Cost (the actual cost of work performed). Derived indices include Cost Variance (EV - AC), Schedule Variance (EV - PV), Cost Performance Index (EV / AC), and Schedule Performance Index (EV / PV), with extrapolated estimates at completion. EVM originated in 1962 US Department of Defense Cost/Schedule Control Systems Criteria (C/SCSC, the original 35 criteria) and was generalized as ANSI/EIA-748 (1998, current revision 2013), required on US federal cost-reimbursement and major-acquisition contracts above defined thresholds. EVM is also documented in PMI's Practice Standard for Earned Value Management.
Core components
- Three primary metrics: Planned Value (PV / BCWS), Earned Value (EV / BCWP), Actual Cost (AC / ACWP)
- Variances: Cost Variance (CV = EV - AC), Schedule Variance (SV = EV - PV)
- Indices: Cost Performance Index (CPI = EV / AC), Schedule Performance Index (SPI = EV / PV)
- Estimate at Completion formulae (EAC = BAC / CPI most common, with multiple alternatives reflecting different assumptions)
- To-Complete Performance Index (TCPI)
- Work Breakdown Structure and Performance Measurement Baseline (PMB) foundation
- Integration with scheduling network and cost-estimating systems
Primary use case
Performance measurement on US federal cost-reimbursement and major-acquisition contracts (DoD, NASA, DOE); ANSI/EIA-748 compliance certification by major prime contractors; internal project performance monitoring across construction, engineering, and complex systems-development projects; input to project status reporting, executive dashboards, and contract deliverable forecasts; academic reference in project-management research and pedagogy.
Common criticisms
- EVM's Schedule Performance Index has a well-known mathematical pathology: as projects approach completion, SPI converges to 1.0 even on substantially late projects because cumulative EV approaches cumulative PV — Lipke (2003) developed Earned Schedule (ES) as a duration-based correction, now widely discussed but unevenly adopted
- Vanhoucke's research at Ghent has documented extensive empirical limitations in EVM forecasting accuracy, particularly in early project phases
- EVM's accuracy depends on accurate Performance Measurement Baseline establishment, which is empirically rare and frequently rebaselined in ways that reset performance measurement, masking true performance trends — a practice GAO and DoD oversight reports have repeatedly criticized
- EVM presumes deterministic plans inappropriate for agile / iterative delivery, motivating Agile EVM proposals (Sulaiman et al.) with mixed reception
- ANSI/EIA-748 compliance certification has become a ceremonial industry of itself, with critics noting compliance does not translate to actual measurement effectiveness
- in cost-reimbursement contracting EVM creates contractor incentive to optimize EV reporting rather than actual delivery
- smaller projects find EVM disproportionate to the complexity it addresses.
Lineage
- Siblings
- PMBOK Guide, DoD 5000 Series, Critical Chain Project Management