1.1 Network Name
SSID Name TBA
SSID Password TBA
1.2 Shirt Colors
|Friday, March 29, 2019|
|4:30 PM | Registration Open|
|5:00 PM | Networking and Dinner Served|
|6:00 PM | Open Ceremony|
|6:30 PM | Hacking Begins|
|10:30 PM | Midnight Snack|
|11:00 PM | Slideshare Karaoke|
|Saturday, March 30, 2019|
|8:00 AM | Breakfast Served|
|8:30 AM | Hacking Resumes|
|11:30 AM | Lunch Served|
|1:00 PM | Projects Due|
|1:30 PM | Team Technical Check-in|
|2:00 PM | Project Presentations|
|4:00 PM | Judge Session|
|5:00 PM | Award Ceremony|
4. Software and APIs
6.1 Request a Mentor
You can request a mentor on Slack from the #mentors channel on Slack.
8. Submissions and Judging
8.2 Judging Criteria
Business Model. | Outside of technical impressiveness in the project, during this hackathon judges will be looking for how teams communicate customer validation (Who are your users?) and acquisition strategy (How will you attract your users?). Those two pillars will help validate the idea.
Impact. | Our theme this year is to create a solution that will help improve the betterment of the DMV community. In this category we are looking for key factors that shows how the team's idea is scalable and give a clear measure as to how thier solution makes an impact on the user's life.
Technical. | In the midst of the given 24 hours the judges will be looking for an established minimum viable product and a working prototype . This can range from a web application, mobile application or an IoT.
Design and User Experience. | The teams final minimum viable product and prototype should achieve an engaging and memorable user experience. This means having a clear interface that is intuitive for users that come from different backgrounds.
Presentation. | Teams will be rated base off presentation layout and articulation of their solution. This means how well was the team able to communicate their target audience, problems they are solving and how their product is the solution to that problem.