MbShea@PWP@English@UMCP

Working Title: Hackathon Design Teams: What They Do and How They Do It

Audience: high school / college students interested in organizing hackathons, particularly the design team

Context: Hackathons are, contrary to its name, an event where people come together to build things, rather than hack into stuff. UMD is home to two large hackathons, Bitcamp and Technica, and over the years there has been a steady increase in interest for helping to organize these events. First time hackathon organizers or participants that are thinking of getting involved in actually organizing hackathons are likely to not know where to start.

Purpose: To guide the reader through organizing and managing the Design team of a hackathon. This document will focus on how the design team is put together, what responsibilities the Design team is in charge of and how to carry them out, the type of collaboration expected with other teams, and how to help make the hackathon a success. More specifically, this document will serve as a guide for the next Design Lead who will be taking my place next year. However this document can also be of use to other members of the team as well.

DOCUMENT TYPE: A manual/guide on what to keep in mind when forming and leading the design team of a hackathon

H, this looks like a folder of guides on how to keep this student activity in play, after people graduate. You have a colleague who is looking at this, too. Let's connect you about a possible group project or one that is parallel. Ask me.