8 Project Measurement, Control, and Closeout

Establish meaningful measures

A project plan is useful when the team compares actual results with it and responds to meaningful differences. Monitoring collects performance information; Control uses that information to decide whether corrective action, an approved change, or a revised forecast is needed. Project controls commonly connect scope, schedule, cost, risk, and change.

Before work begins, agree on success criteria and establish approved scope, schedule, and cost baselines. For each measure, define what it means, how it is calculated, who provides the data, how often it is updated, and what threshold requires attention. Choose measures that support decisions rather than merely being easy to collect.

Choose and interpret performance measures

Use measures that show progress and support decisions across the project:

• Deliverables and scope: Compare accepted deliverables with planned deliverables, and track requirements that have passed or remain unresolved.

• Schedule: Track milestone dates, completed work, the forecast finish date, and schedule variance.

• Cost and resources: Compare actual spending with the budget, forecast the cost to complete, and track availability of critical resources.

• Quality: Compare defects, rework, test results, or acceptance rates with agreed criteria.

• Risks and issues: Track exposure, response progress, owners, and due dates.

• Benefits: Use indicators to show whether intended outcomes are emerging. Some benefits can only be assessed after delivery.

Report the evidence precisely. If $\frac{8}{10}$ planned deliverables have been accepted by the reporting date, report $80\%$ accepted rather than saying only that the work is “mostly complete.” State assumptions: if the remaining two deliverables are on the critical path, the percentage alone may hide a serious schedule threat.

Interpret earned value and variance

For projects using Earned value management, compare planned value, earned value, and actual cost:

• Planned value (PV): The budgeted value of work scheduled.

• Earned value (EV): The budgeted value of work actually completed.

• Actual cost (AC): What the completed work actually cost.

Schedule variance and cost variance are calculated as follows:

For example, if $PV = \$100{,}000$, $EV = \$80{,}000$, and $AC = \$90{,}000$, then:

These results indicate that less work has been completed than planned and that the work completed cost more than its budgeted value. The figures are signals to investigate, not explanations by themselves. Measure against a controlled, credible schedule, and analyze trends as well as individual variances.

Manage risks, issues, and changes

A Risk is an uncertain event that could affect objectives; an Issue is a problem that has already occurred. Keep both visible in a log that identifies an owner, impact, response, and review date. Reassess priority as conditions change, and escalate risks or issues when their impact exceeds the team’s authority or agreed tolerance.

When a proposed change arises, record what is requested and assess its effects on scope, schedule, cost, quality, resources, risks, contracts, and expected benefits. The authorized decision-maker approves, rejects, or defers the change. Update relevant plans and baselines only after approval, then communicate the decision to affected people.

Do not quietly alter a baseline to make performance appear better. Retaining a traceable record preserves a fair comparison between the original plan and approved changes.

Communicate status for decisions

A useful status report is timely, consistent, and candid. It typically includes:

1. Overall status and the reporting period.

2. Progress against objectives and the baseline, supported by evidence.

3. Forecast completion, significant variances, and trends.

4. Key risks, issues, changes, and response owners.

5. Decisions or support needed, who should provide them, and when.

Use a simple status indicator only when its thresholds are defined, and pair a color or rating with a short explanation. For example: “Schedule: red; a supplier delay threatens the acceptance test; recovery options need sponsor decision by Friday.” Report forecasts as forecasts, distinguish facts from estimates, and tailor the level of detail to the audience.

Complete delivery and handoff

Close the project in a controlled way whether it finishes as planned or is stopped early. Confirm which outputs have been delivered and accepted, and document unmet requirements and their disposition. Transfer ongoing risks, issues, actions, support duties, and benefit tracking to named owners who accept them.

Provide the receiving team with usable documentation, operating instructions, training, access, and support arrangements as appropriate. Reconcile contracts and finances, archive records, release temporary resources, and inform stakeholders of closure.

A handoff is not complete just because files have been sent. Confirm that the recipient can operate or maintain the deliverable and knows where to get help. If benefits will be realized after project closure, assign responsibility and agree how and when they will be reviewed.

Capture lessons for future work

Capture Lessons learned throughout the work, especially after significant changes, resolved issues, risk responses, and milestones. At closure, compare results with the original objectives and plan: identify what worked, what did not, why, and what should be repeated or changed next time.

Record actionable findings with enough context to make them useful. Share them with the relevant organization and store them where future teams can find them.