Judging

All projects will be judged by the following:

  • Documentation (10%): Did student include the required permissions, pre-planning documentation, pseudocode, flowcharts, storyboards, etc…
  • Complete and Functional (15%): Is the project complete and does it function properly?
  • Creativity (20%): Student’s creativity in the design as well as the oral presentation.
  • Understanding (25%): Student’s understanding and mastery of the software used. Higher points for software that requires a deeper understanding of the project category in categories like Mobile Apps, or Project Programming.
  • Intended Purpose (30%): The overall effect of the project and all of the elements within. How well do the elements work together to create the intended effect or serve the intended purpose of the project?

At the time of the judging, students will be required to:

  1. Use the program or applications software to demonstrate their projects.
  2. Demonstrate an understanding of the software as it relates to the project.
  3. Explain the various aspects of the creation of the project.
  4. Defend their choice of software for the project.
  5. Provide the Project Documentation form, properly filled out, to the judge.
  6. Answer judges’ questions about the project.

Students should be prepared to explain and demonstrate the highlights of their project in no more than 15 minutes.

Projects are evaluated by the judges to determine the best project in that category. The judges use several instruments for making their evaluation. Judges will provide each student with a feedback form listing strengths, weaknesses, and suggestions of each project. Actual scoring materials will NOT be released.  The rubric is not the final evaluation instrument but simply a guide for the judging process.

Click here for self evaluation rubrics that can be used to find strengths and weaknesses of a project. Judges will NOT base final scores solely on these rubrics. They are guidelines only.