Free Agile Project Management Template
A nine-week agile project: a short sprint 0 to write the vision, build the first backlog and agree the definition of done, three two-week sprints with planning, delivery and a review and retrospective, then a release sprint to harden, ship and refine the backlog for what comes next.
No credit card. Import the spreadsheet as a new project on the Free plan.
The spreadsheet is a 17-task plan with phases, durations and milestones, ready for Excel or Google Sheets. It carries no dates, so set your own start, or paste it into the Gantt chart generator to have the schedule built for you. Want to compare the plans side by side first? Every one of them is on the project plan template page, with the rows shown before you download.
What’s inside
All 17 tasks are below, from the product vision to the release review, each with its description, duration and priority. The three sprints repeat on purpose: planning, delivery, review and retrospective, every two weeks.
17
Scheduled tasks
5
Phases
5
Milestones
~9
Weeks end to end
Agile still has a plan, just a shorter one
Agile teams plan constantly; they just commit to less at a time. This template shows that shape: the dates are fixed in two-week boxes, the scope inside each box is decided at its planning meeting, and every sprint ends with something shown to the people who asked for it. The backlog items are not listed here because they are yours, so each sprint carries one delivery task to rename or split into your stories.
Sprint 0 is short and earns its place. A vision the team can repeat, a first backlog ranked by value, a definition of done everyone signs up to and a board set up before sprint 1 save the first real sprint from being spent arguing about how to work. The release sprint at the end is the same idea from the other side: hardening and release get their own time instead of being squeezed into the last afternoon.
In the spreadsheet each sprint is a phase, so the file reads as a sprint plan in Excel or Sheets. Onplana has real sprints with a board and a backlog on the Professional plan and up, which is the better home once the stories are written; the agile project management page shows how that works.
The plan, phase by phase
Sprint 0: Set Up4 tasks
Write the product vision and goals
Who it is for, the problem it solves and how you will know it worked, in a paragraph the team can repeat.
Build and rank the first backlog
The work written as user stories, ranked by value, with the top items small enough for one sprint.
Agree the definition of done
The checks every item passes before it counts as done: reviewed, tested, documented, deployable.
Set up the board and the working agreement
The board columns, sprint length, meeting times and how the team handles interruptions.
Sprint 13 tasks
Plan sprint 1
Pick the top backlog items the team can finish in two weeks and agree the sprint goal.
Build the sprint 1 backlog items
Rename or split this into the stories chosen at planning. Each one meets the definition of done.
Hold the sprint 1 review and retrospective
Show the working result to stakeholders, then agree one thing the team will do better next sprint.
Sprint 23 tasks
Plan sprint 2
Re-rank the backlog with what sprint 1 taught you, then commit to the next sprint goal.
Build the sprint 2 backlog items
Rename or split this into the stories chosen at planning. Each one meets the definition of done.
Hold the sprint 2 review and retrospective
Show the result, collect feedback into the backlog, and check last sprint's improvement happened.
Sprint 33 tasks
Plan sprint 3
Use the team's velocity from two sprints to commit to a goal it can actually finish.
Build the sprint 3 backlog items
Rename or split this into the stories chosen at planning. Each one meets the definition of done.
Hold the sprint 3 review and retrospective
Show the result and decide with the product owner what must be in the release.
Release Sprint4 tasks
Plan the release sprint
Agree what ships, what waits, and the checks the release must pass.
Harden, test and fix
End-to-end testing, performance and security checks, and fixes, with no new features added.
Release to customers
Ship, announce and watch the first hours closely, with a way back ready.
Review the release and refine the backlog
What customers did with it, what the team learned, and a re-ranked backlog for the next cycle.
Milestones
Five milestones: the backlog ready at the end of sprint 0, the end of each of the three sprints, and the release. On a Gantt chart they are the heartbeat of the project, evenly spaced every two weeks.
Backlog ready
Day 9 of the plan
Sprint 1 done
Day 24 of the plan
Sprint 2 done
Day 38 of the plan
Sprint 3 done
Day 52 of the plan
Released
Day 62 of the plan
Frequently asked
What is in the download?
A CSV file with the 17 tasks, one sprint per phase, each with its duration in days, priority and notes, and the five milestones as zero-day rows. Excel opens it directly and Google Sheets imports it.
Why are there no user stories in it?
Because they are yours, and a template full of someone else's stories is a list to delete. Each sprint has one delivery task to rename or split into the stories chosen at its planning meeting. Sprint 0 is where the first backlog gets written.
Can I change the sprint length?
Yes. Two weeks is the most common length, and the template uses it. For one-week sprints halve the delivery tasks; for three-week sprints add a week to each. Keep the length the same from sprint to sprint, or velocity stops meaning anything.
Is this Scrum?
It follows the Scrum rhythm of planning, delivery, review and retrospective, and adds a sprint 0 and a release sprint, which many teams use and Scrum itself does not require. If your team runs Kanban, keep sprint 0 and the release work and drop the sprint boundaries.
Start with the plan already built
Import the Agile Project spreadsheet into a free Onplana project and your phases, tasks, and milestones are scheduled from the start date you pick. No credit card, no time limit.