We have broken down the hackathon in six distinct phases. Typically these phases run in parallel and overlap, as opposed to working consecutively. As a hackathon organiser, you will be playing chess on multiple boards, creating a funnel towards the actual hackathon.
Below you can find the 6 life-cycle phases with a short n' brief explanation.
Click on the titles to learn more.
Start out by delimiting one or multiple problems. These problems could range in scale, number, type of stakeholders involved and domain areas. Read on to learn how to recognize hackathon-suitable problems, the need for focus and how to distill relevant sub-topics as hackathon challenges.
Perform an in-depth analysis of the problem. Here we explore what the underlying questions behind a particular problem are and what feasible solutions stakeholders have considered or are considering. Read more on why we typically organize a pre-event for this stage.
Pin-point all the concerning stakeholders of your problem. The impact and longevity of the outcomes of your hackathon critically depends on the participation of key stakeholders in the ecosystem, just as the topic and agenda of the event. Read more on who is who and how to identify the ideal challenges in the dedicated section.
Commit people to your hackathon. This phase will put any event organiser to the test. Lesson learned by FarmHack: choose quality over quantity. Learn more on how to curate for teams with a fine balance between problem owners, stakeholders, domain experts and free ‘tech savy’ agents that will spice up your event.
The actual hackathon, where the magic happens! Every hackathon is an original, you can tailor it to any circumstance. Read more to find out how you secure sweet hackathon results, that make this format stand out from your average brainstorm or pressure cooker session.
The afterparty. Build partnerships on top of the hack results. After approx. 30 hours of collaboration and coding, results are still very early stage. How to embed results and maintain commitment, is crucial. Read more on how and why to do this.