Release Planning

Contingency reserve covers the risks you priced; management reserve covers the ones you couldn’t name. How both get spent silently after the commitment — and how to read what’s left, in days.

Acceptance criteria vs definition of done: one sets the bar for every item in the release, the other sets the size of this one. Only one of them quietly moves a committed release date, and it files no change request on the way out.

A release management process defines gates, owners and handoffs — it answers what happens next, never when. Where the committed date actually moves, and how to give every gate you already run a live confidence band.

Integration hell isn’t a coding problem, it’s a scheduling one. Why individually-done work isn’t done together — and how to read the cost against a committed date.

Conway’s Law predicts where your dependencies will be before anyone writes a ticket. Why they still surface too late — and how to read the cost in days.

An assumption log records what was true on planning day. Here’s how expired assumptions quietly move a committed release date, measured in days.

The ninety-ninety rule says the last 10% takes another 90% of the schedule. Here’s why “almost done” hides erosion of a committed release date.

A hardening sprint is schedule buffer the confidence vote already priced. Here is what quietly spends it before the last iteration starts, and how to read what is left in days.

Escalation of commitment is why a feature nobody believes in still ships in the release. What makes agile teams especially vulnerable, and the four mechanics that make cutting scope a normal decision instead of an admission of failure.

A velocity forecast gives you one date. Three-point estimation gives you a range and the width of your own uncertainty — which is the number stakeholders actually need before they commit to a release.