Teams

• Team Size

  • Teams may consist of up to 4 participants. We encourage diverse teams with varied skill sets to foster innovation and creativity.

• Team Merging:

  • Teams with fewer than 4 participants may be merged with other teams during the team formation period. 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.

  • What happens if my team is not made up of 4 people, or if I don't have a team?

    No worries! If your team isn't complete or if you're flying solo, we'll find teammates the first day of the event, before hacking starts. 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. This is a fantastic opportunity to meet new people and combine talents for an exciting hackathon experience.

• 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.

• Respecting Team Members:

  • 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.

• Team Support:

  • Organizers and mentors will be available throughout the hackathon to provide guidance, support, and assistance to teams as needed.

Project Development

• Project Initiation
  • All project work must commence only after the official start of the hackathon. Pre-event work, excluding planning and design brainstorming, is against the rules to ensure a level playing field.
• Use of Pre-existing Code
  • The use of libraries, frameworks, and open-source code is allowed, but the substantial work on the project must be performed during the hackathon. This encourages innovation while still allowing teams to leverage existing tools and platforms.
• Innovation and Originality
  • Projects should aim for innovation or an original implementation of ideas. Originality is often a key evaluation criterion. Teams are encouraged to think creatively and push the boundaries of conventional solutions.

Deadlines

• Team Registration Deadline
  • All teams must complete their application by Saturday 13th 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.
• Arrival Time
  • Teams are required to arrive at the hackathon venue by the specified time on the day of the hackathon: Saturday 20th at 9:00. This ensures that all teams are present for the opening remarks, understand the event's structure, and are ready to start simultaneously.
• Project Submission Deadline
  • Each team must submit their completed project by the established deadline: Sunday 21st at 12:00. 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 deadlines and submission guidelines may result in disqualification.
  • The hackathon organizers reserve the right to make final decisions on any matters related to deadlines, submissions, and presentations.

Presentation Format

Teams must prepare a presentation of their project according to the guidelines provided. This may include a live demonstration, a pitch presentation, or a video submission. The exact format and any associated requirements will be announced during the opening ceremony. All the presentations must be in english.

Warranties

By participating to the Hackathon every participants must guarantee that the “project” developed: