Board verdict
—
Contention
0/100
1 / 6
Over capacity
More work arrives at these steps than they can clear, so the queue never settles — the backlog grows for as long as the load continues. This is a different statement from a high score, and it is usually the thing to fix first.
What this costs
Derived from the predicted waits, not assumed. Rework and coordination are hours engineers actually spend; blocked time is what a team loses waiting for an environment, net of what it redirects elsewhere.
capacity lost
0%
engineer-days / month
0
cost / month
$0
merged → live
0
A deploy queue costs this, not payroll — the team moves on, the change doesn't.
where it goes
Signals at caution or danger
Reading the board
What to do about it
Frees roughly 0 engineer-days a month (≈ $0) if the whole path lands.
Effort is judgment, not an estimate — no source behind these durations. Sequence and relative size are the useful part; treat the weeks as a scale to argue with.
What this is built on
The board leans on several bodies of work. They agree with each other more than they overlap — each supplies a piece the others assume. The sources justify the direction of every claim here; the numbers remain judgment.
Where the ideas compound
The part that isn't in any one book. Each pairing does something neither idea manages alone — and the second line is what goes wrong when you adopt only one.