🧑‍🤝‍🧑 Teams

• Team Size

  • Teams can have a maximum of 4 participants. Diverse teams with complementary skills (coding, design, business, etc.) are strongly encouraged.

• Team Merging:

  • Teams with fewer than 4 participants may be merged with other teams. We'll set you up with someone for your team before the event. We prioritize creating teams for those who are solo or in smaller groups, aiming to match you based on the challenge you’re interested in tackling, as well as ensuring a balance of skills within each team.

• Incomplete or Individual Teams:

  Participants registering individually or in incomplete teams (fewer than 4) will be matched into complete teams on the first day of the hackathon. This ensures that all participants have the opportunity to collaborate and contribute effectively to projects.

• Individual Registration:

  • Each participant must sign-up individually / in a team for the hackathon.
  • Individual registrations will be automatically assigned to a team.
  • Incomplete teams (less than 4 people) might go through some changes.

• Team Diversity:

  • We encourage teams to be diverse in terms of skills, backgrounds, and perspectives. A balanced mix of programmers, designers, and domain experts often leads to well-rounded projects.

• Respect and Collaboration:

  • Respect and consideration for team members are essential throughout the hackathon. Each team member brings unique skills and perspectives to the project, and valuing diversity enhances the team's overall effectiveness.

• Mentorship and Support:

  • Mentors and organizers will be available throughout the hackathon to support teams with technical questions, ideation, or logistical issues.

💻 Project Development

• Start of Project:

  • All hacking must begin after the hackathon officially starts. Planning, brainstorming, and design concepts can be prepared beforehand, but no coding or technical implementation is should be before the event start since the exact challenges will be given after the opening ceremony.

• Allowed Resources and Code:

  • Teams can use open-source libraries, frameworks, publicly available APIs, and pre-existing tools. However, the majority of your project's codebase and implementation must be developed during the event.

• Innovation and Originality:

  Projects should demonstrate originality or innovation. Substantially replicating existing products or services without meaningful innovation is discouraged and will get a low evaluation. Originality is a key evaluation criterion.

🕑 Deadlines

• Team Registration Deadline
  • All teams must complete their application by Friday 25th April at 23:59 (Late applications will NOT be allowed). Late registrations will not be accepted, to ensure that all participants receive equal information and preparation time.
• Check-In Time
  • Teams are required to arrive at the hackathon venue by the specified time on the day of the hackathon: Saturday 10th at 9:00. Late check-ins will not be allowed so you won’t be able to take part to the hackathon if you don’t make it there on time.
• Project Submission Deadline
  • Each team must submit their completed project by the deadline set: Sunday 11th at 11:30. Submissions must include all relevant project files, documentation, and any required demonstration videos. Late submissions will not be considered for evaluation.
• Compliance and Disqualification:
  • Failure to adhere to the above deadlines or project submission guidelines may result in disqualification. The hackathon organisers hold final authority over all decisions related to deadlines, submissions and projects presentations.

🎤 Project Presentations

• Teams will present their projects following guidelines provided during the opening ceremony.
• Presentations may include live demos, pitch decks, or video submissions as required by the track.