HackathonGuidelines .pdf

File information

Original filename: HackathonGuidelines.pdf

This PDF 1.4 document has been generated by , and has been sent on pdf-archive.com on 09/10/2015 at 22:49, from IP address 163.118.x.x. The current document download page has been viewed 369 times.
File size: 245 KB (3 pages).
Privacy: public file

Download original PDF file

HackathonGuidelines.pdf (PDF, 245 KB)

Share on social networks

Link to this file download page

Document preview

Hackathon Guidelines
Date: 10/10/2015

9:00am - 10:00am -

Team Building and Strategy

10:00am - 9:30pm -


9:30pm - 10:00pm -

Hack Demo and Judging

10:00pm - 10:30pm -

Winners announced and prizes (See prizes below)


Olin Engineering Auditorium

(Tons of refreshment available during event)

Team Building
This stage of the hackathon is self-explanatory, but tricky to execute. A perfect team
would generally consist
● The person with the idea
● The programmer or hardware person
● The designer
A team is limited to a ​
maximum of 4 people​
and a ​
minimum of 1​
. It is beneficial to form
a team of more than one person, because if one decides to go for a break, the other can
keep working.


You will probably need to go over what kind of app or hardware you want to build, and
analyzing it before starting development.

This is the development process, the moment you put your brain juice to work. We got
energy drink to help with this process. You are required to create an app or hardware
within the time frame

Each team will have the chance to give a demo to the judges individually, as well as a
5-minute powerpoint presentation at the end of the judging.

Judging Criteria (Ordered based on priority)
1. How close to a ‘product’ the hack is
2. Originality
3. Projected impact on the world
4. Intuitiveness / Ease of use
5. Eye candy
6. Demo / Powerpoint presentation

1st Place:

A RC Quadcopter Drone with HD Camera

2nd Place:

An Android/iOS compatible smartwatch

3rd Place:

A Wireless Bluetooth Headset


Swag / Giveaways
● 10 Selfie Sticks (Available on a first-come first-serve basis)
● Lots of swag from Google


Are we going to be breaking into a computer?


Unfortunately not. A hackathon (at least in the traditional sense) doesn’t

deal with that kind of hacking. ‘Hacking’, used in this sense, means creating something
cool that works, or kinda works or looks like it works. So an app or a flashy hardware
creation/modification can pass as a hack in this case.

Do I have to be a super-good programmer to compete?


The strongest point of a hackathon is bringing out the best in you. Even if

you think you aren’t good enough, join a team and try to contribute to the team’s
success in any way you can. Usually, people come out of a hackathon with 2 times the
experience they had going into it. So you never know, you might even end up winning.
It’s worth a shot at least.

Do I have to be a CS student to compete?


No. The products made in this hackathon can be hardware or software.

The rules are just that simple: make something cool

Can I use an already made project?


The goal of the hackathon is to create something new. You may not

present a project made before the competition. However, you may use pre-built themes
and wireframes to speed up your design

Do I have to be in the venue all the time?


Not necessarily. You only have to be available at check-in and at least the

final 2 hours of the competition. Hacking can be done from anywhere.

Document preview HackathonGuidelines.pdf - page 1/3

Document preview HackathonGuidelines.pdf - page 2/3
Document preview HackathonGuidelines.pdf - page 3/3

Related documents

sponsorship document
hacking the hype why hackathons don t work techcrunch
prospectus 1

Link to this page

Permanent link

Use the permanent link to the download page to share your document on Facebook, Twitter, LinkedIn, or directly with a contact by e-Mail, Messenger, Whatsapp, Line..

Short link

Use the short link to share your document on Twitter or by text message (SMS)


Copy the following HTML code to share your document on a Website or Blog

QR Code

QR Code link to PDF file HackathonGuidelines.pdf