Hackathon Rules and Assessment
Rules
- Teams must consist of 2 to 3 members.
- Teams must have a functioning prototype or MVP by the end of the event to present to judges.
- Plagiarism is prohibited and can result in disqualification.
- Implementation via code is not mandatory.
- Participants can request access to any content GTAF has.
- All work must be done during the hackathon event and cannot be pre-existing projects.
- Both the participants and GTAF will own all resources developed during the hackathon.
- Participants can't leave the premises during the hackathon hours.
N.B.: All participants must abide by a code of conduct and anti-harassment policy.
Assessment Criteria
Concept: The concept must adhere to the theme, and the team should demonstrate its usefulness. Both the problem and the solution should be well defined.
Concept: The concept must adhere to the theme, and the team should demonstrate its usefulness. Both the problem and the solution should be well defined.
Usability and User Experience: The project must not be perfect or production-ready, but the UX must be considered while designing.
Usability and User Experience: The project must not be perfect or production-ready, but the UX must be considered while designing.
Feasibility: Budget, data, tech and other constraints must be considered.
Feasibility: Budget, data, tech and other constraints must be considered.
Presentation
Presentation
Bonus:
Bonus:- Real user feedback and desirability
- Aesthetics
- Readiness for production
Panel
Mentors
Yemin Sajid
Nabil Mosharraf Hussain
Zunaid Aslam
Faisal Hossain
Judges
Sharif Abu Hayat
M Mahbubur Rahman
Modasser Billah Tishad
Abdullah Anwar
The organising committee holds the right to change any rules if necessary, and the teams will be notified.
Any decisions made by the organising committee are final.