Project plan template
Published:
Last updated:
See “Better Project Planning in 90 Minutes” for an introduction to this format.
Problem Statement
In a few to several paragraphs, describe the problem to be solved. Some questions to consider:
- What is the problem or need to be solved?
- Who experiences it, how frequently, and what’s their current workaround?
- How does the competition solve it?
- What makes it important, urgent, or valuable to solve right now?
Please add a link to a PRD (Product Requirements Document) if one exists.
If no PRD what are the design implications for this project? Please involve Design in this plan as needed.
Solution Description
In a few to several paragraphs, provide a high-level overview of the solution to the problem. It should be “rough, bounded, and solved.”
Link to any designs if any exist.
Open Questions
Anything we’re still uncertain about.
Milestones
List any key, high-level project milestones. More than several is probably too much; go higher level or split up the project. Project milestones aren’t GitHub issues.
TBD
People
Who is responsible for what
No Gos
Explicitly identify any “no gos”, or aspects that will be deliberately ignored.
Things we aren’t going to do as a part of this project: