$10K first prize to create technology that monitors the health of farm workers. Additional prizes too!

Create technology that will help monitor the health of farm workers throughout the United States.  Almost 50% of all farm workers are Hispanics - what a great way to help our agricultural community and the Latinx community at the same time!

This hackathon is sponsored by Two Sigma, Macys.com, Goldman Sachs and GE Healthcare.  It is hosted by the Society of Hispanic Professional Engineers, in collaboration with the National Latino Farmers & Ranchers Trade Association.

To get more information, go to http://www.hackathon.shpe.org 

View full rules

Eligibility

* Individuals must be 18 years and older

* Passionate about tech and the Latinx community

* Teams of 3-5 individuals

You can come as part of a team or be placed in a team upon arrival. However, all submissions must come from a team of 3-5 individuals.

Requirements

Hackathon: Wednesday, November 2nd, 2016 – Friday, November 4th, 2016

Hackathon // Background

Title: Build A Farmer’s Future
Goal: Produce software, in the form of web and/or mobile applications, that meets the needs of our four target groups: OSHA, Farm Owners, Crew Leaders, and Farm Workers.

Description:

Thank you for being part of SHPE's first-ever Hackathon at National Conference.

As the largest organization in the United States that brings together over 5,000 Latinxs in tech, we are honored to dedicate the resources and talents of our developer community to the improvement of an issue that affects many Hispanics in our country.

According to the U.S. Department of Labor National Agricultural Workers Survey, “76% of farmworkers in the United States identify as Hispanic/Latino.”  Whether migrant workers who are in the U.S. seasonally, immigrants who now live in the U.S. (documented/undocumented), or children of immigrants, the farmworker population is primarily Hispanic.

This industry has a history of abuse, neglect, and dangerous work conditions for its employees.  Given this context, we chose to focus this year's hackathon on ways to improve the health monitoring for farmworkers.

The challenge design has involved OSHA, National Latino Farmers & Ranchers Trade Association, University of California Davis, and our various sponsors.  We are excitedly anticipating what 100+ teams of developers will create.  Your solutions have true potential for creating a valuable platform to revolutionize this industry and have a direct impact in our Hispanic community.

Scope:

Occupational Safety and Health Administration (OSHA) needs to create better metrics and better identify farms that need more supervision. Data gathered can be used to improve education and training for farm personnel at all levels.

Farm Owners need a better way to consolidate/aggregate data collected daily by Crew Leaders and use it to make adjustments to their farm Illness and Injury Prevention Programs (IIPP).

Crew Leaders need a digitized way to collect data on a daily, ongoing basis to better understand and comply with OSHA regulations.  For example, they must do regular check-ups throughout the workday; ensure workers are drinking water, taking bathroom breaks, and resting.

Farm Workers need to be educated on their rights and OSHA requirements, and need an anonymous way to file a complaint

