Download Mini-Jam Overview

EcoD Hackathon Guidebook
Table of Contents
Overview …………………………………………………………………………………………Page 1
What is Hackathon?
Types
What/who is involved?
Conducting the Hackathon……………………………………………………………………Page 2
Timeline
Sample Agenda
After the Hackathon……………………………………………………………………………Page 5
Summarize results
Appendix …………………………………………………………………………………………Page 6
Templates & Tools
1
Overview
What is it?
A hackathon has NOTHING to do with "hacking" or breaking into existing systems to expose and/or exploit
vulnerabilities. This is a common misconception among non-developers. A hackathon is a FUN and INNOVATIVE
opportunity for developers (i.e. Student / Developers, Start-Up / Developers) to come together and build really
awesome applications.
For the most part, apps created during a hackathon can be cross environment, i.e., running in the cloud and on a
mobile or wearable device, and often hosted on a cloud environments (i.e., like Bluemix). Users are usually provided
free trials and use this access for the event and the solutions remain the property of the participants.
Are there different types of Hackathons?
Hackathons can be audience, technology and ownership.
What’s involved? Ownership vs Sponsorship
Sponsorship or being part of someone else’s event - Many 3rd party hackathons are Friday
evening through weekend events (so as not to interfere with work). Partnering with a technical
conference in your area to partner is a great way to market it, and maximize the pool of developers to
recruit from. There is usually a “Sponsorship fee” and the Owner handles many of the logistics
(location, physical infrastructure, security, food, registration, promotion, submissions, etc.).
Ownership - Planning your own – Includes everything from a sponsored event, plus you are now
responsible for the overarching themes, infrastructure, promotion, registrations, submissions, etc.
o Decision whether if this is physical or virtual event
 Physical events: Meeting space must be reserved – stakeholder ensures participants
show and assigns judges. Who is providing the food and prizes
 Virtual events also require logistics (SmartCloud Meetings, urls, dedicated people
assigned with forums manned, etc. )
With either event - avoid holiday weekends and the periods around them.
Who is Involved?
For a successful hackathon 3 roles should be identified.
1. Hackathon Owner or Sponsor - Ultimate go-to person to lead the hackathon and coordinate
2. Marketing – allocate budget, organize team, identify Evangelist(s) (IBM skilled but not hands on),
coordinate prizes, social invitations, onsite setup/running of IBM exhibit, manage SWAG, summarize
event, etc.
3. Technical– prevent techtalk, present for the event's duration, help developers decide to use Bluemix,
help developers start/port with Bluemix, answers HOW TO questions from developers, use his/her
device to show Bluemix, lead for communicating with Bluemix support team, judges, capture
requirements and technical feedback, etc.
Roles can be combined, but it is imperative the technical role has a similar background to the developers.
Answering “How To” questions and providing support from a developer’s PoV is critical.
Back to top
2
Conducting the Hackathon
Here's a suggested timeline for engaging sponsors, leaders, and contacts. The timeline could be
compressed, but the activities need to take place with enough time
8 weeks
–
7 weeks
–
Kickoff (Owner)
 Work should begin 2 months before the planned date. This will provide you plenty of
time to arrange logistics and promote your event.
MOST IMPORTANT – decide the objective/ goal / theme – Everything should drive towards these
 Identify Team members / establish planning calls
–
–
–
Determine your budget (Owner)
 Which organization is funding?
– Travel and Living expenses, SWAG, prizes, sponsorships
Create / Use measurable snip urls for registration to Bluemix and register with Bluemix wiki
(Marketing)
Place Event into Bluemix calendar, EcoD geo calendar
Create Participant Starter Kit (Owner/Marketing)
– What is Bluemix, Examples relevant to audience, Judging criteria (rubric)
– Signup form (only if owned hackathon),
– Use mainstream Bluemix forum(s) for questions, reviews
– Provide digital FAQ
 Example “Starter Kit” for Bluemix at http://ibm.biz/LearnBluemix and
http://hackathons.mybluemix.net/
7 weeks
–
If this is an on-site (face to face) hackathon, you must verify availability. (Owner/Marketing)
(Only for Owned Hackathons)
 Pick a date and location (Owner/Marketing)
 Choose the location that is large enough all of the attendees
 Find a large room with seating and a projector for kickoff, demos, and awards.
 Identify break-out rooms for the participants
 Determine infrastructure availability
– Sufficient power, internet bandwidth, chairs, tables, and whiteboards
 Begin scheduling catering
 Determine food requirements
6 weeks
–
Identify technical person(s) and evangelist(s) supporting
 recommend 3 technical expert / 50 developers who attend / 8 hours (not total
participants, but expected users of IBM technology or services) (Technical)
 recommend 1-3 Evangelist(s) who attend as needed for shifts (Marketing)

Verify Bluemix and related services infrastructure, supporting platform will be up (technical)
Verify product support team will be available (technical)
Complete Event Brief, Contracts and Logo Agreement process (Marketing)
 When complete, provide IBM logo and IBM Bluemix TShirt logo to Hackathon
interface (Marketing)
 Document Hackathon branding and sponsorship opportunities (Marketing)
