# Project guidelines and resources

**URL:** <https://discourse.codeforamerica.org/t/project-guidelines-and-resources/1083>\
**Category:** Partnerships\
**Tags:** best-of-discourse\
**Created:** [April 13, 2021, 7:34pm UTC](https://discourse.codeforamerica.org/t/project-guidelines-and-resources/1083 "2021-04-13T19:34:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhorowski](https://avatars.discourse-cdn.com/v4/letter/m/4da419/32.png) [@mhorowski](https://discourse.codeforamerica.org/u/mhorowski)\
**Post date:** [April 13, 2021, 7:34pm UTC](https://discourse.codeforamerica.org/t/project-guidelines-and-resources/1083/1 "2021-04-13T19:34:26Z")

</div>

From Code for BTV:

Here’s our so-called “[Partner Packet](https://drive.google.com/drive/folders/1Xyp_85NOPMdUKOO52Mbikz5p5KjzjvCC?usp=sharing)”: 4 documents (and an overview) that can be used when setting expectations and roadmaps for selecting, initiating, developing and closing projects. This information is destined to always be a work in progress (even on a quick skim now I see things I want to change ), but it is a helpful starting point. There are a few things this info attempts to do:[Project Selection Guidelines](https://docs.google.com/document/d/1-m-G6XrrhspheVBKIeMxj_DiOJSk86c_zCzkJSUcGXA/edit)

- helps people quickly understand which types of projects are best suited for work in our brigade
- good talking-piece to help orgs & members consider project scope before committing to the work

[Operating Principles](https://docs.google.com/document/d/1jpJMCuBvIi_m51_xLeDk6rq0U3inS22JzpLJhUaeN_o/edit)

- Important for helping partners see the project as a whole, including their role & the responsibility of ultimately owning the project
- Great checklist for brigade/proj leaders to make sure we cover the things that are easy to forget

[Project Proposal](https://docs.google.com/document/d/1a0PUUlPTHNRhUIIpXph7p25Mt_-wqErYvDu7eS3gBmQ/edit?usp=sharing)

- Intended as a discussion piece to focus attention on proj aspects that are often skipped or punted
- Not at all helpful if used as a substitute for a thoughtful conversation
- Likely needs a lot of modification & updating - haven’t reviewed this in a while…

[Post-Project Follow-Up](https://docs.google.com/document/d/1pZE3W5vpc-i_WeVWkcHxpjQZa6fjmDoJhCYQ_TEsvB0/edit?usp=sharing)

- Checklist for crossing T’s and dotting I’s when wrapping up a project
- Important expectation setting for project leads to clarify that “deploy to prod” **≠** “done”, but also that projects should (ideally) be finite.
- Also good expectation setting for partners.
- Honestly, this is an aspirational checklist - not sure we’ve actually ever done _all_ these things on a single project

---

<div class="post-metadata">

**Author:** ![mzagaja](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mzagaja/32/121_2.png) [@mzagaja](https://discourse.codeforamerica.org/u/mzagaja)\
**Post date:** [January 13, 2022, 2:24am UTC](https://discourse.codeforamerica.org/t/project-guidelines-and-resources/1083/3 "2022-01-13T02:24:45Z")

</div>

Just saw this post for the first time and these are some really great resources. Thanks for sharing!

---

<div class="post-metadata">

**Author:** ![Mari](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.codeforamerica.org/mari/32/992_2.png) [@Mari](https://discourse.codeforamerica.org/u/Mari)\
**Post date:** [July 1, 2023, 6:53am UTC](https://discourse.codeforamerica.org/t/project-guidelines-and-resources/1083/4 "2023-07-01T06:53:59Z")

</div>