Which Metrics Should a PMO Track on Hybrid Agile-PRINCE2 Projects?

## The short answer

On a hybrid project, a PMO should track three layers of metrics: **value and outcome metrics** (is this delivering the benefits in the business case?), **flow metrics** (is delivery healthy and predictable?), and **governance health metrics** (are decisions being made on time with real evidence?). Avoid vanity activity metrics like story-point velocity reported upwards, percent-complete against fixed plans, or documents produced — they measure motion, not progress. Measure value delivered, predictability and decision quality.

## Why hybrid metrics need rethinking

Pure PRINCE2 reporting leans on percent-complete-against-plan, which is meaningless when scope is deliberately flexible. Pure Agile reporting leans on velocity, which is a team's internal planning tool and becomes harmful the moment it's used as an upward performance metric. A hybrid PMO needs a measurement set that respects both the governance need for accountability and the delivery need for adaptation. The principle: **measure outcomes and flow, not activity and conformance.**

## Layer one: value and outcome metrics

These answer the board's real question — is the investment paying off?

- **Benefits realised to date** against the business case's expected range.

- **Value delivered per stage** — has shipped, working product actually moved the target outcome?

- **Business case health** — is the project still justified given what's been learned?

- **Cost of delay avoided** — value captured early by shipping increments rather than waiting for a big-bang go-live.

These are the metrics that belong in board packs. They connect delivery to the reason the project exists.

## Layer two: flow and delivery health

These tell you whether delivery is predictable enough to forecast — far more useful than raw speed.

- **Throughput** — items completed per period, used for forecasting, not for comparing teams.

- **Cycle time** — how long work takes from start to done; shorter and more stable is healthier.

- **Predictability** — how reliably the team hits its forecasts, which is what governance actually needs.

- **Work in progress** — high WIP signals overload and predicts slowdowns.

- **Defect or rework rate** — a quality signal that velocity hides.

Note what's absent: velocity as an upward metric. Velocity is a planning aid for the team. Reported to management, it gets gamed (inflate the points) and tells the board nothing about value.

## Layer three: governance health

Unique to hybrids, these check that the governance wrapper is actually working rather than rubber-stamping.

- **Decision latency** — how long key decisions take once raised; slow decisions starve fast delivery.

- **Stage boundaries held on time** — gates slipping signals governance drift.

- **Exception response time** — how quickly the board reacts when tolerances are breached.

- **Evidence at gates** — were continuation decisions backed by demonstrable product, or by slides?

- **Stop rate** — a portfolio that never stops anything isn't governing; it's approving.

That last one matters. A healthy portfolio occasionally stops projects at a boundary. A zero stop rate usually means the gates are theatre.

## Metrics to stop tracking

Actively retire these — they create false comfort or perverse incentives:

- **Percent-complete against a fixed plan** on flexible-scope work.

- **Velocity reported as a performance KPI.**

- **Documents produced** as a measure of progress.

- **Utilisation as a primary metric** — 100% utilisation destroys flow and predictability.

- **Number of features shipped** without reference to whether they moved an outcome.

Each of these rewards the wrong behaviour: looking busy, padding estimates, or shipping volume over value.

## Building the PMO dashboard

A practical hybrid dashboard separates audiences:

1. **Board view**: value realised, business case health, stage decisions due, stop/continue recommendations.

2. **Programme view**: throughput and predictability trends, cross-team dependencies, risk movement.

3. **Team view**: cycle time, WIP, defect rate, retrospective actions — owned by the team, not policed from above.

Keep team metrics with the team. The fastest way to corrupt good flow metrics is to turn them into upward judgement; teams will optimise the number instead of the outcome.

At neart.ai we build enterprise-grade PMO tooling, and the dashboards that change behaviour for the better are the ones that lead with value and predictability and quietly retire the vanity counters. What you measure upward is what your teams will optimise — so measure what you actually want.

## Takeaway

Measure in three layers: value and outcomes for the board, flow and predictability for delivery, and governance health at the boundaries. Retire percent-complete, upward velocity and document counts. The test for any metric is simple — does it reward delivering value, or just looking busy?