A manifesto for zero-sum sprint capacity
If everything is a priority, nothing is.
Your team's capacity is fixed. Your backlog is not. Prioritisation is the discipline of saying what will not be done — and making the people who ask for more carry the cost of asking.
- 01Capacity is finite. Treat it as such.
- 02Every yes is a no to something else.
- 03Opportunity cost must have an owner.
- 04Plans are commitments, not wishlists.
I · The problem
The illusion of elastic capacity.
Infinite lists
Modern tools let anyone add anything, anywhere. The backlog grows; the sprint does not. Nothing forces a choice.
Elastic sprints
Urgent work is squeezed in on top. Velocity charts look fine until delivery quietly collapses three weeks later.
Fragmented attention
Teams context-switch between half-started commitments. Everyone is busy. Little is finished.
II · The mechanism
One in, one out.
A sprint is a fixed container. A new request may enter only if work of equivalent effort leaves. Try it: the board below will not let you exceed capacity.
Incoming request
Capacity 21/21 ptsBoard-requested pricing report
5 pts · needs 5 pts freed
Sprint is full. Choose a task of equal or greater effort to remove →
Current sprint
III · The Sacrifice Log
Every urgency has a signatory.
When a stakeholder pushes work over the plan, they don't just add it — they sign for what it displaces. The log is a permanent, visible ledger of trade-offs, so opportunity cost is owned rather than absorbed by the team.
| Date | Admitted | Sacrificed | Owner |
|---|---|---|---|
| 14 Oct | Regulator data request | Courier API migration | J. Whitfield, COO |
| 21 Oct | Black Friday stock alerts | Supplier scorecards | A. Okafor, Commercial |
| 04 Nov | Board pricing report | Returns automation | R. Patel, CFO |
Illustrative entries.
IV · Early access
Join the early access cohort.
A small group of operations teams, admitted in order. No newsletters, no noise.