Project Setup
Set up your Civic Tech DC project and prepare for your first official Project Night.Your project has been accepted into Civic Tech DC; congratulations! Now it’s time to prepare it for volunteers to join and contribute.
Project Setup covers the basic steps you need to complete before your first official Project Night. You don’t need to have everything figured out, but you should come prepared with a good pitch and enthusiasm for getting others involved.
For more detailed guidance on organizing your team, managing your project, or setting up technical tools, see our Lead a Project, Grow a Project, and Technical Resources guides.
1. Document Your Project
Section titled “1. Document Your Project”Before recruiting volunteers, make sure your project has a clear purpose and a realistic starting point.
Complete the Project Brief Template to document the problem you’re trying to solve and what you hope to build or accomplish. You can also reuse this brief as a one-pager to help onboard new contributors and introduce them to your project, so you won’t have to start from scratch later.
Example: A Completed Project Brief
Section titled “Example: A Completed Project Brief”Not sure how detailed your project brief should be? Here’s an example of what a small civic tech project might look like when it’s ready to welcome contributors.
This is an illustrative example, not an existing Civic Tech DC project.
Project: Community Resource Finder
Section titled “Project: Community Resource Finder”The problem
Residents looking for free or low-cost community services often need to search multiple websites to find information about food assistance, digital literacy programs, and other local resources. Information may be outdated or difficult to navigate.
Who we’re working with
A local community organization that regularly helps residents find services. The organization would help identify common information needs, review early designs, and provide feedback on whether the tool is useful.
What we’re proposing
A simple, mobile-friendly directory that allows users to browse community resources by category and neighborhood.
What success looks like
- Community partners can find and share relevant services more easily.
- Residents can access the directory on a phone without creating an account.
- The partner organization has a manageable process for updating information.
Initial scope
Our first version will focus on one service category and a limited geographic area. We’ll test it with the partner before considering additional categories.
Out of scope
- User accounts or personalized recommendations
- A comprehensive directory of every service in DC
- Automated collection of information from third-party websites
- Features that require collecting sensitive personal information
Current status
Early planning. We have identified a potential partner and drafted the problem statement, but still need to validate the proposed approach with users.
Next milestone
Interview partner staff and potential users, confirm the first service category, and develop a basic prototype.
2. Identify Contributor Needs
Section titled “2. Identify Contributor Needs”Think about what kinds of contributions your project needs and what volunteers can realistically work on. Complete the Volunteer Contributor Needs Template to identify roles, and refer to the Contributor Pathways page for ideas on how volunteers can get involved.
Example: Contributor Needs
Section titled “Example: Contributor Needs”| Role | What someone would help with | Good first task |
|---|---|---|
| User researcher | Understand how people currently find services | Draft five interview questions |
| Designer | Create an accessible directory interface | Sketch a mobile search page |
| Developer | Build a small searchable prototype | Set up the project repository |
| Data contributor | Review resource information | Check ten sample directory entries |
| Documentation contributor | Make the project easy to join | Draft the README and setup instructions |
What Makes This a Useful Brief?
Section titled “What Makes This a Useful Brief?”Notice that the project doesn’t begin with a long list of features or a preferred technology stack.
It explains the problem, identifies who should help validate the work, limits the initial scope, and gives volunteers concrete ways to contribute.
A project brief should be detailed enough to help people get started, but flexible enough to change as the team learns more.
3. Set Up Your Project Tools
Section titled “3. Set Up Your Project Tools”Every project needs a central place for contributors to find information, communicate, and work together.
Before your first Project Night, make sure you have:
- A project Slack channel. Create a channel in the Civic Tech DC Slack workspace for your team. You should make it public so people can find and join your project. Slack also allows you to add tabs at the top of a channel for onboarding documents, links, and other resources.
- A GitHub repository, if your project involves code.
- A shared location for project documentation. Google Drive is a good option and makes contributors have appropriate access.
For instructions on GitHub access, repositories, and other tools, visit Technical Resources.
4. Prepare for Your First Project Night
Section titled “4. Prepare for Your First Project Night”Your first Project Night is an opportunity to introduce your project to the community and begin building your team. Come prepared to explain what you’re working on and what you need help with. For more guidance on running Project Nights, see Lead a Project.