Equity Hackathon 2nd Edition

There will be three rounds of judging

1. Idea Submission Phase

This will be based on the following criteria

• Innovativeness of the idea - How unique/creative is the concept of the product or the solution?
  • Originality of solution
  • How uniquely it address the identified problem statement
  • The creativity of the solution (the UI/UX component)
  • How realistic is the solution to be implemented
• The solution statement
  • Completeness of the solution statement; Background information of the solution has been provided, Objectives of the solution, Justification of the solution, Description of the solution
  • Is the solution statement coherent?
  • Has solution statement shown understanding of the problem statement?

1. Technical Phase

This will be based on the following criteria

• Project Completeness - Is the project or solution complete?
  • Is the system able to be used as is or any adjustments needed?
  • Whether there are any errors when running the system
  • security features
  • Usability of the system (ease of use, learn, experiment with)
  • Integration of components of the system? Are they fully integrated and the completeness of the integration?
• Functionality - How well does the product or solution work in terms of its claimed functionality? Has the design addressed interoperability adequately?
  • All objectives in the solution provided (prototype) as per solution statement have been met
  • Has final solution (prototype) addressed the need
  • Viability of the solution
  • Adequacy of the design and style of the system
  • Use of Azure Microsoft Platform
• Technical Documentation
  • Tech Stack - Is a tech stack diagram included? Is the diagram conceptually well laid out? Are the specific name/brand of technology/programming languages well described?
  • Portability - Is there an adequate explanation of what components can be swapped for other alternatives
  • Scalability - Is there an adequate explanation of how scale may be achieved? Is there specific mention of vertical vs horizontal scaling
• Project Quality - The objective of project hygiene is to achieve easily readable, understandable and maintainable code for the people who will be in charge of correcting errors, extending functionality, training and other forms of maintenance. Common tenets to observe:
  • Clear and consistent structure - design and arrangement of program features such as classes, functions, scripts, data stores and other elements
  • Naming - Use of meaningful and sensible naming conventions, preferable widely accepted conventions for the language and platform chosen
  • Use of abstractions (design) - Design elements should be clearly evident in implementations. This ensures that ideas can be transplanted with ease from one technology to another
  • Documentation - Clear documentation should be provided such that a person who reads it should be able to understand and explain what the project to another person
  • Team work & Collaboration - Team work is important. Team discussions, team decisions, architecture decisions should be documented to capture a history and justifications for decisions taken
  • Source control - work from a central repository, using accepted standards for adding or modifying features such as peer reviewing, discussions and approvals - This is a minimum requirement
  • Testing - Testing is an important part of development (as part of checking functional compliance and quality assurance).

1. Final Judging Phase

This will be based on the following criteria

• Innovation
  • How unique/creative is the concept of the product or the solution?
• Technical Implementation
  • How effective is the technical approach and implementation of the product or solution on the software?
• Functionality
  • How well does the product or solution work in terms of its claimed functionality?
• CX - Customer Experience
  • What is the overall customer experience using the product or solution
• Alignment with Challenge
  • How well does the product or solution line up with the hackathon challenge?
• Presentation
  • Was the presentation organized and engaging?

 Did the presenters properly identify the problem that they are trying to solve and clearly articulate the way their product or solution addresses the problem?