All participants must be older than 18, and must bring a valid form of identification.
Participants must abide by the expectations set in the MLH Code of Conduct, or you will be asked to leave the event.
Teams may be comprised of up to five members.
Projects should be original works created on site. Coming with an idea in mind is perfectly fine, working on an existing project is not.
All submissions must be recieved through DevPost by 1:00PM on Sunday.
Students are permitted to come and go from the venue as they please.
Anything you create is your work, HackPSU and its partners have no claim over intellectual property produced at the event.
HACKPSU GENERAL JUDGING CRITERIA
CREATIVITY AND ORIGINALITY (10 POINTS)
- Is the solution novel, original and not-obvious?
- How different is the design from current solutions?
- Does it approach the problem from an unusual or different perspective?
- How creative is the problem statement?
- Does the solution address a problem which is novel, original and not-obvious? TECHNICAL SKILLS (5 POINTS)
- Was the solution technically challenging? (Taking into account team size and measured relative to competition)
- How intricate was the solution?
- Did the solution pose a challenge to the group? IMPLEMENTATION (15 POINTS)
- Was the solution effective in addressing the problem?
- Was the solution easy to operate for the target demographic? (user friendliness)
- Is the solution needlessly complex?
- Overall, is the solution viable in addressing the problem statement? CLARITY (3 POINTS)
- Was the team able to convey their ideas in a way understandable to the audience?
- Were the topics accessible to the audience?
- Were all obscure acronyms or jargon explained? KNOWLEDGE (12 POINTS)
- How effectively did the team handle questions?
- Did the team demonstrate knowledge of the subject matter?
EDTECH JUDGING CRITERIA
- Importance/Prevalence of the identified issue
- Creativity and feasibility of the proposed solution
- Quality of the solution and/or presentation of the idea
OPTUM JUDGING CRITERIA
1. A solution that works!
- Should be function, although does not need to be pretty (no need to spend a lot of time on UI components)
2. Solution must incorporate an open source health related API or mobile technology
- Must be able to pull data or otherwise demonstrate integration
3. Presentation (Clear, Concise, Captivating)
- No need to have a powerpoint
- Does not need to be on a mobile device
- No need to conduct full market analysis, but should acknowledge existing products