<aside> 👥 An recruiting process outline for setting up your first project team

</aside>

When you are setting up your initial project team, consider the responsibilities that you’re executive board will already be doing and what gaps need to be filled to have a full team to take on a nonprofit project when you begin. On a usual project team you need the following roles

• A product manager - Meets with the nonprofit, plans sprints, assigns tasks, and aligns the team goals with the nonprofit goals
• One or two designers - Conduct user research, engage in creating user flows, mockups, and detailed wireframes
• Three or more developers - Who will be tasked with building out the project itself

To fill in the possible gaps, you need to recruit!!

Step 1: Promote that your club is open for recruitment

The first step in recruiting for your new chapter is reaching out to the general student body to see who would be interested in and work well on a Hack4Impact project team. You can try to reach out to these types of people through the following channels

• Events that other CS clubs host on campus or that the College of Computer may host
• Reach out to be included in all major list servers (emails that go out to the general student body)
• Reach out to professors to be included in class announcements
• Hand out flyers at engineering buildings

Step 2: Organize an informational session for prospective members

To further inform the general student body about the organization, hosting an informational session would be helpful! This step is completely optional but suggested especially for new chapters who may not have an existing network. During an event like this, include the following information:

1. Team Introductions
2. Hack4Impact Overview
3. Chapter Team Structure
4. Why Join Hack4Impact?
5. Past Projects
6. Application Timeline and link to the application