Rules

  1. It's your hackathon. You can work on anything you like, in any way you like, if you don't want to be part of the contest.
  2. Team size. Teams must have no more than 6 members.
  3. Fresh code. None of your code should exist before the hackathon, and the code must be developed on site. Teams may plan ahead of time, however.
  4. Frameworks. You can use any language, frameworks, platforms, or libraries you wish. You can build an iOS or Android mobile app or a web app.
  5. Publishing code. There will be extra credit for published, open source code — but this is at the team’s discretion. We’d love to see a new software company too!
  6. Schedule. We will start as soon after 6 pm on Friday as we can. We will finish at 3 pm sharp on Sunday, and commence with demos.
  7. Demos. Teams will be selected in random order and presentations/demos will be 4 minutes long (firm), followed by 2 minutes of questions from the judges and if there is time, the audience.
  8. Judging criteria. To compete, you must deliver a working app. You will be scored on originality, functionality, science, impact, and design.
  9. Small print. By taking part in the event, you agree to allow Agile Scientific to include mention of your participation in the event, and to appear in photos and video of the event.
  10. Smaller print. Agile Scientific makes no claim over intellectual property generated during the event. Your work belongs to you and your team.
  11. Smallest print. Agile Scientific reserves the right to change the rules before the event starts, and is the sole arbiter of rule interpretation should disputes arise. Which seems unlikely.