Hack Indiana Heads to the Statehouse
#INCapitolHack, the first installment of the 2016 Hack Indiana Series, pits developers, coders and designers against challenges from state government agencies to hack for the greater good.
The Challenge is open to individuals, teams of individuals and entities (corporations, LLCs, etc.) (each, a “Participant”). Participation by a minor (as determined under the laws of the state of Indiana) requires the written consent of the minor’s parent or guardian. The minor must be accompanied by the minor’s parent or guardian throughout the duration of the hackathon on February 26-27, 2016. If the Participant consists of a one person team, that individual must be a resident of Indiana. If the Participant is a team, at least one team member must be a resident of Indiana. The team is responsible for deciding ownership interests, licensing rights, and prize distributions among its members. None of the Challenge Entities (defined below) will become involved in any dispute with an entity and its team members, and if a dispute cannot be resolved among team members and the entity, the App will be disqualified. Each Challenge is limited to five (5) teams competing with a limit of 5 participants per team. In the event that participation would exceed twenty (20) teams, GICC and the Sponsors will increase the cap limit per Challenge incrementally six (6) teams, seven (7) teams, etc. until all participants are included. Any entity participating in the Challenge must be qualified to do business in Indiana. All non-publicly-traded entities must be owned solely by legal residents of the United States. The Administrator may refuse to consider an App in their sole discretion. No employee, officer, director, agent or owner of GICC (including its affiliates), Judges, or an immediate family member (parent, sibling, spouse child) or a household member of a GICC, Judge, officer, director or owner may participate in the Challenge. Employees of GICC and The State of Indiana (the “Organizations”) who have had any involvement in the design of the Challenge or development of the Problems may not participate in the Challenge, and neither may members of his / her immediate family or household.
How to enter
State of Indiana
Addressing the Challenge (50%)
Demo should be able to show how the solution meets (or will meet the objective). Some, but not all functionality, may be present in the prototype; but, the demo should show how the solution solves the main problem.
Creativity and Innovation (25%)
How creative or unique the solution is to meeting the objective.
Feasibility and Sustainability (15%)
The demo should be able to describe how it can be sustained over time. Look for ease of support, maintenance...use of open source/public resources, what would a potential install or roll-out look like.
Accomplishment and Learning (10%)
How much did the team learn from the customers/SME's to inform the solution, how nuanced is the solution, how many details from the customers are included?