1. Team Structure

One of the key aspects of the hackathon is teamwork. In a collaborative setting, teamwork is essential to ensure a diverse and rich set of ideas are brought to the table, which leads to better solutions.

• Maximum Team Size: 3 Members
  Each team can consist of up to three participants. This limit ensures that teams remain manageable while still being large enough to allow for the pooling of diverse skills and perspectives. With a smaller team size, communication tends to be more efficient, which is crucial given the limited time frame of the event.

  The team dynamic should include participants with varying skill sets, such as coding, design, project management, and user experience. A well-balanced team can leverage each member’s strengths, which significantly improves the quality and feasibility of the final solution.

• Solo Participation: 1 Member Per Team
  Participants who prefer to work independently can opt for solo participation. This decision should not be taken lightly, as working alone means that you will be responsible for every aspect of the project. Solo participants should have a comprehensive skill set, including coding, design, and testing, as they will need to handle every aspect of the development cycle themselves.

  While solo participation can be challenging, it offers a unique opportunity to showcase individual skills and creativity. Participants choosing this path should be prepared to manage time effectively and remain focused throughout the event.

2. Project Requirements

The primary goal of the hackathon is to foster innovation. To ensure that all participants are solving real-world problems and addressing important challenges, the following requirements must be met:

• Topic/Challenges from the Organizer-Provided List
  A list of pre-selected topics or challenges will be provided by the organizers prior to the event. This list ensures that all projects remain relevant to the theme of the hackathon and that participants address challenges that matter. The topics have been carefully curated to reflect the current needs of the industry or society, and they serve as a guide for participants to brainstorm solutions.

  It is important to note that participants are required to select topics from this list. External or unrelated topics are not permitted. The reason for this rule is to maintain consistency across the competition and ensure that all participants are solving problems within a similar scope, which allows for more focused and relevant judging.

• No External Topics Permitted
  This rule helps to keep the competition fair and organized. If participants were allowed to choose their own topics, there might be a wide variety of unrelated ideas, making the judging process more subjective and difficult. By restricting topics to those provided by the organizers, the competition remains focused and ensures that all participants are contributing to solving similar types of challenges.

• All Code Developed During the 15-Hour Event
  One of the most important rules of any hackathon is that all code should be developed within the event’s time frame. This ensures that the competition remains fair and that no one has an unfair advantage by using pre-written code, templates, or tools developed outside of the event. The goal is to test the participants’ ability to think creatively, design solutions on the spot, and work under time pressure.

  Exceptions to this Rule:
  There are a few exceptions to this rule. Specifically, publicly available libraries, frameworks, and open-source tools may be used during the event, provided they are attributed correctly. This allows participants to build on existing technology, making the development process more efficient and promoting the use of tried-and-tested solutions. However, it is important to note that these libraries and frameworks must not be pre-built solutions that solve the challenge but should only be used as a supporting tool in the development process.

3. Event Schedule

The event will take place within a specific timeframe, and adhering to this schedule is critical to ensuring the event runs smoothly and is fair to all participants.

• 15-Hour Timeframe: Strictly Enforced, No Extensions
  The event is designed to challenge participants to think quickly and solve problems within a limited timeframe. The 15-hour window is strictly enforced, and no extensions will be granted, regardless of the circumstances. This helps simulate the real-world pressure of working within tight deadlines, a scenario participants will encounter frequently in the tech and start-up world.

  The event schedule will be carefully structured to ensure that participants have adequate time to plan, design, develop, and test their projects. There will be periods for brainstorming, coding, and refinement, but once the timer is up, all work must cease. This rule emphasizes the importance of time management and preparation.

• Teams May Take Breaks, But At Least One Member Must Remain at the Venue
  While breaks are encouraged for participants to recharge, it is important that the work continues throughout the event. Teams must ensure that at least one member remains at the venue at all times, ensuring continuous progress. The remaining members can take breaks as needed, but it is essential that work is always being done to complete the project within the given timeframe.

4. Technology & Equipment

The right tools and technology are critical to the success of any hackathon project. Participants are encouraged to bring their own devices and software tools, but certain equipment may be provided by the organizers to help with the development process.

• Use of Tools, Languages, and Frameworks
  Participants are free to use any programming language, tools, or frameworks that they are comfortable with. The event is meant to allow creativity to flourish, so there is no restriction on the type of technology used, as long as it helps to solve the problem at hand. Whether you are working with Python, Java, JavaScript, or any other language, you are free to choose what works best for your project.

  However, participants should ensure that they are familiar with the tools they are using, as there may be limited technical support available. Using unfamiliar or new tools during the event could hinder progress due to setup or configuration time.

• Bring Personal Devices (Laptops, Peripherals)
  Participants should bring their personal laptops and any peripherals they might need, such as a mouse, keyboard, or external storage devices. Having your own equipment ensures that you are comfortable working with the setup you are familiar with, which can help maximize productivity during the event.

  In the case that participants do not have access to their own devices, the organizers will provide computers on a limited basis. Requests for organizer-provided computers should be made well in advance of the event to ensure availability.

• Participants are Responsible for Software Setup
  Participants are expected to handle their own software setups, including installing the necessary programming environments, libraries, and frameworks. While there may be some technical support available, participants should come prepared with all the necessary software installed and configured ahead of time. This allows more time for actual project development during the event.

5. Judging & Winners

The judging process is one of the most critical aspects of the hackathon, as it determines which teams’ solutions best address the challenges.

• Judges’ Decisions Are Final
  The decisions of the judges are final and binding. They will evaluate projects based on the criteria outlined in the event rules and any additional judging rubrics provided. Judges typically come from diverse backgrounds, including technical experts, industry leaders, and professionals with experience in the field. Their role is to fairly assess each project’s innovation, feasibility, and overall impact.

  Participants should be prepared to present their projects clearly, demonstrate how their solution addresses the problem, and show how it works in action. The judges will consider the technical complexity of the project, how well it meets the challenge requirements, and the overall impact the solution could have.

• Criteria for Winning
  While the specific judging criteria will be outlined in detail prior to the event, participants can expect to be judged on factors such as:

  • Innovation: How unique or original is the solution? Does it present a fresh approach to the problem?
  • Impact: How meaningful is the solution in addressing real-world problems? Does it have the potential to make a tangible difference?
  • Feasibility: How practical is the solution? Is it something that can be implemented or scaled?
  • Technical Complexity: How sophisticated is the project in terms of design, coding, and development?
  • Presentation: How clearly and effectively is the project presented? Does it communicate the idea and functionality effectively to the judges?