Performance Measurement Baseline: What Are You Really Measuring Against?
A project reports scope on track, the schedule showing a small slip, and spend a little under profile. Each of those is reasonable on its own, and together they can describe a project that is comfortably in trouble, because nothing in the set relates the money to the work it was supposed to buy.
The performance measurement baseline is the artefact that joins them, and Section 4 of the PMBOK® Guide Eighth Edition lists it among the things a project maintains. It is an integrated reference: the approved scope, spread across the approved schedule, with the approved cost attached, so that progress and spend can be compared in the same currency.
What it integrates
Scope, expressed as measurable pieces. The work broken down far enough that somebody can say a piece is finished without argument. Where the breakdown is too coarse, progress becomes an opinion, and an integrated baseline built on opinions integrates nothing.
Schedule, so that each piece has a time. This is what allows a comparison of what should have been done by now with what has been. Without the time dimension, a project can only compare totals, which is a comparison that only becomes interesting at the end.
Cost, attached to the same pieces. Each piece of work carries its budget, so spend can be traced to work and not merely to a period. This is the part most often missing in practice: costs are held by supplier or by category while work is held by activity, and the two cannot be reconciled without a mapping nobody has built.
How progress is claimed
Objective measures where they exist. Units installed, rooms handed over, tests passed, documents approved by a named party. A physical or countable measure removes the conversation about percentages entirely, and it is available on far more projects than people assume.
Conventions, applied consistently, where they do not. Claiming half the value when work starts and the rest at completion, or claiming only at milestones, are both workable rules provided everybody applies the same one throughout. The trap is the percentage estimated by the person doing the work, which drifts towards optimism steadily and stalls around ninety per cent for a long time.
A ward measured by spend
A hospital trust was refurbishing a twenty-eight bed ward in three phases, with the ward remaining partly operational. The monthly report to the capital group showed spend against budget and a narrative on progress.
At month four the report showed about fifty-five per cent of the budget spent, with a comment that work was proceeding to programme. The comment was sincere and the spend was accurate.
Walking the ward gave a different account. The first bay was genuinely complete, with beds made up, curtain track hung and lockers in place. The second was painted and bare: no fittings, services still open at the wall. The third was stripped back to blockwork with protection sheeting taped over the screed.
Roughly a third of the work was finished, against fifty-five per cent of the money. The difference was mostly front-loaded: strip-out, asbestos removal, mechanical first fix and the prefabricated bed head units, all of which had been paid for and none of which shows as a finished room.
That is a perfectly normal profile and it was invisible in the reporting, because nothing tied the money to the work. When the trust rebuilt the report against an integrated baseline, with each bay carrying its own value and progress claimed on handover of a completed bay, the position became readable at a glance and the forecast improved immediately: the remaining two-thirds of the work carried a different cost profile from the first third, and the group could see it.
The project finished within two per cent of budget. What changed was not the outcome; it was that everybody could see the position eight months before the outcome arrived.
Keeping it usable
Keep the pieces small enough to finish. Work packages that take four months to complete produce four months of unanswerable questions about how far along they are. Pieces that finish within a reporting period make progress a fact.
Change it only through change control, and keep the history. The baseline's value is entirely in being stable enough to measure against, and adjusting it to accommodate performance removes the measurement. Where a change is genuine, it goes through the process and the previous version stays on the record.
For a PMP® candidate, it helps to recognise that the baseline integrates scope, schedule and cost so that performance can be read in one place, so a scenario giving spend and a narrative is missing the comparison that matters. A response that accepts a percentage complete without asking how it was derived has accepted somebody's estimate of their own progress. Situations where each measure looks acceptable and the integrated picture does not are worked over at length in a structured PMP exam preparation course.
Ask one question about your own project this month: how was the progress figure in the last report calculated, and by whom? If the answer is that somebody estimated it, the number is a judgement, and the useful next step is agreeing an objective rule for claiming progress on the work that remains.
Interested in going further?
Three separate baselines can each look healthy while the project is not, and the integration is what makes that visible early. Omega's PMP® Exam Preparation works through measurement that joins money to delivered work.
The performance measurement baseline is one of the artefacts described in the PMBOK® Guide Eighth Edition.
Ad · Amazon affiliate link.
References
A167: Project Charter Explained: Purpose, Content and Common Misunderstandings
A168: Business Case vs Project Charter: What’s the Difference?
A169: Assumption Log vs Risk Register
A170: Decision Log: The Forgotten Project Control
A171: Change Log vs Issue Log
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
