The Region III Hackathon is a creative problem solving challenge for all. Teams of 2-4 will work diligently for 8 hours to develop a code towards a technical issue. This event is open to all majors. Meals and refreshments will be provided. Prizes for winners as well!

 

Time

Task

3:00 PM

Check - In Begins

4:00 PM

Opening Ceremony (Sponsor Introduction, Problem Statements, Rules, etc.)

4:30 PM

Hacking Begins

6:00 PM

Dinner (45 minutes)

11:00 PM

Hacking Ends

11:00 PM

Judging (45 minutes)

11:45 PM

Closing & Awards

Eligibility

Must be a registered collegiate participant at the Region III 2017 Fall Regional Conference in Jackson, MS

Requirements

Only one submission per team. Submissions will be due at 11:00 PM CST.

  • There will be two deliverables:
  • A 3-5 sentence submission with the category selected and the solution that your team has developed and submitted to the Programs Chairperson by 11:00 PM on Friday, November 3rd
  • A final project
    1. At least one member from the team must remain in the room!! (Rotating for restroom breaks, snacks, etc. is permitted)
    2. NO LATE SUBMISSIONS WILL BE REVIEWED
    3. Teams CANNOT employ outside help on submitted projects
  • Teams must submit their final projects to the following link by 11:00 PM CST November 3, 2017. If any projects are late, they will not be reviewed.

Hackathon Sponsors

Prizes

1 non-cash prize
Awards & Recognition
3 winners

First, second, and third place winners will be awarded and recognized accordingly.

Devpost Achievements

Submitting to this hackathon could earn you:

Judges

Regional Advisors

Regional Advisors

Judging Criteria

  • Innovation/ Ambition
    ● Was the idea unique, or a different take on an existing/similar app? ● What was added to the app that made it special or more useful? ● Was the idea behind the app ambitious? Creative? ● How well did the app execute upon the theme/category chosen?
  • User Interface / User Experience
    ● Does the UI of the app look professional/fun, or is it sloppy? ● Is the app easy to use? ● Does the workflow of the app make sense, is it intuitive?
  • Overall Quality
    ● Does the app work? ● How many & how severe were any bugs encountered? ● Was anything in the app that wasn’t fully implemented (a useless button that was supposed to do something)? ● Did the team scope their app’s features well given the time frame?
  • Quality of Pitch/ App Impact
    ● Does the app seem like something people would want to buy and use outside of the Hackathon? ● Was the team able to explain their idea and what the app actually did?

Questions? Email the hackathon manager

Tell your friends

Hackathon sponsors

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.