HACC Judging Criteria

2020 Technical Review Rules

APPLICATION SUBMISSION REVIEW START DATE: Wednesday, Nov 11, 2020 at 9:00 a.m.

Submission Requirements – all applications must be:
  • submitted through the DevPost Team Submission
  • have commitments to Team’s GitHub Repository
  • deployed and a link or instructions on how to run the application included on DevPost Team Submission

If using a project name that differs from your HACC registered team name, you MUST include your team name in your submission instructions to help evaluators find your project.

No code freeze shall be in effect.  Technical review shall commence at the above date and time and it is recommended you have functioning code to be evaluated at this time.  If you experience technical difficulties; need to do bug fixes or make substantial improvements to your solution, you may request a second review.  All submission are assured at least one review.  Second reviews will be at the discretion of the technical evaluation committee and only if time allows.  Therefore, be sure to have a functioning version in by the due date to avoid not being selected due to incomplete or non-working code. Teams may continue improving their solutions and work towards improved demos/ prototype for the judging day presentation.

Submission Rules:
  • If requesting the technical assessment team run your project locally, you must provide clear and concise instructions and they must work. The technical assessment team will NOT set up databases, register for services, troubleshoot startup errors, or anything else that would take specialized knowledge of the workings of the application.
  • Functional Evaluation Videos are required to demonstrate the functional capabilities of the system but shall not replace code being committed to a repository for the technical aspects of this review. If you have a mobile application, you must request time to do a live demo with the technical assessment team. Videos should be provided to evaluators on DevPost
  • If you have a Salesforce, Google, Snowflake, ESRI or any other platform based application, you MUST provide the technical assessment team with access to the application and a written summary of what modules or services were used. Additionally, include a general timeline and scope of work completed if you don’t have custom code on GitHub to show.
  • If the project requires authentication, then access needs to be granted for the judges to login.
  • Judges may reach out to you to gain clarification on any questionable issues. Please be prepared to respond to Slack messages in a timely manner.

Technical Review Criteria

Technical Review Criteria

One or more technical judges will review each submission. Your technical review score will be the percentage of all possible points, rounded to the nearest percentage point.  For example, if Judge 1 gives your submission 19 points, Judge 2 gives your submission 26 points, and Judge 3 gives your submission 28 points, then your technical review score is (19 + 26 + 25)/90 = 78%.

2020 Judging Criteria

Important Dates
  • November 7, 2020 by 5:00 p.m. Teams make final declaration of the challenge they have selected as their project. 
  • November 11, 2020 at 9:00 a.m. – DevPost Team Submission – includes description of proposed solution, link/instructions for code, video – there will be no code freeze, however, teams must be aware that this is when technical evaluations will begin and should make sure to commit working code by this date to ensure the review committee can evaluate your team’s solution.   Teams may continue to refine their solution until judging day. 
  • November 18, 2020 – Team Selection announced – teams who have met a minimum technical point threshold will be invited to present their proposed solutions on judging day and be asked to select a rehearsal appointment slot from on the doodle poll.
  • November 20, 2020 – Selected Team presentations and Zoom rehearsal – During your team’s appointment, your team will connect on a Zoom call with the HACC Committee to confirm their presentations are ready and working.
  • November 21, 2020 at 9:30 a.m. –Presentations will be a maximum of three minutes in length with two minutes allowed for questions from the judges.
Selection of Teams to Present

Final presentations will be made by teams on November 21, 2020 on the Judging and Presentation Day via Zoom. The teams will be informed of their qualification for presentations as soon as the technical review of all teams is complete on Wednesday, November 18, 2020.

To qualify – All teams must have working code submitted in DevPost and GitHub.  Open Challenge teams will be selected based on their meeting a minimum threshold result in the technical review (total tech review percentage needs to be 60% or higher). Top four High and Middle school teams will be selected based upon technical scoring in relationship to other High and Middle school team results.

Total Participation will be limited to 25 teams:

  1. Top four high school and middle school teams;
  2. Top two teams for each of the State challenges (8-16 teams typically);
  3. The top team for all open challenges ;
  4. Remaining invites will be given based on highest scores received in the technical review for teams not selected in the first 3 items. If not enough teams meet the minimum threshold criteria to invite 25 total teams, the number of presentations will be reduced accordingly.

 

The presentation format is a total of 5-minutes:  3-minute presentation, 1 minute maximum live/video demonstration of solution (a walk-through of your application) and 1 minute Q&A.  Teams will be provided with a sample template of the presentation to cover the 5 categories to be evaluated, along with other details judges need to evaluate your work.  If a category is not covered or addressed in your presentation, judges will be directed to provide a score of 0 for that category. The Zoom host will stop presentation at each of these cut off points if necessary.

Judging Criteria

Judging Criteria

Several judges from the community will review each presentation. Your presentation score will be the percentage of all possible points, rounded to the nearest percentage point.  For example, if Judge 1 gives your presentation 16 points, Judge 2 gives your presentation 23 points, Judge 3 gives your presentation 21 points, and Judge 4 gives your presentation 19 points, then your presentation score is (16 + 23 + 21 + 22)/100 = 82%.

Your total score is the average of your technical review score and your presentation score. So, in the above example, the average of the technical review score (78%) and presentation score (82%) is 80%, which is the final score for this submission.

Tie Breaker for Prize Positions:  if two or more submissions are tied, the Presentation Judges will vote on the tied submissions, with the Administrator casting the tie-breaking vote, if necessary.

The Audience Favorite award will awarded a separate prize.