KPIs a PMO actually needs.

Three categories. Eight metrics total. Anything more is dashboard theater. Built around what executives ask, not what tools can graph.

02
—
RELY

Reliability KPIs.

01 · Sprint commitment hit rateCOMMITTED ITEMS COMPLETED %
02 · Carryover ratioNOT-DONE / COMMITTED
03 · Forecast accuracyFORECAST P50 VS ACTUAL

These answer "can we trust the dates this org commits to?" Track at portfolio and at team level. Big variance between teams is the most actionable insight here.

03
—
FLOW

Flow health KPIs.

04 · Cycle time p75FLOW SPEED
05 · WIP per engineerFOCUS LEVEL
06 · Bug-fix work shareQUALITY DEBT TREND

04
—
RISK

Risk KPIs.

07 · Open blocker ageOLDEST · MEDIAN
08 · Scope churn rateADD/REMOVE / SPRINT

05
—
SKIP

What to leave off.

Story-points-per-sprint. Velocity is internally useful, externally noisy. Don't roll it up to portfolio.

Lines of code. Don't.

Code coverage. Useful for engineering hygiene; meaningless to a PMO. Different audience.

"Health" rollups with green/yellow/red bubbles. The rollup loses the signal that mattered. Show the actual numbers.