Project Plan
A project plan that stays useful after week one — scope boundary, milestones with exit criteria, dependencies with owners, and a decision log.
No sign-up. No email. Markdown — edit it in anything.
When to use it
Once the BRD is baselined and a sponsor has committed budget.
Who fills it in
Project manager.
Works alongside: BRD · Release Checklist
The template
Instruction lines are marked with > — delete them
once the document is filled in.
Project: _______________ Version: 0.1 Date: _______________ Project manager: _______________ Sponsor: _______________
Delete instruction lines (marked
>) before circulating.
1. Summary#
What we are doing:
Why:
Done when:
One sentence. If you cannot write it, the project is not ready to start.
2. Scope boundary#
In scope:
Explicitly out of scope:
The cheapest scope control available. Be specific enough to settle an argument.
3. Milestones#
A milestone without exit criteria is a date, not a milestone.
| # | Milestone | Exit criteria (how we know it is done) | Target date | Owner |
|---|---|---|---|---|
| M1 | ||||
| M2 | ||||
| M3 |
4. Workstreams#
| Workstream | Lead | Deliverables | Depends on |
|---|---|---|---|
5. Team and allocation#
| Name / role | Workstream | Allocation % | From | To |
|---|---|---|---|---|
Allocation of 100% across three projects is a plan to miss all three.
6. Dependencies#
| # | We need | From whom | By when | Confirmed? | If late |
|---|---|---|---|---|---|
| D1 | Yes/No |
"Confirmed" means the other party agreed, in writing, to that date.
7. Risks#
| # | Risk | Likelihood | Impact | Mitigation | Owner | Review date |
|---|---|---|---|---|---|---|
| R1 | H/M/L | H/M/L |
8. Assumptions#
| # | Assumption | Impact if false | Validate by |
|---|---|---|---|
| A1 |
9. Budget#
| Category | Estimate | Committed | Notes |
|---|---|---|---|
| People | |||
| Licences | |||
| Infrastructure | |||
| Contingency |
10. Governance#
| Status reporting | Frequency, format, audience |
| Steering meeting | Frequency, attendees, decision authority |
| Escalation path | Who, in what order |
| Change control | Who approves a scope change |
11. Communication plan#
| Audience | What they need | How often | Channel | Owner |
|---|---|---|---|---|
12. Decision log#
The single most useful section six months later.
| # | Date | Decision | Made by | Why | Alternatives rejected |
|---|---|---|---|---|---|
| 1 |
13. Change log#
| # | Date | Change requested | Impact (scope / cost / date) | Decision | Approved by |
|---|---|---|---|---|---|
| 1 |