Course Preview

Earned Value Management for IT Projects

Earned value management compares the budgeted value of completed work with the value planned and the cost incurred. IT project teams use the comparison to detect cost and schedule trouble and forecast likely outcomes from an approved baseline.

itEngineering leadership and delivery management | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don’t Panic — Earned Value Management for IT Projects

Earned value management, or EVM, is the discipline of asking whether a project has actually finished the work it planned before congratulating its spending. This is useful because a budget report has a small but persistent design flaw: spending less than planned can mean efficient delivery, or it can mean the work has not happened. Numbers do enjoy ambiguity when left unsupervised.

The antidote is three values at one status date, the reporting cutoff shared by the schedule, progress evidence, and costs. Planned value, or PV, is the budgeted work that should be complete. Earned value, or EV, is the budgeted work that is actually complete. Actual cost, or AC, is what that completed work cost. Keep those three aligned and the arithmetic can tell a coherent story. Let them come from unrelated dates and systems and the arithmetic will still work, which is the worrying part.

The course’s central object is the performance measurement baseline, the time-phased arrangement of authorized scope, schedule, and budget. It turns deliverables into control accounts and work packages, then gives each package a way to earn value. A migration wave can earn value when its units are accepted. An interface can earn it through weighted milestones. Hours spent, tickets opened, and story points do not become completed scope merely by being enthusiastic.

Two comparisons then matter. Cost variance compares EV with AC: did completed work cost more or less than its budgeted value? Schedule variance compares EV with PV: is the planned budgeted work actually complete? The latter is measured in budget units, not days. For calendar impact, the network schedule and critical path are still waiting patiently in the next room.

The useful question is not whether a CPI or SPI number looks tidy. It is whether the team can trace it to a control account, explain the cause, forecast the consequence, and choose an action without rewriting history. The Cheatsheet holds the formulas and diagnostic patterns. The practice reference shows the calculation sequence. The exercise turns a status snapshot into a control-account review. Field Notes concentrates on the places where a plausible report becomes misleading.

EVM does not certify that a product is useful, secure, or even based on a realistic plan. It measures performance against the approved plan. That limit is not a defect. It is the reason the method is most helpful when it joins engineering, risk, quality, and delivery evidence instead of attempting to impersonate all of them with one heroic spreadsheet.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

IT Project Managersupporting

Sources