Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 17 tasks across 5 phases, about 13 weeks from start to finish with the parallel work shown.
What's in the template
| Phase | Task | Duration | Starts | Depends on |
|---|---|---|---|---|
| Discovery | Stakeholder interviews and goals | 5 days | Day 1 | Nothing (starts first) |
| Discovery | Requirements and user stories | 8 days | Day 6 | Stakeholder interviews and goals |
| Discovery | UX research and wireframes | 10 days | Day 6 | Stakeholder interviews and goals |
| Design | Architecture and tech stack decision | 6 days | Day 14 | Requirements and user stories |
| Design | UI design and design system | 10 days | Day 16 | UX research and wireframes |
| Design | Dev environment and CI pipeline | 4 days | Day 20 | Architecture and tech stack decision |
| Build | Increment 1: core data model and APIs | 15 days | Day 24 | Dev environment and CI pipeline |
| Build | Increment 2: main user flows | 15 days | Day 39 | Increment 1: core data model and APIs, UI design and design system |
| Build | Increment 3: integrations and admin | 12 days | Day 54 | Increment 2: main user flows |
| Test | Test plan and test data | 5 days | Day 14 | Requirements and user stories |
| Test | QA on increment 1 | 8 days | Day 39 | Increment 1: core data model and APIs, Test plan and test data |
| Test | QA on increment 2 | 8 days | Day 54 | Increment 2: main user flows, QA on increment 1 |
| Test | Security review and fixes | 7 days | Day 66 | Increment 3: integrations and admin |
| Test | User acceptance testing | 6 days | Day 73 | QA on increment 2, Security review and fixes |
| Release | Documentation and release notes | 4 days | Day 66 | Increment 3: integrations and admin |
| Release | Production deployment | 1 day | Day 79 | User acceptance testing, Documentation and release notes |
| Release | Hypercare and bug fixes | 10 days | Day 80 | Production deployment |
Durations are examples to replace with your own estimates, not benchmarks. Some work runs in parallel, so the plan takes 89 days instead of the 134 it would take one task at a time. The 11 darker bars are the critical path: a day lost on any of them moves the finish date.
About this software development project
Most software plans fail in the hand-offs, not in the coding. Requirements arrive after the architecture is fixed, QA gets a build the week before launch, and nobody booked the security review. This template lays out the whole life cycle so each hand-off is a visible link between two bars.
It is sized for a small product team (two to six engineers, a designer and a product owner) shipping a new web application or a major feature over roughly four months. Build work is split into three increments so testing can start on the first one while the second is still being written, which is where most of the schedule is won back.
If your team works in strict two-week sprints, keep the increments and treat each as a pair of sprints. If you are running a fixed-scope contract, the same structure works; add a change-control task between increments so scope changes have a place to land.
Who it's for: Engineering managers, product owners and agency leads who need one schedule that developers, QA and the business can all read.
How to use it
- Use this template. Click Use this template. The plan opens in the editor with discovery, design, build, test and release as lanes and every dependency already drawn, so you can see the critical path before you change anything.
- Re-estimate the build increments. Ask the engineers to size each increment. Change the bar length and everything that waits for it moves; the finish date tells you immediately whether the estimate fits the deadline.
- Pull testing forward. QA on increment 1 already starts while increment 2 is being built. If your team can test continuously, shorten the QA bars rather than deleting them, so testing effort stays visible.
- Share it with the business. Send a read-only link to stakeholders. They see dates and dependencies without needing an account. A link shows the plan as it was when you made it, so create a fresh one after big changes.
Why the plan is split into increments
A single twelve-week "Development" bar hides every risk until the end. Three increments give you three points where working software is tested and shown, and they let QA overlap with development instead of queueing behind it. In this template the critical path runs through the build increments and user acceptance testing, so those are the tasks to protect.
Design and UX research run beside the architecture work rather than after it. The link that matters is that increment 2 (the main user flows) waits for both increment 1 and the finished UI design. If design slips, you will see increment 2 move on the chart before anyone writes code against an unfinished screen.
Where software schedules usually slip
Environments, access and third-party integrations. The CI pipeline task is short but sits on the critical path, because nothing can be built and tested reliably without it. Integrations sit in the last increment on purpose: they depend on other teams' timelines, so give them float or start the conversations during discovery.
The security review is a separate bar because it is usually done by someone outside the team with their own calendar. Book it when you build the plan, not when increment 3 finishes.
Planning tips
- Keep hypercare in the plan. Launch is not the finish line for the team, and leaving it off makes the next project look like it can start the day after release.
- Add the people who own each task in the owner field so the weekly status report shows who is waiting on whom.
- Save a baseline after the estimates are agreed, then compare against it every sprint review.
- Put external dependencies (vendor APIs, app store review, legal sign-off) in as their own tasks with their own durations.
Frequently asked questions
- What phases should a software development Gantt chart include?
- Discovery, design, build, test and release are the usual phases of the software development life cycle (SDLC). This template also includes a security review and a hypercare period after launch, because both take real time and are often left out.
- Can I use a Gantt chart with agile development?
- Yes. Use the Gantt chart for the release-level plan (increments, test windows, launch date) and keep day-to-day work in your sprint board. The sprint planning template covers a single two-week sprint in more detail.
- Does the template show the critical path?
- Yes. The tasks are linked finish-to-start, and the darker bars on this page are the critical path. In the editor, the critical path updates as you change durations or links.
- Can I download the plan?
- The Download CSV button on this page gives you the template as a spreadsheet with start dates, end dates and dependencies. Downloads from the editor after you change the plan are on the Solo plan ($12/month).
Related templates and guides
- Software Sprint Plan Gantt chart template
- Agile Release Plan Gantt chart template
- Mobile App Development Plan Gantt chart template
- IT Project Plan Gantt chart template
- Sprint planning on a Gantt chart
- TeamGantt alternative
- Free Gantt chart maker, no sign-up
- Critical path calculator
- Free timeline templates
- All Gantt chart templates
- Gantt chart examples
- How to make a Gantt chart
- Excel Gantt chart template
The free plan saves one project. Downloads from the editor (PDF, CSV) and more projects are on Solo, $12/month.