The Mega Event
8-Hour Software Hackathon

• Theme: Adherence to the theme announced on the day of the hackathon is mandatory.
• Time Management: Development must be completed within the 8-hour limit.
• Originality: Only original work developed during the event is acceptable.
• Resources:
  • Any programming language or tools can be used
  • Internet access is provided
  • Participants must bring their own devices
• Conduct: Professionalism and respect are expected towards everyone at the event.
• Submission:
  • Final submissions must be uploaded to GitHub by the end of the 8-hour period
  • Hourly pushes are required
  • Late submissions will not be accepted
• Judges' Decision:
  • The judges' decision is final
  • Any disputes must be reported to the event coordinator within 30 minutes after the results

The judging panel will include experienced professionals and academics from the software development and technology fields. They will ensure a fair evaluation based on predefined criteria.

• Innovation: Creativity and originality of the solution.
• Functionality: Technical quality and effectiveness of the solution.
• Usability: User-friendliness and design.
• Relevance: How well the solution addresses the theme.
• Presentation: Clarity and effectiveness of the presentation.

Focus: Idea Clarity and Foundation Building

• Clarity of Idea (30%):
  • How well-defined is the problem the team is addressing?
  • Is the proposed solution feasible and aligned with the theme?
• Initial Setup (40%):
  • Has the team successfully built the foundation of their software?
  • Does the project have a clear structure (e.g., project framework, database setup)?
• Team Collaboration (30%):
  • Are team members working effectively and dividing tasks efficiently?

Outcome: Teams failing to establish a clear base or demonstrate meaningful progress will be disqualified at this stage.

Focus: Midpoint Progress and Functional Prototype

• Progress Towards Completion (40%):
  • Is there visible and substantial progress on the project (e.g., working prototype or initial features)?
  • Are the key functionalities halfway implemented?
• Functionality (30%):
  • Do the implemented features function as intended?
  • Is there evidence of a working backend or user interface?
• Usability and Design (30%):
  • Does the project demonstrate a focus on user experience (e.g., intuitive design, navigation)?

Outcome: Teams are expected to have a functional prototype. Those with minimal or unclear progress risk elimination.

Focus: Final Product and Presentation

• Completeness and Functionality (40%):
  • Is the software complete and does it perform all intended functions?
  • Are there minimal bugs and smooth workflows?
• Innovation and Relevance to Theme (30%):
  • How creative and original is the solution?
  • Does the project align well with the hackathon theme?
• Presentation and User Experience (30%):
  • How well did the team present their project (clear explanation, demo, and Q&A)?
  • Is the final product user-friendly and visually appealing?

Outcome: Final judging will determine the winners based on the quality and impact of their final solution.