Special Considerations:

  • Immigration Status - taking into account users’ privacy concerns with regards to immigration status (i.e. being undocumented)
  • Language Diversity - being inclusive of the many languages that farm workers may speak, not limited to just English and Spanish (i.e. indigenous Mexican languages)
  • Literacy - catering to all reading levels
  • Worker Abuse - compensating for possible neglect of workers by crew leaders and/or farm owners
  • Multiple Work Environments - considering the different risks and benefits that change by farm type (i.e. citrus plants require the use of ladders but present opportunities for shade; strawberries do not require ladders but expose the workers to sun for longer periods of time

Challenge Structure:

  • The participants’ job in this challenge is to create any solution involving software that helps address the concerns of one or more of the four stakeholders
  • Software solutions can take the form of mobile apps on either an iOS or Android platform, and/or web applications to be hosted on either Linux, Windows, or Mac servers

Mentors & Judges:

Mentors will be floating throughout the hackathon space to advise participants as they hack as well as reviewing submissions via DevPost.

The mentors will be available to all teams.  Their functional expertise (UX, back end, database, specific language, security, etc.) will bring valuable insight and depth to the your projects.

Mentors will point your teams in directions that will enhance your solution.  They will ask open ended questions that will encourage and challenge you in developing an innovative solution. Mentors are not part of any team, so they will not be involved in the implementation of your application.

Judges will review and score all submissions for the hackathon and judge the participants via DevPost. They will be judging the submissions during the Qualifying and Final Rounds.

 

Hackathon // Overview

Kick-off

Time

Agenda

3:00 PM

Hackathon Team Registration & Badge Pick-Up

6:00 PM

SHPE introduces first ever Tech Program at SHPE Conference

  • Barry Cordero, Interim CEO
  • Overview of Tech Program Schedule: Tech Talks, Workshops, Theater, Hackathon
  • Introduces Qualcomm - Tech Program Sponsor

6:05 PM

Qualcomm Representative

  • Welcome Statement

6:10 PM

Jennifer Vasquez, Senior Director of Business Dev

  • Introduces Premier Hackathon Sponsor, Two Sigma

6:15 PM

Two Sigma - Premiere Sponsor Address

6:25 PM

Competition Kick-Off

7:00 PM

Meet your clients: Panel of Subject Matter Experts

  • National Latino Farmers & Ranchers Trade Association
  • OSHA
  • Farmworkers

Hackathon

Time

Agenda

Wednesday, 8:00 PM - 12:00 AM

  1. Team work begins
  2. Familiarize yourselves with guidelines, procedures and rubric
  3. Meet with mentors as needed

Thursday, 12:00 AM - 7:30 AM

  1. Prepare submissions for the qualifying round
  2. Work on your proposed system architecture
  3. Work on your expected user interface design/sketches
  4. Begin developing your application

7:30 AM - 9:00 AM: Breakfast break

 

9:00 AM - 12:00 PM

 

12:00 PM - 1:00 PM: Lunch Break

  1. “Using Software Engineering to Predict the Future” - Panel with Two Sigma

3:00 PM

Qualification Round

Follow the Submission Guidelines and submit your executive summary, system architecture and user interface design.  Failure to submit the required pieces will result in automatic disqualification.

1:00 PM - 5:00 PM

 

5:00 PM - 7:30 PM: Dinner Break

  1. SHPE Opening Ceremony

7:30 PM - 8:30 PM

  1. Qualifying teams announced

8:30 PM - 12:00 AM

 

Friday, 12:00 AM - 6:00 AM

6:00 AM

Final Submissions Due

Follow the Submission Guidelines and upload your application to DevPost. You may update your elevator pitch, architecture design, platform choice, etc as necessary.
You MUST submit a zip file with all your source code. Including the link to your GitHub repo is optional.

6:00 -7:15 AM: Breakfast Break

 

7:15 AM – 8:00 AM

  1. Mentors/Judges Deliberation
  2. Prepare for the possibility of presenting, in case of being selected as Top 8

8:00 AM - 9:00 AM

  1. Final eight teams announced
  2. Prepare for the presentations

8:50 AM

Presentations Due

 

Hackathon // Final Round

Final Round

Time

Agenda

9:00 AM

Two Sigma Welcome & Intro of Panel of Judges

9:10 AM

Team 1

  1. Set-up (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

9:20 AM

Team 2

  1. Team 2 Set-up / Sponsor Commercial (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

9:30 AM

Team 3

  1. Team 3 Set-up / Sponsor Commercial (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

9:40 AM

Team 4

  1. Team 4 Set-up /Sponsor Commercial (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

9:50 AM

Team 5

  1. Team 5 Set-up / Sponsor Commercial (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

10:00 AM

Team 6

  1. Team 6 Set-up /Sponsor Commercial (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

10:10 AM

Team 7

  1. Team 7 Set-up / Sponsor Commercial (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

10:20 AM

Team 8

  1. Team 8 Set-up / Sponsor Commercial (2 min)
  2. Presentation (4 min)
  3. Q&A (4 min)

10:30 AM

Break // Compile Scores
Meet with Judges to discuss Top 3 Winners

10:45 AM

GE

  1. Present Third Place Prize ($3K)
  2. Present Second Place Prize ($5K)

10:50 AM

  1. Com
  1. Present First Place Prize ($10K)

10:58 AM

Goldman Sachs: Closing Remarks

 

 



 

 

 

Hackathon // Submission Guidelines

QUALIFYING ROUND - THURSDAY 3pm:  Qualifying Documents (Executive Summary, Designs, Team Lead)

 

  • Executive Summary

 

  1. Participants should start working on what they want to build for their submissions. This should be a very brief summary about what the program should be able to do, how it will benefit different parties involved.
  1.   Design
  2.   Team Lead
  1. Here, teams should go into more detail about the design of the project. This should include (but is not limited to): Platform, workflow for the application, list of projected challenges, mockups, etc.
  2. This must include a mockup of the platform architecture and a mockup of the proposed user interface.  These may be sketched by hand or digitally.    
    1. Upload a PNG, GIF or JPG of your system architecture (can be informal – a hand-drawn sketch is fine)
    2. Upload a PNG, GIF or JPG with a sketch (or draft screenshot) of the expected user interface of the system you are building (again, can be informal – hand-drawn is fine)
  3. All groups should also create a list of deliverables they intend to complete by the end of each stage, and who will own each task (see below)
  1. Team Lead: The main liaison for the group to the mentors, judges, and sponsors. Please identify this person and notify Francesca with the name and email of your team lead.
  2. Based on the skillset and interests of the group, there should be a clear owner for each area of the process.













 

 

 

Hackathon // Scoring

 

Qualification Round

5

4

3

2

1

Implementation

Summary clearly defines the problem and approach, strongly addresses challenges expected in implementation, strong technical components, confident will be completed and implemented in the given time period.

Summary defines the problem and approach, addresses some challenges expected in implementation identified, moderate technical components, idea seems viable to complete in given time period.

Summary clearly defines the problem and approach, addresses some challenges expected in implementation, standard technical components, idea seems viable to complete in given time period.

Summary defines the problem and approach, addresses no challenges expected in implementation, poor choice of technical components, idea does not seem viable to complete in given time period.

Summary does not clearly define the problem or approach, addresses no challenges expected in implementation, poor choice of  technical components, idea does not seem viable to complete in given time period.

Functionality

The idea seems extremely feasible and viable with a high probability of success.

The idea seems reasonably feasible and viable with a fair level of potential for  success.

The idea seems moderate, and has a good probability of success.

The idea might be feasible and viable, but the probability of success could be higher.

The idea might not be feasible and viable, and has a rather low probability of success.

Technical Difficulty

Design of application is very user friendly.

Application is strongly designed and features implemented have a realistic application.

Solution was creative and addressed most of the special considerations.

Design of application is user friendly.

Application has good design. At least one functional feature, others near implemented with realistic application.

Solution was creative and addressed most of the special considerations.

Application has satisfactory design.

Most features are incomplete in implementation, but given some time, would be good and relevant.

Most features are incomplete in implementation, but given a significant amount of time and resources, could be good and relevant.

Design of application is poor and incomplete in implementation.

 

 

Hackathon // Qualification Round, Submission Instructions

  1.      Go to devpost.com.  On the top menu, click Hackathons and search for Build A Farmer’s Future.

 

  1. On the top right corner, click the green/teal button to submit your work
  2. Enter a title, an elevator pitch, and your team members.  The “It’s Built With” field is optional.
  3. In the “Here’s The Whole Story” section, indicate what type of solution you are building (web app, mobile app, or something else) and enter your executive summary, design/features, and roles as described in the Submission Guidelines above.
  4. Leave the “Try It Out” field blank.
  5. Scroll to the bottom of the page and click Save.

 

 

 

 

 

FINAL ROUND - FRIDAY 6am Submission Guidelines:  

 

Your code will be evaluated on implementation, functionality, and technical difficulty as outlined in the rubric above.  You must submit your source code via devpost.com using the following instructions:

  1. On the top right corner, click the green button to edit your previous submission to Build A Farmer’s Future
  1. Scroll through the page.  Make all necessary edits to your existing submission.  If your architecture or designs changed, make note of that or edit the text to reflect the changes in your software.
  2. At the bottom of the page, in the Image Gallery section, click “Choose Files” to select the appropriate zip file to upload.  All of your source code should be put in a zip file and uploaded with your submission.  In the Try It Out field, you can share a link to your GitHub repository (this is optional). If you use a github repository, you still need to upload a .zip file, else you will be disqualified.
  1. Scroll to the bottom of the page and click Save.

 

 

PRESENTATIONS: FRIDAY 9am - Top 8 Teams Final Presentation Guidelines
Your final presentation will be evaluation according to the rubric below.  Please note that the audience, in addition to the panel of judges, will also be voting for their favorite presentations.

Final Presentations

5

4

3

2

1

Presentation

Presentation is clearly and logically organized.

The message has a highly impactful introduction; clear content and transitions; and demonstrates strong technical expertise. Claims are always supported by solid, compelling evidence (both quantitative and qualitative).

Presentation is clearly and logically organized.

The message is clearly stated but could be better highlighted; clear content and transitions; and demonstrates strong technical expertise.

Most claims are supported by solid, compelling evidence (both quantitative and qualitative).

The presentation has a coherent structure but the introduction and /or the conclusion could be more impactful.

The message is clearly stated but could be better highlighted; clear content and transitions; and demonstrates fair technical expertise.

Some claims are supported by solid, compelling evidence (both quantitative and qualitative).

The presentation is not well organized and lacks overall coherence and cohesion, which means that key ideas remain unclear. There may not be a clear introduction and / or conclusion. Claims may not be substantiated by suitable evidence.

The presentation is fragmented. It lacks any clear structure and overall sense of coherence, which makes it difficult to follow. There may not be an introduction and / or conclusion. Claims are unclear and, in the main, unsubstantiated.

Presentation (4 minutes)

  • Summary
    • Team: Quick introduction of everyone involved
    • Who was this developed for
    • What was the problem & your solution
  • Demo
    • Demonstrate the features that work
    • Talk about the platform and design strategy used
  • Next Steps
    • Talk about future features you could implement if given enough time
    • Talk about the challenges you might face
    • Talk about the impact your application could have

Q&A (4 minutes)

  • The judges and audience will have time to ask you questions about your application and the process.

Prizes

  • First Place - $10,000 (Macys.com sponsored)
  • Second Place - $5,000 (GE sponsored)
  • Third Place - $5,000 (GE sponsored)
  • Runner Ups - Students will receive the Github Student Developer Pack which gives you a 1-year personal subscription. Professionals will receive 1-year of unlimited private repositories.

 

How to enter

A. You MUST bring a resume with you to the hackathon. B. Go to this link and register your team.  ONE SUBMISSION PER TEAM, please. C. Create ONE devpost.com account for your team and sign up for the Build A Farmer's Future hackathon. D. If you plan to use GitHub for your repository, here is that information: STUDENTS - you can get free individual Student Developer Pack at: https://education.github.com/pack PROFESSIONALS - you can get one month of unlimited private repositories for an individual using the code hackathon-30f3187 E. You MUST donate your code to open source.  Read the GNU General Public License Version 3 (GPL-3.0). Scroll to the bottom of that document, and make sure you insert the appropriate wording into your source code.   ADDITIONAL GITHUB RESOURCES: https://services.github.com/resources/ https://guides.github.com/   If you will not be present on Wednesday night for the kick off, we will be emailing you a link to the live streaming of the kick-off session.  We require that, if you are not present, you watch the two sessions as they will have all the information to get you and your team started.  If you cannot watch it live, a recording will be available, and you must watch it before starting your project.

Judges

Francesca Escoto

Francesca Escoto

No avatar 100

Heidy Arriola

Leonardo Marcovitz

Leonardo Marcovitz

Joy Ekuta

Joy Ekuta
Two Sigma

No avatar 100

Rob Fuentes
Goldman Sachs

Mark Roth

Mark Roth
Two Sigma

Aisha Lews

Aisha Lews
CODE2040

No avatar 100

Rigo Rios
National Latino Farmers & Ranchers Trade Assn

No avatar 100

David Ortiz
Emortal Sports

No avatar 100

Hector Medina
Macys.com

Ed Montenegro

Ed Montenegro

Alfredo Ruvalcaba
Qualcomm

Joy Ekuta

Joy Ekuta
Two Sigma

Judging Criteria

  • Functionality
    Practicality / utility of the application. Strongly supported by target group experts that this could solve at least one of the challenges and special considerations.
  • Implementation
    Overall user experience, creativity, teamwork, and features implemented during the hackathon.
  • Technical Difficulty
    Design of application is user friendly. Application was well designed and features implemented have a realistic application. Solution was creative and addresses the special considerations for your selected target users.