---
# System prepended metadata

title: Project Plan Template
tags: [process]

---

# Project Plan Template

###### tags: `process`
[toc]

## Meme 
<!--
*Do something creative to represent the project.  Create a [meme](https://imgflip.com/memegenerator), create a fake song, a painting, anything.*
-->

## 💡 Idea
<!--
*The idea space is the bare minimum needed to communicate an idea and allow the submitter to present the idea during project planning.*
-->

### tl;dr
<!--
*~3 sentances on what this idea is.*
-->

### Goal

<!--
*1-2 lines on What problem are you solving and a proposed solution. Bullet points are fine*
Example: 
- Problem: It's hard to understand context on what to give attestations too.
- Solution: Make the experience of going through contributions for attestations fun.
- Goal Alignment: What company objective does this project align with?

Who is the customer?
What’s the problem you’re trying to solve?
What’s the solution (and you need to explain to the customer, not to yourself).
Would they reasonably adopt this solution, because you’re asking for a behaviour change?

--> 
- Problem: 
- Solution:

<!-- 
Before you assume you've solved things here are some questions to ask yourself:
- Have we evaluated all the simple solutions we might already fix with this idea?
- What's the minimum criteria to test the solution? (Could be as simple as talking to some DAO friends about experience.)
- Can we ask users with wireframes?
- Have we asked users direct questions about pain points to understand the problem?
-->

--- 

## Scope, Stakeholders, Type

<!--
*What type of work will this include?*
*Who should this project consult in it's lifecycle?*
Project type:
- Agile (v1 v2 etc.)
- Bundle
- Exploratory
- Internal
-->

*Provide all information needed for project kick off.*

##### Related Links
<!--
*add link to one pager (if one pager was done)*
--> 

- [govrn.app](https://govrn.app/)

---

### 🧭 Discovery for product (Omit this if it doesn't fit)

<!--
*The most important parts to a great spec are context, design considerations, and implementation details. 
Check out the [spec bible ](https://hackmd.io/Wqsic-XXSL-a-58YeYtmyg) if you want inspiration
*
-->

### User Experience/UX Goals:

<!-- What will the user experience look and feel like? Informimng or mocking a Low fidelity Figma prototypes welcome, though we recommend deferring to design for everything beyond a high level summary. 
You can also hack together screenshots or looms. Anything articulating the flow and goals.
--> 
<!-- 
E.g., I am trying to see my DAO's settings to add a new member. I land on my profile and click on DAO, i would need to see that I am an admin, from there I see a settings page. On that page i will need to see these functions...etc. 
-->

---
### Completion Criteria

<!--
*What will the end result of each [stage] be?*

Example:
Product [Exploration calls]
1. Evaluate problem and possible low lift solutions on alignment call
2. Set timelines and priority for pitch day

Design [Sketching]
1. Come up with 4 design options for a new attestation feed.
2. Sync (or deliver loom walkthrough)
3. review and finalize
4. Determine if another meeting is needed and skeleton sketch a technical spec. 
5. Consult engineering 
etc. etc.
--> 

Stakeholder and phase
 1. [First step]
 2. [Second step]

### Timeline

<!--
*Is there a timeline or deadline for this work? Attach relevant priority on linear task. 
What needs to be done by when?
If the timeline feels hand-wavey, tag next steps and schedule a quick sync to get everyone onboard. Open the calendar for 10 minutes.*
Good Example:
- Design: 2 Weeks shooting for [handoff] by date (X)
- Build and Implementation sync: Date (x) or follow up date (x) owned by @person
- Ship to staging: Cycle name, Date of check ins, 
- QA: 1 Week
--> 

---

## 📖 Bible

<!--
*This is a general section to put any supporting meeting notes, documentation, etc that accumlates as the project goes on.
-->

### Meeting Notes

<!--
*Most projects will have a few of these or relevant discord threads. Add `---` in between each for a line break and move relevant decisions and follow ons to relevant sections.*
-->

### Considerations & Open Concerns & Discussions Log


### Decisions

<!--
*Add relevant discord threads, links to comments, or votes on chain that resolved outstanding issues from considerations*
-->