–
–
–
4 weeks
–
Have a place where participants can learn about event and sign up. (Marketing) (only if
Owned event)
o Logistics: Create a simple one-page site
– When, where, who is invited, and a link to a signup form.
3
–
–
–
–
–
–
–
3 weeks
2 weeks
1 week
–
Hold call with Hackathon Event Interface (Owner)
with IBM Marketing lead and Technical lead
–
Create the submission page when apps are submitted (technical role) (Only for Owned
Event)
o Name, email, app name, description, technologies used
o BlueMix submission sample
https://www.surveygizmo.com/s3/1787626/appSubmission
o If accepting code, apps, videos, determine how to capture
–
–
–
Verify event feedback form is ready (marketing role)
Host event Planning call (Owner)
Host “Get Ready Call” (technical role)
o Explain to developers enrollment process
o Review the challenge, judging criteria, and prizes
 Example for Bluemix (link)
Prepare 5 minute quick pitch to participants
Update audience with social promotion and IBM exhibit deliverables (marketing role)
Start Social posts (Technical and Evangelist)
Host event Planning call (Owner) with IBMers and invite Hackathon Event Interface
Verify detailed event agenda and IBMers shift Schedule
Repeat if need “get ready call” (technical role)
Verify judges and review rubric for judging submissions
Verify Hackathon Event Interface has everything they need (Owner)
Continue Social posts (Technical and Evangelist)
–
–
–
–
–
–
–
–
1 day before/day
of event
You can also utilize EventBrite.com as they provide all the tools, e.g., way to
pay for tickets)
o Build Event Drive to plan :
– DevComm (existing IBM ISV partners)
– CCDb (existing IBM resellers)
– Social Promotion (IBM Communities, Linked-In, etc.)
– Create prepared social communication (templates for pre-event, day of and
post event – tweets, blog posts)
Host event Planning call (Owner)
Identify onsite materials and giveways (Marketing)_
o Online visitibility consistent with event (i.e. website, Learning site, Facebook, Twitter)
o Postcards, Flyers, Banners, Tablecloth, Monitor
o Identify giveaways
– Bluemix stickers, inexpensive giveaways
– Determine shipping logistics (ship to address, name, email, phone, storage)
– Consolidate speakers bios and provide to sponsor
– Identify judges
o Review “Get Ready Call” material
Review the data sets/API’s that will be provided
Document and make available examples that help Developers use other Sponsors’ APIs with
Bluemix (Technical)
Provide Speaker picture and Bio to Marketing lead (Technical)
Document other Sponsors and their prizes (Technical)
Arrive on-site and setup (marketing/technical role)
 Table setup; IBM tablecloth, monitor; demo devices, banners, flyers, SWAG items
 Interact with Hackers at exhibit, at their workspaces and in common areas, at
opening/final ceremonies, at Expo), Internships/Jobs, AmbassorU program, Students for
4
–
–
–
Post event
a Smarter Planet program, etc.
 Be Social, especially tweets with pictures of Hackathon excitement
 Communicate with Bluemix and related services support teams as needed (Technical)
Promote winners (blog posts, tweets, etc.)
Certificates for winners
Communicate Requirements and Feedback
Back to top
During the Hackathon
Suggested 2 day business hour agenda (on-site) (Only for Owned Hackathons)



Kickoff (Day 1 - 9AM to 10AM)
o Breakfast (you decide who pays)
o Introduction (Customer and/or IBM rep, food and lunch logistics)
o Technical Introduction (Technical expert)
 Explanation of the Goal/Purpose (Technical expert or Customer rep)





Demos relating to objective (Technical expert)
Check in (Noon)
o Check into Starterkit specifying (name, email, app name)
o Lunch
Compete (Day 1 - 10AM to 5PM (or later) / Day 2 - 9AM to 2PM)
o Developers build their apps during these times
o
o

Distribute contest judging criteria and how to submit applications for consideration (Technical expert or Customer rep)
Talk about the prizes (Technical expert or Customer rep)
Technical support availability/logistics (Technical expert)
o
o
 Devs can pair up or work alone, doesn't matter
Lunch, dinner provided to developers (you decide who pays)
Assistance provided throughout the day by IBM technical expert(s)
 The need for "breakout sessions" may arise
Developers submit their completed app URLs, "30 second elevator pitches," and complete the feedback online form
Social Collaboration during event (Marketing role)
Expo! (Day 2 - 2PM to 3PM)
o Developers set up at tables throughout the space and demo their applications in a casual, "science fair" like setting
o The judges in the room walk around and see each app
 Score based on defined criteria (you must provide Day 1)
o Judges who are not in-person will review the apps submitted to the online form.
 Use mobile application for scoring (insert link)
Deliberation/Drinks/Winners Announced (Day 2 - 3PM to 5PM)
o Judges (in-person and remote) deliberate on the apps created and pick a set of winners (typically 1st, 2nd, 3rd place) - this can be done over the
phone
o Food and drinks for attendees during/after this deliberation
o Winners announced at 4pm, judges join in the food/drink fun
Back to top
After the Hackathon
5
Consolidate Survey information from Event tool (i.e. ChallengePost) and/or survey tool (Owner/Marketing)
Standard statistics – people/Apps.
Description of apps were created.
Collect email address
Send Thank you letters
Track follow-on requests (Owner/technical)
Back to top
6
Templates & Tools to Conduct a Hackathon
Learning Bluemix and answering FAQ: http://ibm.biz/LearnBluemix
Coremetrics measured url for Bluemix registration: http://ibm.biz/HackBluemix
Back to top
7