A capacity planning template records who is on the release, how much of them, and when they are away, once, at the confidence vote. What to write in each field so it stays true, and how to keep capacity live against a committed release date in Jira.
A release planning template records the date, scope, dependencies and team once, in the week of the confidence vote. Which fields go stale first, what to write in each so it stays honest, and how to keep them live against a committed release date in Jira.
A cutover plan is hour-precise about deployment and silent about the date it inherits from a confidence vote months earlier. How to anchor the change window to a live 85% release date in Jira.
WSJF decides what deserves attention next — real economic judgment, honestly applied. What it never says is what the re-rank costs the release date you already committed to.
Schedule float is slack your dependency network created by accident, not a reserve anyone set aside. Why it drains before a committed release date ever moves.
A ROAM board captures real engineering judgment at PI planning, then goes stale. How Owned, Accepted and Mitigated risks quietly move a committed release date.
When one senior developer or the Scrum Master assigns the points, the number survives but the information does not. Who should estimate story points, and why the disagreement is the valuable part.
Fixed release cadence or ship-when-ready? The choice looks like a scheduling preference. It is really a decision about which variable absorbs the miss — the date, or the scope.
Sprint length was a settled argument for a decade. AI-assisted delivery has reopened it. What sprint length is actually for, what shortening really costs, and the test that beats the debate.
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.
© 2026 — Divim, Inc. Digital Visual Management Systems and Consulting, Inc.