ReleasePlan came out of the same conversation on every programme: "what will actually be in the release?" It turns backlog, capacity and a date into a plan that holds up under questioning.
Live screenshot of ReleasePlan — real-time, dependency-aware release coordination.
Import the scope for the release and the team doing it — no rebuilding a runbook spreadsheet from scratch every cycle.
Add velocity, leave and holidays so the timeline auto-calculates against the people you actually have that quarter.
Mark blockers, cross-team dependencies and Go/No-Go gates so the critical path is visible before the release weekend.
Send a live link. Stakeholders always see the current plan, and you compare what-if scenarios before committing to one.
Set a release date and see what fits, or set the scope and see when it lands. Both directions, same source of truth.
Model team velocity, leave and public holidays so the plan reflects the people you actually have, not a perfect team.
Mark blockers and cross-team dependencies so the items most likely to slip surface before the release, not during it.
A clean release view you can drop straight into a steering pack — no reformatting the same slide every fortnight.
Drop scope, add a developer, move the date — compare versions side by side before you commit to any of them.
Send a link instead of a spreadsheet. Everyone sees the current plan rather than the version they downloaded last month.
Free to use. If it's missing something your team needs, tell me and I'll look at building it.