PgMP Case Study

PgMP Case Study: The Earned Value Report Nobody Wanted to Present

PMLearning Subject Matter Expert (SME)

July 02, 2026 · 3 min read

PgMP Case Study: The Earned Value Report Nobody Wanted to Present

1 The Case

A program director was preparing the quarterly summary for the steering committee. The earned value data across the program's four components told a clean story — almost. Projects B, C, and D were textbook-perfect: earned value matching planned value matching actual cost, exactly on schedule and on budget. Project A was the outlier: planned value of 100, but earned value of only 90 against an actual cost of 110. Behind schedule (SV of −10) and over budget (CV of −20) — the only red cell in an otherwise green wall.

The Challenge: What Would You Do?

Every experienced program leader knows the temptation in this moment, because the aggregate math offers an escape hatch: rolled together, the program's totals looked nearly on track, and Project A's variance could be blended into a portfolio-level average that no one on the committee would question. The component's project manager, worried about exposure, lobbied for exactly that — 'report at program level, we'll recover quietly.' Presenting the blended number wouldn't even have been false, strictly speaking. It would just have been engineered to prevent the steering committee from seeing the one thing they most needed to see. That's the line between summarizing and spinning — and it's an ethical line, not a technical one.

✓ The Solution

The program director reported it straight. The summary narrative named the outlier explicitly: Project A is behind schedule and over budget; components B, C, and D are on track. But honest reporting isn't the same as alarmed reporting — the variance came paired with analysis and a recovery plan: root cause of A's slippage, corrective actions underway, revised forecast, and the specific decision the committee was being asked to make about additional support. The committee spent the meeting on the one project that needed governance attention instead of admiring three projects that didn't. Project A got resources approved that a blended report would never have justified — and the director's reporting earned a credibility that outlasted the program.

Exam Application & Takeaway

▸Program-level reporting exists to direct governance attention, not to deflect it. The professional standard: find the outlier, name it plainly, and pair every red flag with analysis and a proposed path — transparency plus a recovery plan, never transparency alone or spin alone. On the PgMP exam, EVM table questions reward the same instinct: scan for the outlier first (any component where EV diverges from PV or AC), characterize it precisely — behind schedule if EV < PV, over budget if EV < AC — and build your narrative around the recovery of that component while noting the stable ones.

The picture the committee actually saw

S-curve chart of Project A earned value analysis: at the month-6 status date, Actual Cost is 110, Planned Value is 100, and Earned Value is 90 — showing the project behind schedule (SV −10) and over budget (CV −20) — Project A at the status date: the earned value curve (green) trails the plan (blue) while actual cost (red) runs above both — the classic signature of a project that is both late and over budget.

This is why the S-curve is such an honest chart: the three lines tell the story before anyone says a word. Up to the status date, Project A's actual cost climbed faster than the value it earned, while that earned value fell short of the plan. The vertical gaps at the dashed line are the variances — schedule variance of −10 between the green and blue curves, cost variance of −20 between the green and red. And the fact that the curves had been quietly separating for weeks before the review is the strongest argument for reporting it early: variance trends widen; they rarely heal on their own.