Why this hackathon project is still growing 18 months later - Technical.ly Philly

Civic

May 9, 2014 12:30 pm

Why this hackathon project is still growing 18 months later

Instead of fizzling out and losing steam after the hackathon ended, like most projects do, the team continued to work on greenSTEM for a year and a half, up until it was ready to ship. Here's why and what other hackathon participants might learn from it.

greenSTEM Network team members Matthew Fritch (far left) and Kevin Clough (center) at a May 2014 Code for Philly night.

Full disclosure: Several events referenced in this story were organized by Technical.ly Philly. This reporter was not part of those efforts, and they are specifically highlighted in the article text.

greenSTEM Network, a soil-monitoring kit designed to teach students about STEM, started like many other hackathon projects do. Someone had an idea, pitched it at a hackathon and found a team of developers to work on it.

But instead of fizzling out and losing steam after the hackathon ended, like most projects do, the team continued to work on greenSTEM for a year and a half, up until it was ready to ship. Matthew Fritch, the Water Department environmental engineer who originally presented the idea at the February 2013 TechCamp hackathon, which, full disclosure, Technical.ly Philly organized with the U.S. State Department and dev firm Jarvus, plans to install the kits at four public schools next week.

So what made greenSTEM different?

Ignoring the hackathon deadline, for one. Hackathons normally end on a Sunday afternoon with a demo session, with participants presenting their work and judges choosing a winner. But the greenSTEM team didn’t have a finished product to present the Sunday that TechCamp ended and that was fine by them, said developer and team member Kevin Clough.

It also helped that Christian Kunkel, a Jarvus team member who helped organize the hackathon, stressed that participants didn’t need to complete a project by the end of the weekend: they could keep working on it at the weekly Code for Philly hack nights that Kunkel’s team help organize. (The idea of a ‘Finish-athon’ has been touted before as a way to keep hack projects living.)

And that was exactly what the greenSTEM team did. At Tuesday’s Code for Philly night, the greenSTEM team was still hard at work. Fritch said he spent the night “battling with a Raspberry Pi,” which the team is working to configure so that students can use the single-board computer without any setup required.

We spoke to the greenSTEM team to find out why else the project lived past the hackathon, and here’s what they said. Also, see the greenSTEM team present at Indy Hall’s Show and Tell this Thursday.

Advertisement

  • While most hackathon projects are run by volunteers, greenSTEM was unique because Fritch was able to make it part of his job. (He now teaches a class at Science Leadership Academy, which builds on his involvement with the project.) Later, when greenSTEM secured funding for the project, some of that money went toward paying team member Christopher Nies and Jarv.us, the web dev company where Clough works, to work on it.
  • The money was never a driving point, the developers said. There was no expectation that there would be money behind greenSTEM when they first started working on it. Still, the money helped, especially because it was a hardware project and there are equipment costs associated with that, Nies said.
  • greenSTEM had several opportunities to keep working on the project, like at the April 2013 AT&T Edutech Hackathon and weekly Code for Philly meetups. They also got to present their work at Philly Tech Week’s Switch Philly, where they won second place. (Full disclosure: Technical.ly Philly also organized both the Edutech hackathon and Switch Philly.)
  • A word of advice to hackathon teams: don’t take it personally when team members drop out or lose interest, Nies said. There was one point when the greenSTEM team was nearly a dozen people strong. Today, it’s a team of three.
-30-
VIEW COMMENTS
  • Sean Dawes

    Think your last point is something more teams and companies need to realize. Not everyone is cut out for building something but a lot of people want to be part of a success story. Execution is what separates those who will succeed and those who will step aside because they can’t cut it. Just gotta keep rolling with the punches as people come and go and stay focused on executing and the end goal.

Advertisement

Read this rundown of Philly’s civic-tech all-stars

Tinker with LoRaWAN systems at HackIoT Philly

Code for America’s time is now

SPONSORED

Philly

Vistar Media’s tech stack is not for the faint-of-heart

Chesterbrook

Deacom

Inside Sales Representative

Apply Now
Center City, Philadelphia

IntegriChain

Senior Business Analyst

Apply Now
Philadelphia, PA

IntegriChain

Senior Data Engineer

Apply Now

Saturday: See final projects from the Code4PA Hackathon

Next week: Hack for good at GiveBackHack

Code for freedom at the upcoming Reentry Project hackathon

SPONSORED

Philly

MakeOffices’ new location is ripe for startup collaborations

Chesterbrook, PA

Deacom

Enterprise Software Sales Representative

Apply Now
Philadelphia

Azavea

Software Engineer, Geospatial Insights Team

Apply Now
Philadelphia

Clarivate Analytics

Senior UI Developer

Apply Now

Sign-up for regular updates from Technical.ly

Do NOT follow this link or you will be banned from the site!