A project control methodology that integrates scope, schedule and cost by measuring planned value (PV), earned value (EV) and actual cost (AC) against an established baseline to assess performance and produce forecasts (e.g., cost and schedule variances and performance indices).

Principle

By quantifying work performance in a single currency or unit (EV) and comparing it to PV and AC, EVM yields objective performance measures (schedule and cost variances and indices) that can be used to forecast estimates at completion, subject to quality of measurement and baseline stability.

Demonstration

Illustrative scenario → Recognition: Project baseline sets Budget at Completion (BAC) = $1,000,000; at month 6 PV = $600,000, measured EV = $540,000, AC = $580,000. Action: compute CPI = EV/AC = 0.931; SPI = EV/PV = 0.900. Consequence: CPI < 1 and SPI < 1 indicate both cost and schedule underperformance and support revised EAC forecasting and corrective actions.

Misapplication

Using percent complete estimates that are not objectively measured (inflated EV), failing to update the baseline after authorized scope changes (misleading PV), or applying EVM metrics mechanically without assessing quality or scope changes yields deceptive performance readings.

Consequence

When implemented with disciplined scope control and reliable measurement, EVM enables early detection of variances, objective communication of status, and informed forecasting; when misused it creates false precision and can hide cost or schedule risks until late in the project.

Reversal

EVM is less appropriate for projects lacking a stable, measurable scope baseline (early‑stage R&D, exploratory projects) or for delivery models emphasizing rapid scope evolution (some agile contracts) unless adapted with compatible measurement conventions and rebaseline governance.

Boundary

Clearly within: capital projects or contracts with defined work breakdown structures, measurable progress criteria and established cost/schedule baselines. Boundary case: software projects using incremental agile delivery—EVM can be applied with story‑point to dollar mappings but requires methodological adjustments. Clearly outside: purely exploratory research with undefined deliverables.

Semantic Tension

Control and predictability (EVM) ↔ Flexibility and rapid scope change (agile methods); applying EVM imposes discipline that can conflict with adaptive development unless measurement and governance are reconciled.

Synthesis

Earned Value Management converts physical progress into integrated cost and schedule metrics; its diagnostic and forecasting power depends on objective measurement, stable baselines, and disciplined change control rather than on the formulas alone.