What’s in the template
| Part | Weeks | Content |
|---|---|---|
| Sprint 0 | 1–2 | Backlog, team, definition of done |
| Release 1 | 2–8 | Epics: sign-up and onboarding, core workflow; milestone Release 1 |
| Release 2 | 8–16 | Epics: reporting, integrations; hardening sprint; milestone Release 2 |
| Ceremonies | 2–16 | Sprint reviews and retrospectives every two weeks |
| Backlog sheet | — | User stories with epic, priority (Must, Should, Could), points, sprint and status |
Rename the epics after your own product areas. The plan works for software, but also for marketing, product or internal teams that work in sprints.
What an agile project plan is (and isn’t)
An agile project plan does not fix every task up front. It fixes the cadence (two-week sprints), the releases you are aiming for, and the epics you expect to fit in each. Stories are planned one or two sprints ahead, from the backlog. After each sprint review, you move epics on the release plan according to what the team actually delivered: that is the whole point.
How to use it
- Write the backlog: one user story per line, grouped by epic, with a priority.
- Estimate in points and use the team’s velocity to see how many sprints each epic needs.
- Lay out the epics on the release plan and set the release milestones.
- Run each sprint on the Kanban board: the same tasks, card by card.
- Re-plan after each review: move epics, not stories, so the plan stays readable for stakeholders.
Which template for which need?
| Need | Template |
|---|---|
| Several releases over a few months | This agile project plan |
| One sprint, day by day | Sprint planning template |
| A software project with testing, UAT and go-live | IT project plan template |
| A one-page overview for executives | High-level project plan template |
Wondering whether Gantt charts and agile mix? Read agile Gantt charts and Kanban vs Scrum.
Questions
What is an agile project plan?
A plan built around sprints and releases: epics laid out across sprints on a timeline, with user stories planned from a prioritised backlog.
What should an agile project plan include?
The sprint cadence, the releases and their target dates, the epics planned for each release, and a backlog of user stories with priorities and estimates.
Can you use a Gantt chart in agile?
Yes, at the release level: epics as bars, releases as milestones. The sprint itself runs on a Kanban or Scrum board.
Is the agile project plan template free?
Yes, in Excel and online, for personal and commercial use.
How long should a sprint be?
Two weeks is the most common. The template uses two-week sprints; change the durations if yours are one or three weeks.