Submission Requirements

Submissions must include the full name(s) of the participant(s), a written explanation of the problem/challenge the submission is solving, how it is solving the problem, the impact the solution has on consumer or business travel or the industry, how the solution is demonstrated in a working tech prototype or fully presented design, and how it fulfills each criterion from the Judging Criteria. 

The idea should be a project that you haven't done before and the first day of the hackathon should be the first day you start developing and coding or designing it.

In addition:

  • Participants are required to address one (1) or more of the three (3) themes/challenges presented by TravelScrum.
  • Participants also are invited to use, at their discretion, any of the travel and broader technology APIs offered by TravelScrum and its sponsors (if any) or available from public domains across the internet. Use of APIs and other proprietary technology is subject to terms and conditions of those technology providers/sponsors.
  • TravelScrum will not have a role in agreements between and among the parties on the use of APIs and other tools.
  • Participants are required to conform to the laws of the country in which they reside regarding use of intellectual property, taxes and other fees assessed for cash and other prizes awarded for participation in TravelScrum Hackathon.
  • Participants represent that they are owners, authorized users or licensees of all equipment and software they use at or as part of the hackathon.
  • Participants/developers/teams shall retain ownership of their own code, branding and other intellectual property created during the hackathon. While TravelScrum makes no claim of ownership of any participant-created IP, participants should fully understand all terms and conditions included in licensing agreements for use of third-party APIs.
  • API and other technology providers retain ownership of their technology, branding and other intellectual property, use of which is authorized under each API provider’s terms and conditions.
  • Judges are required to evaluate each project based on their judgment that the project was created specifically for TravelScrum Hackathon (see Judging Criteria).
  • All decisions of the judges are final.

Code of Conduct

You are here to battle the post-pandemic crisis by creating real impact and building ideas into working solutions. This is a hackathon to design and build solutions that can be actionable and launched in the real world, not just to brainstorm and create slide presentations. Implementable business models (mockups), Working code and functioning prototypes are expected to demonstrate a project

Be kind to other participants, organizers and mentors. We are all participating for the same goal of collaboration and competition. 

Be patient – things will go wrong and the volunteer organizers are trying our best to respond to changing conditions and problems.

This is a harassment-free event for everyone, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We do not tolerate harassment of participants in any form. If you become aware of any harassment, please report it immediately to the event organizers. 

No spam, advertising or unnecessary self-promotion is allowed.

Sharing services with team members that could benefit the development of your idea is fine. However, direct selling, soliciting or using the event for commercial advertising is not tolerated.

Other

Void where prohibited or restricted by law, and void in countries/regions under sanctions by the United States, including Cuba, Iran, North Korea, Sudan and Syria.