The theme for this year's hackathon is "Coding Sprint 2023: Supercharging Innovation On-The-Go." The theme implies that the hackathon competition this year will be an exciting opportunity for people to supercharge their innovation efforts and drive progress towards their goals.
The hackathon competition is open to all currently enrolled CIS students of Kolehiyo ng Lungsod ng Dasmariñas. Competitors must be in good academic standing (do not have a GWA lower than 2.5) and have no violations to the school policies and regulations.
Teams must be formed prior to the event with a maximum of 5 members and should include students with a range
of skills, such as programming, design, and research.
Teams should be made up exclusively of CIS
students who are not event organizers, facilitators, judges, sponsors, or in any other privileged position
at the event.
Since the development and coding will be done remotely, participants will be using their own devices ensuring
that they have all the necessary software and tools
installed to develop their project.
Participants are required to bring at least one laptop per team for the wireframing and project presentation onsite.
Participants who plan to utilize online resources will need to bring their own internet connection, while those who don't have internet access can use offline resources
instead.
Due to time constraints, the coding timeframe is strictly limited to overnight. This restriction encourages participants to work efficiently and creatively within a limited timeframe, which can be a valuable learning experience.
The coding timeframe for a hackathon starts at 3 PM and ends at 6 AM the next day, the total duration of the coding timeframe would be approximately 15 hours.
GitCub officers will serve as mentors and will be available throughout the hackathon to provide guidance and support to participants.
Teams can use libraries and frameworks in their projects.
Participants can use templates with only basic UI elements. They are allowed to use pre-made
templates, but is not allowed to use any pre-existing functionalities or complex UI components.
The
main goal should be to modify the templates to create something unique and creative. Participants can add
new features, modify existing ones, and change the overall design of the template.
Teams are required to stop hacking once the designated time is up and must be present at the event venue at the exact time. However, they are permitted to debug and make minor fixes to their programs after the allotted time. For example, if a team discovers a bug during their hack demonstration that breaks their application, they may make a few lines of code changes to fix the issue. However, significant modifications or the addition of new features are prohibited.
All
intellectual property rights to the projects developed during the hackathon will remain with the
participating team.
Participants must treat all team members, including competitors, judges, mentors, facilitators, etc., with
respect and courtesy, abiding by the school’s code of conduct.
Teams can be disqualified from the
competition at the organizers’ discretion. Reasons might include, but are not limited to, breaking the
competition rules, behaving in a way that violates the school’s code of conduct, or other unsporting
behavior.
As per our Code of Conduct, there is no discrimination on the basis of race, religion,
national origin, color, sex, gender identity, sexual orientation, social class, economic status, veteran
status, disability, or age.
Each team will be given a set amount of time to present their project to a panel of judges. The presentation should clearly describe the project, its purpose, and its features.
The distribution of prizes or rewards will be determined by the event organizers. The decision of the
organizers is final and binding.
Projects will be judged based on the following criteria:
Innovation and Creativity (30%): The project should demonstrate a unique and innovative approach to
solving a problem or creating a new product. Judges will evaluate how well the project stands out from other
solutions or ideas that have been previously developed.
Technical Execution (30%): The project should demonstrate technical skill and proficiency in the
development process. Judges will evaluate the quality of the code, the use of appropriate tools and
technologies, and the overall technical feasibility of the project.
Impact and Potential (20%): The project should have the potential to create a positive impact on
society, the environment, or the economy. Judges will evaluate how well the project addresses a real-world
problem, the scalability of the solution, and the potential for future development and implementation.
Presentation and Communication (10%): The project should be presented clearly and effectively, using
appropriate visuals and demonstrations. Judges will evaluate how well the team communicates the problem, the
solution, and the potential impact to the audience.
Teamwork and Collaboration (10%): The project should demonstrate effective teamwork, collaboration,
and communication among team members. Judges will evaluate how well the team members work together, the
level of individual contributions, and the overall project management and organization.
While these criteria will serve as a guide, judges are ultimately granted the freedom to use their
expertise and technical intuition to determine which projects are the most impressive and deserving. The
judges' decisions will be considered final.
Developing a startup: If the web-based app developed during the hackathon is innovative and has potential in
the market, the participants may consider turning it into a startup. They can explore funding opportunities
and build a team to bring their app to market.
Job opportunities: Participating in a hackathon showcases the skills and abilities of the
participants, making them more attractive to potential employers. The participants can leverage their
experience in the hackathon to find new job opportunities.
Networking: Hackathons provide opportunities to network with other participants, mentors, and
judges. Participants can build relationships with people who share similar interests and are involved in the
same industry, potentially leading to future collaborations.
Continued Learning: Hackathons provide a fast-paced environment for participants to learn new
skills, tools, and technologies. Participants can continue to build on their experiences by exploring more
about the tools they used, learning more about the subject area of the hackathon, and seeking out other
educational opportunities.
Industry recognition: Winning a hackathon or being recognized for a successful project can lead to
industry recognition and increased visibility. Participants can leverage this recognition to further their
career or startup opportunities.
Day before the event: Briefing with the teams for preparation for the upcoming competition
Participants will be provided with details of a particular business problem and will need to concentrate on
creating a solution. The organizers will offer recommendations on the suggested solutions or systems that
could be developed.
Day 1 (Morning) – Pitch Presentation
There would be a pitching session for topics, during which the participants will be introduced. Each team
will present their proposed solution to the business problem that was discussed during the briefing. Due to
time constraints, the ideation, research, and brainstorming of each team will be done the day before the
competition.
Day 1 (Afternoon) – Wireframes Presentation
After the pitching presentation, participants will need to create wireframes within a limited time. Each
team will then present their wireframes and initial designs to the judges.
Development and Coding
To accommodate time constraints and facility/resource limitations, the participants will work on their
projects remotely. This approach creates a more inclusive and accessible environment that fosters innovation
and collaboration, as participants can work on their projects at a time and location that suits them best.
Allowing remote work is a practical solution that ensures the success of the hackathon while providing
participants with an optimal experience.
Day 2 – Final Demo and Presentation
The Hackathon Final Round is the culminating event of the competition, where each team will present their
completed web-based app to a panel of judges and an audience. This final demo and presentation will showcase
the system that they have created throughout the hackathon.
During the final round, each team will have a
set amount of time to demonstrate the functionality and features of their web-based app. They may show how
users can interact with the app, highlight the app's key features and functionalities, and explain the
benefits and value of their app to the audience and judges.
Teams will also need to be prepared to answer
questions from the judges and audience about their app, including the technical aspects of the development
process, the user experience, and the overall concept and design of the app.
The judges will evaluate
each team based on various criteria, such as the app's functionality, usability, innovation, and overall
impact. The winning team will be announced at the end of the final round, and may receive prizes,
recognition, and opportunities for further development of their app.
The goal of the Hackathon Final
Round is to showcase the impressive work of each team, and to determine the winning team based on their
creativity, technical skills, and ability to deliver a functional and innovative web-based app.