Time:

This round takes place 2 hours before the official start of the hackathon, allowing teams to present their ideas before diving into development.

Objective:

Teams will pitch their selected problem statement and the innovative solution they plan to develop. This round is crucial for setting the stage for their project, as it allows teams to articulate their vision and plan.

Evaluation Criteria:

Problem Statement Justification:

Teams must explain why they chose their specific problem statement, including its relevance and the potential impact of solving it.

Innovation:

The proposed solution should be novel and demonstrate creativity. Judges will look for originality and how the solution differs from existing approaches.

Problem-Solution Alignment:

Teams must clearly show how their solution addresses the problem statement. The correlation between the problem and the solution is key to demonstrating a well-thought-out approach.

Application Potential and Future Scope:

The team should discuss the practical applications of their solution and its potential for future development or scalability.

Assessment:

Judges will evaluate the pitches based on the originality of the idea and its potential impact. Strong presentations will be well-researched, clear, and compelling.

Format:

The idea must be presented using a PowerPoint presentation (PPT). This presentation should be concise yet comprehensive, covering all key aspects of the idea.

Time:

13 hours after Round 1, this round serves as a mid-point check-in, allowing teams to present the progress they’ve made on their projects.

Objective:

Teams will present the progress they’ve made in developing their solution, providing insights into the methodologies and technologies they’re using.

Evaluation Criteria:

Technology Stack Explanation:

Teams must explain the tech stack they’ve chosen, including programming languages, frameworks, and tools. The rationale behind these choices should be clear.

Detailed Progress Report:

Teams need to provide a detailed report of what they have accomplished so far. This includes a demonstration of any working components or prototypes.

Idea-Progress Correlation:

Judges will assess how well the progress aligns with the initial idea pitched in Round 1. Teams should demonstrate that they are on track to achieve their goals.

Assessment:

Judges will focus on the methodology and approach the teams have taken. They will consider how effectively the team is translating their idea into a working prototype.

Format:

Like Round 1, this round requires a PowerPoint presentation. The presentation should highlight significant milestones achieved and outline the remaining steps.

Time:

9 hours after Round 2, this is the final round where teams present their completed projects to the judging panel.

Objective:

Teams will showcase their final product, including the prototype they’ve developed, and explain how it solves the problem statement they selected.

Evaluation Criteria:

Final Presentation:

Teams must submit a polished PowerPoint presentation that encapsulates the entire journey from idea to final product. The presentation should include key insights, challenges faced, and how they were overcome.

Project Poster:

A project poster must be created to visually summarize the project. This poster should be designed to communicate the core concept, methodology, and outcomes at a glance.

Code Submission:

Teams must submit their code via a GitHub link. The code should be well-documented and structured, allowing judges to review the technical implementation.

Prototyping and Deployment:

Judges will evaluate the functionality of the prototype, including its usability, reliability, and scalability. The deployment strategy will also be considered, focusing on how easily the solution can be put into practice.

Overall Contributions:

The final assessment will consider the contributions of each team member, the cohesiveness of the team, and the overall quality of the project.

Assessment:

This round is critical as it determines the winners of the hackathon. Judges will assess the final product based on its technical merit, creativity, and potential for real-world application.