Agile guide · Agile practices
The Role of the Project Plan in Agile Development
A common myth says Agile projects have no plan. In reality, Agile replaces one large, fixed plan with several smaller plans at different levels of detail, each updated as the team learns.
Key takeaways
- Agile plans in layers, from vision to the daily plan.
- An Agile project plan still covers goals, team, cadence, risks and budget.
- Plans are updated every iteration with real progress.
The five levels of Agile planning
Agile practitioners often describe planning as layers, sometimes drawn as an onion:
| Level | Horizon | Typical artifact |
|---|---|---|
| Vision | Years | Product vision statement |
| Roadmap | Quarters | Agile roadmap |
| Release | Months | Release plan |
| Iteration | Weeks | Sprint Backlog and Sprint Goal |
| Daily | Today | Plan agreed at the Daily Scrum |
What an Agile project plan contains
- The goal, scope boundaries and success measures.
- Key stakeholders and how they will be involved.
- Team structure, roles and working agreements.
- Cadence: iteration length and meeting schedule.
- Initial backlog and release forecast.
- Key milestones, dependencies and risks.
- Budget and how it is tracked, often as a cost per iteration.
- How progress will be reported.
Satisfying governance
Organisations often need plans for funding and oversight. Agile teams can meet these needs by:
- Funding a stable team for a period rather than a fixed scope.
- Reporting progress through working increments and burnup charts.
- Holding milestone or phase reviews aligned with releases.
- Keeping a short, living risk and decision log.
Keeping the plan alive
Update the plan at the end of every iteration. Changes are expected; what matters is that every change is visible and that stakeholders understand the trade-offs.
Free templates for this topic
Frequently asked questions
Does a project plan in Agile need a project manager?
Some Agile teams do, especially in hybrid or scaled settings. See the Agile project manager.
Can a project plan in Agile include Gantt charts?
Sometimes, at milestone level for stakeholders. Day-to-day planning uses backlogs and boards.
Do teams still need a project plan in Agile?
Yes, but it is layered and lightweight: a vision, a roadmap, release plans, iteration plans and daily plans, each refined as the team learns.
What are the five levels of the project plan in Agile?
Vision, roadmap, release, iteration and daily. Detail increases as the horizon gets shorter.
What should an Agile project plan include?
The goal, scope boundaries, success measures, stakeholders, team and roles, cadence, initial backlog and release forecast, key milestones, risks, budget and reporting approach.
How does a project plan in Agile handle a fixed budget?
Often by funding a stable team for a period and calculating cost per iteration. Scope is then prioritised to fit the budget.
What is the planning onion for a project plan in Agile?
A diagram showing Agile planning as layers from vision on the outside to daily planning in the centre.
How does a project plan in Agile support reporting to governance boards?
Through working increments, burnup charts, a short risk and decision log and milestone reviews aligned with releases.
How often is a project plan in Agile updated?
At least at the end of every iteration, with the release plan and roadmap reviewed on a slower cadence.
Is a backlog the same as a project plan in Agile?
It is part of one. The backlog holds the ordered work, but a full plan also covers goals, stakeholders, cadence, budget and risks.
Can you use a work breakdown structure in a project plan in Agile?
Some teams use a high-level breakdown of features or epics, but detailed task breakdowns are left to each iteration.