Skip to content
Start free
Free template

Software release plan Gantt chart template

A release cycle for a small product team runs about six weeks in this template: scope frozen on day 9, two weeks of development, about ten days of QA and bug fixing, a release candidate on staging, then the release around day 36 and a week of monitoring and hotfixes. It’s written for the people outside engineering who need the date, and sits above your issue tracker rather than replacing it.

Use this templateStart free
Opens in the NeoGantt editor in your browser.
Task
W1
W2
W3
W4
W5
W6
  1. Scope & design
  2. Requirements & scoping
  3. Technical design
  4. Scope frozen
  5. Build
  6. Feature development
  7. Code reviews
  8. Documentation
  9. Stabilise & ship
  10. QA & regression testing
  11. Bug fixing
  12. Release candidate & staging
  13. Release 🚢
  14. Monitor & hotfixes
Software release: 9 tasks, 2 milestones, about 6 weeks milestone

This is the actual template. Durations count working days; weekends are skipped. Drag any bar to reshape it once it’s open.

When to use it

  • Stakeholders outside engineering want to know when a release will land and what has to happen first.
  • You’re an agency building software for a client and need a release plan the client can follow.
  • Marketing and support need the date early enough to write announcements and help docs.
  • The release spans several sprints and you want the phases laid out end to end.

What’s in it

The template is split into phases. Here’s what each one covers and why it’s there.
  1. 01

    Scope & design

    Requirements and scoping, then technical design, with Scope frozen at day 9. The freeze is what makes a release date believable. Anything that arrives after it goes in the next release, or the date moves and everyone knows why.

  2. 02

    Build

    Two weeks of feature development, with code reviews alongside and documentation starting halfway through, once interfaces stop changing. Code reviews get their own bar because on a small team they compete with development for the same people.

  3. 03

    Stabilise & ship

    QA and regression testing starts before development finishes, bug fixing runs through it, then a release candidate goes to staging. There’s no separate code freeze milestone; many teams add one at the release candidate so only fixes go in from there. Release lands around day 36, followed by a week of monitoring and hotfixes.

Adapting it to your project

Write the rollback plan before release day

Decide how you’d undo the release (redeploy the previous build, switch off a feature flag, reverse a database migration) while the release candidate is on staging. Add it as a task in Stabilise & ship. Nobody writes a good one with production down.

Mark change freezes and holidays

Add public holidays and company change freezes (end of year, end of quarter for finance systems) as non-working periods. A release sitting right before one, with nobody around for hotfixes, becomes obvious.

Save an iteration at scope freeze

Name it after the release. If the date moves, the next iteration’s summary lists which bars shifted and by how much, which shortens the retrospective.

Give stabilisation the time it usually takes

If bug fixing regularly runs past the release candidate on your team, lengthen the phase. Two releases in a row that overran by the same amount are telling you the estimate.
Use this template

Questions

What should a software release plan include?

The scope of the release, the technical approach, development, code review, documentation, testing, bug fixing, a release candidate on staging, a rollback plan, the release date and a period of monitoring afterwards. Many teams also mark a scope freeze and a code freeze as milestones.

How long is a typical software release cycle?

It depends on the team. Teams practising continuous delivery release daily or weekly, many product teams ship on two- to six-week cycles, and larger or regulated releases can take a quarter or more. This template runs about six weeks including scoping and post-release monitoring.

Does NeoGantt handle dependencies for release planning?

No. It doesn’t link tasks or calculate a critical path; you move bars yourself or shift the whole plan at once. That works for a release plan shown to stakeholders. If you schedule releases around hundreds of dependent tickets, a tool with dependencies, such as Microsoft Project, is a better fit.

Related

Product launch templateA free product launch timeline: research, positioning and pricing, launch assets, press and a beta, launch day about five weeks in and a post-launch review.Project plan templateA free project plan Gantt chart in four phases (initiation, planning, delivery, close). About seven weeks, with approval milestones and two workstreams.Website project templateA free website project Gantt chart: discovery, design, build and launch over about 10 weeks, with the client’s content, design review and UAT flagged as theirs.NeoGantt for project managersVersion history and iterationsNeoGantt vs Microsoft Project

Start your software release plan

Open it, drag the bars onto your real dates and rename anything that doesn’t fit. Sign up when you want to keep it.

Use this templateAll templates