EVM (Earned Value Management)

Three numbers tell the state

EVM lines up three values on the same axis: PV (planned value — what should be done by now, per plan), EV (earned value — what is actually complete), and AC (actual cost — what has actually been spent). Take week 5 of a 10-week, $100k project: the plan says half should be done (PV $50k), actual completion is 40% (EV $40k), and spend is $48k (AC). Schedule performance (SPI 0.8) and cost performance (CPI 0.83) fall straight out of those three numbers.

Why it matters

A report of "80% complete" says nothing about whether that 80% is ahead of or behind plan, cheap or expensive against budget. EVM separates the schedule problem from the cost problem: in the example above, the project is both slow (EV below PV) and expensive (AC above EV). It gives you a language that distinguishes being busy from having completed value.

Common misconceptions

EVM is often filed away as a big-government-program discipline. A simplified variant sets the value axis to task weights instead of money. Weights cannot meet AC — the units differ, so no cost indicators — but SPI, a ratio whose units cancel, still holds, and SV comes out as a difference on the same weight-value axis (percentage points). It is the light way onto the schedule axis with no cost accounting. The opposite misconception is believing adoption alone makes the numbers honest: fill EV from a gut feel and EVM becomes precise-looking numerology. A measurement method that judges completion comes first. And EVM is a conversation tool before it is a control tool: in organizations where bad numbers bring blame, the field learns to call EV generously — and every indicator collapses together at that moment.