part nine · the portfolio
The Portfolio
The view across features and products. DORA metrics. Technical debt as chain gaps. VRI. When to stop.
Quarterly portfolio review. Monthly DORA reading. Continuous VRI. Killing initiatives is a portfolio function — not a team conversation.
The portfolio is the view above any single cycle. It is where the leadership reads what the chain is producing across all the work, and decides what to keep funding, what to continue, and what to stop. The discipline of the portfolio is the discipline of writing down what the team is willing to walk away from.
DORA — the four system signals
Lead time, change failure rate, deploy frequency, MTTR. Tracked at portfolio level, not story level. They tell you whether the chain itself is healthy — independent of any individual feature.
| Metric | Read it as |
|---|---|
| Lead time (commit → production) | How thick the chain is. Long lead time means a bottleneck somewhere. |
| Change failure rate | How often the chain ships something that has to be rolled back. |
| Deploy frequency | How often the chain is willing to commit. Low frequency hides problems. |
| MTTR | How quickly the chain recovers when it breaks. |
A team can have great delivery on one feature and still have a chain that is dying. The DORA signals catch that.
DORA is not a team scorecard. It is a chain diagnostic. Read across cycles, not within a sprint.
Technical debt as chain gaps
The corpus has a specific definition of technical debt: the gap between what the chain produced and what the chain should have produced, that has been left in the system because the cycle had to keep moving.
Debt is not all code. It is:
- A migration that runs but is not reversible.
- A runbook that names a step but doesn't say how.
- A brief that has predictions but no check date.
- A test suite that runs but doesn't cover any of the Gherkin scenarios.
- A flag that was meant to be cleaned up after the cycle and is still wrapping behavior six months later.
Debt accumulates by chain level. Discovery debt — briefs without witnessed assumptions — is real and expensive. Operational debt — runbooks that don't work — is the kind that wakes people up at 3am.
The portfolio review reads the debt distribution. Concentration in any one level is a signal that the chain has been letting that phase quietly skip itself.
VRI — Value-to-Rework Index
The financial translation. Value declared per cycle divided by rework produced per cycle. A portfolio-level health metric.
VRI = Σ value(initiatives shipped) / Σ rework(rework cycles needed)A VRI that is improving means the chain is producing more of what was paid for. A VRI that is declining means initiatives are shipping but reality keeps disagreeing. A VRI hidden — because rework is reframed as "next phase" — is the most expensive, because the chain doesn't see itself.
Rework is named explicitly:
- Rework caused by Strategy — the initiative was the wrong bet. Counted.
- Rework caused by Discovery — the brief didn't witness. Counted.
- Rework caused by Scope — the story missed a state. Counted.
- Rework caused by Execution — the bug was a code defect. Counted.
- Rework caused by Operation — the runbook didn't exist. Counted.
Reframing rework as iteration hides the signal. Iteration is what we said we'd do. Rework is what we said we wouldn't have to do.
When to stop
This is the portfolio's hardest job.
An initiative is killed when:
- The prediction was wrong and the new prediction is not better than the next one in the queue.
- The signal reading shows no movement after two cycles of intervention.
- The VRI of this initiative, alone, is below the portfolio threshold.
- Strategy has moved and the initiative is now serving a goal the organisation no longer holds.
Killing is not failure. Killing is the chain's most disciplined act. The team that kills initiatives at the right time has already saved more than they would have spent finishing.
The corpus pattern: a kill produces an artifact, like everything else. The kill brief — short, factual, with the data — joins the corpus. The next initiative inherits it. We have learned not to do this in this way for these reasons.
The portfolio review
Quarterly. Three artifacts on the table:
- DORA signals across all initiatives, with the trend.
- VRI across all initiatives, with the trend, and the rework breakdown by chain level.
- The kill list — initiatives the trio is recommending stop, with evidence.
Decisions made at the portfolio review are written down — kept, continued, killed — with rationale. They become the input to the next cycle's strategy.
A portfolio review that produces only keep decisions is not a portfolio review. It is a status meeting. The discipline is the willingness to say stop.
Enough to know what is alive.
DORA signals are tracked and read. VRI is current. Rework is broken down by chain level. The portfolio review has happened in the last 90 days and produced at least one decision — including, where warranted, a kill.