Skip to content

Latest commit

 

History

History
109 lines (97 loc) · 7.93 KB

lit_summary2.md

File metadata and controls

109 lines (97 loc) · 7.93 KB

hackathon variation

  • one-off [[Correia, 2015 #4578]] or series [[Katayama, 2010 #4521; Katayama, 2011 #4523; Katayama, 2013 #4524; Katayama, 2014 #4522]]
  • short or long
    • 5-day hackathon on scientific software [[Christopherson, 2013 #4574]][[Lapp, 2007 #233]]
  • community-corporate-internal distinction [[Kuchinskas, 2014 #4584]]
  • size
    • small events with 20+ participants [[Moller, 2014 #4512]]
  • in-house [[Burnham, 2012 #4579]] or not
  • off-site "travel" event vs commute [[Raatikainen, 2013 #4571]]
  • prizes for deliverables [[Fafalios, 2014 #4537]] or downstream support for promising projects [[Burnham, 2012 #4579]][[Souza, 2013 #4573]][[Hecht, 2014 #4582]]
  • interdisciplinarity
    • diverse: civically oriented big data hackathon at google London [[Souza, 2013 #4573]]
    • not: e.g.,

diversity of topics

  • healthcare informatics [[DePasse, 2014 #4507]]
  • medical education hackathon [[Aungst, 2015 #4506]]
  • use of hackathons in cities to promote open data [[Almirall, 2014 #4533]]
  • data hackathons
    • use of hackathons in cities to promote open data [[Almirall, 2014 #4533]]
    • ebola data [[HackEbola_with_Data, 2015 #4583]]
  • maker event in India [[Hecht, 2014 #4582]]
  • design maker event wearables [[Richard, 2015 #4572]]
  • toolbox interoperability theme [[Moller, 2014 #4512]]

hackathon process, tools and appraoches

  • theme, targets, scope

    • use-case-driven approach, prior planning [[Lapp, 2007 #233]] [[Vos, 2014 #4508]]
    • importance of well defined problem that is communicated effectively to participants [[Mohajer Soltani, 2014 #4580]]
    • balance learning objective with providing value to humanitarian sponsor ("Balancing student benefit and social impact") [[Linnell, 2014 #4568]]
    • pre-specified targets (ideas, not requirements) [[Raatikainen, 2013 #4571]]

  • team formation and project choice

    • social nature of team-formation process [[Jones, 2015 #4585]]
    • managed student projects [[Hecht, 2014 #4582]]
    • brief pitches followed by open-space-like team coalescence [[Mulholland, 2015 #4543]]
    • conscious choices of teams to learn a new technology [[Mtsweni, 2015 #4566]]
    • pre-specified teams [[Raatikainen, 2013 #4571]]
    • comparison of 3 methods [[Trainer, 2014 #4504]]

  • pre-event engagement [[Correia, 2015 #4578; Hecht, 2014 #4582; Vos, 2014 #4508]]

    • importance of well defined problem that is communicated effectively to participants [[Mohajer Soltani, 2014 #4580]]
    • importance of pre-event engagement, particularly group consensus on objectives and familiarity with problem area [[Christopherson, 2013 #4574]]
    • organizers run one successful even based on 2 months of preparation, then a much less successful event due to less preparation [[Christopherson, 2013 #4574]]
    • importance of preparation [[Trainer, 2014 #4504]]
    • pre-event engagement with github [[Trainer, 2014 #4504]]

  • shared technology

    • general importance of shared technology for event [[Correia, 2015 #4578]]
    • use of github (code, collaboration, communication) [[Correia, 2015 #4578]]

  • participants

    • mixing of different levels of expertise and career stages beneficial for junior participants [[Busby, 2015 #4577]]
    • importance of diversity in participant competences [[Mohajer Soltani, 2014 #4580]]
    • bringing together international participants [[Moller, 2014 #4512]]
    • mixing levels of expertise, career stages, mentoring opportunities; [[Mtsweni, 2015 #4566]]
    • open to participants with and without technical expertise [[Zapico, 2013 #4550]]
    • "invested participation" [[Briscoe, 2014 #4581]]

  • social nature of event

    • social nature of team-formation process [[Jones, 2015 #4585]]
    • The "social-physical-corporeal aspect of these types of events", building community, briding disciplines, citing Coleman, Moilanen and Pargman [[Zapico, 2013 #4550]]
    • some participants were not comfortable asking for help [[Trainer, 2014 #4504]]
    • idea that hackathons are about prototyping relationships (see notes) [[Briscoe, 2014 #4581]]
    • mentioning social benefits, collaboration, motivation [[Raatikainen, 2013 #4571]]
    • even in an internal hackathon, team members may not have worked together before [[Raatikainen, 2013 #4571]]
    • detailed examples of how the hackathon environment leads to interactions that aid in team-formation, social ties, and long-term collaborations [[Trainer, 2014 #4504]]

value points

  • motivation [[Raatikainen, 2013 #4571]]
  • learning
    • balance learning objective with providing value to humanitarian sponsor ("Balancing student benefit and social impact") [[Linnell, 2014 #4568]]
    • explicit focus on providing learning experiences for students [[Linnell, 2014 #4568]]
    • survey showing top 2 reasons for participation are "learning" and "networking" [[Briscoe, 2014 #4581]]
  • generating excitement [[Mulholland, 2015 #4543]]
  • "Sixty percent of the projects from the hacks held in December, February and March have already shipped internally or to Facebook users." [[Burnham, 2012 #4579]]
  • "Mastodon C" prototype chosen for funding after hackathon and the app was being developed further as a start-up company [I think actually the start-up is "agile big data" and is much broader than one app: see http://www.mastodonc.com/]. [[Zapico, 2013 #4550]]
  • detailed examples of how the hackathon environment leads to interactions that aid in team-formation, social ties, and long-term collaborations [[Trainer, 2014 #4504]]

Diversity stuff

outcomes, followups, downstream stuff

  • follow-up program to build on successful projects [[Hecht, 2014 #4582]]
  • downstream excitement and continuing effort after hackathon ends [[Busby, 2015 #4577]]
  • example of outcomes from hackathons taken further to (at least) separate publication [[Fafalios, 2014 #4537]]
  • familiar complaint about not enough products [[Knight_Foundation, 2012 #4575]]

points about studying or analyzing hackathons

  • possible candidate to show the risk of entropy and bit rot when tangible outcomes aren't tracked and recorded explicitly [[Davies, 2014 #4538]]
  • structured thinking about how to make hackathons work [[DePasse, 2014 #4507]][[Groen, 2015 #4531]]
  • superficial analysis of 6 factors that may be important in a set of 6 hackathons [[Mohajer Soltani, 2014 #4580]]
  • sample survey questions [[Trainer, 2014 #4504]]
  • origin and history of hackathons, jams, LAN parties [[Briscoe, 2014 #4581]]
  • possible ways to assess intangible impacts (stories of value creation)[[Wenger, 2011 #4526]]

Miscellaneous

  • costs of remote participation (extra time, lossy communication, lack of in-person dynamics like whiteboarding or looking over a shoulder) [[Christopherson, 2013 #4574]]
  • tradition in bioinformatics-- see quotation about historical importance [[Moller, 2014 #4512]]
  • available online guidance [[McArthur, 2012 #4569; Murby, 2014 #4548]]
  • the importance of a "trusted hub". [[Souza, 2013 #4573]]
  • political perspective on hackathons as manifestations of "entrepreneurial citizenship" in an Indian context. [[Irani, 2015 #4541]]
  • the "civic hackathon", which is basically government awarding hackathon projects prize money for outcomes that "deliver services to citizens" [[Johnson, 2014 #4540]]