Knowledge Baltic Museums Knowledge Baltic Museums

  • Home
  • Knowledge Base
  • People
  • FAQ
  • Project Info
  • Contact
Home / Hackathon in Museums / Hackathon in Museums – Recommendations Infrastructure

Hackathon in Museums – Recommendations Infrastructure

1225 views 3 min , 11 sec read 5

Author: Susanne Marx, Aug 2019

1.   Recommendations – Infrastructure

1.1.               Venue

If hosted by one museum only, most recommendable is to host the hackathon in the organizing institution, so the teams can experience the exhibition, watch real visitors and get thus inspiration. If hosted by several museums, a facility complying with the basic requirements is recommended.

 

1.1.1.            Basic requirements

  • All participants should work in one room. It is beneficial for the atmosphere and for networking. It would be good have extra rooms for teams to work in more quiet atmosphere, however, only bookable for a certain amount of time.
  • All meetings, catering, work etc. should be done in one building. Rooms with daylight are preferable.
  • Some food should be allowed in the main working room (snacks, coffee etc.).
  • Bathrooms: adequate number of toilets, even shower if possible
  • Rooms:
    • Hacking: large tables with seats for about 5-6 people, have comfortable seats or gymnastic balls
    • Opening/closing ceremony: classroom-style seating or cinema-style
    • Sleeping room (warm), matrasses would be good, but is not standard, participants bring sleeping gear
    • Preferably a separate chill room
    • Eat room/space
    • Room for meetings with mentors
  • Access: check for wheelchair friendliness and accessibility even outside working hours
  • Security: Check for security, so that participants can leave their belongings in the room including laptops

1.1.2.            Equipment

WiFi needs to fulfill high demands and depends on the number of participants. In order to provide the participants with redundant multiple simultaneous internet connection, the organizers should have the equipment supporting more computers and other devices than the participating ones, as the demand for the bandwidth was tremendous in our experience.

  • Electricity for many computers in one room, Power strip for each table with multiple plugs
  • Projector
  • Microphone for large rooms
  • Flipcharts at all tables with pens
  • Provide something to play/experience/move
  • Provide a big table in the middle of the room with sticky notes, pens, etc., as a communication hub.

1.2.               Working atmosphere

The working atmosphere differed. Participants expect a relaxed and open minded atmosphere, they also want to have fun during the time they devote to you as hackathon organizers.

In the first hackathons, programmers showed to work in a silent working atmosphere. They preferred to communicate online while working or go outside to discuss in order not to disturb others or to spread their ideas. All other visitors (e.g. project partners) who are not part of teams should have a separate area to not disturb the teams. Participants requested a communication channel during the event for the participants, so that e.g. questions could be shared easily, e.g. SLACK. However, this could be country specific. It was requested in Gdynia, but when provided in Klaipeda, the participants did not use it. Recommendable is to ask participants before the event.

In Greifswald hackathon, the atmosphere was lively with cross-team exchange. The focus here was on creativity, on networking and learning with all teams working on different topics that diminished the competitive angle of the event and could be a reason for this atmosphere. It created a sense of being part in something of value that is created by all teams. The moderation can add a large part to the working atmosphere.

1.3.               Food

Participants need energy, good food is required. Do not provide fast-food, but a real breakfast, lunch and dinner. At night, some extra food is recommended e.g. pizza at around 1 a.m. At the working room, fruits, crackers, crisps, coffee, water, tea should be always available. Some teams requested energy drinks, but it is not a necessity to be provided by the organizers. Ask for specialties in the diet (vegan, vegetarian, other requests/allergies). It proved that there is a large need for a variety of vegetarian dishes.

1.4.               Welcome packs

Welcome your participants and mentors with some gadgets, like t-shirts, mugs, bags or stickers. Fully branded, they also brand all the photos taken during the hackathon.

  • Shirts (different sizes, male/female)
  • Pens, Cups, USB Sticks, Bags
  • Sticky notes, notebooks (could be branded, but not necessarily)
  • Something from inviting organizations
  • Entrance tickets to the inviting organizations for the participants to have a chance to come back after hackathon (so use event for promotion)

1.5.               Sleeping arrangements

Most hackathons last over 24 hours and participants sleep little or not at all. For resting and sleeping arrangements, you should provide a room, participants bring sleeping bags/matrasses. Having some chairs or resting sofas is very welcomed. Also consider that comfortable chairs are needed in the working room to allow for sitting such a long time.

1.6.               Photo/Film

Documentation was done during the hackathons with professional photos and video. Key aspects:

  • Make sure that the agreement regarding taking photos/ recording movie with participants is included in terms and conditions
  • Recommendable: No photos during the night, only in the beginning and in the end
  • Have a briefing of the film crew to not be intimidating to participants, go about with care and do not disturb
  • Group photo after winners’ announcement
  • Professional video: opening ceremony, show branding, work of participants, interviews with organizers, mentors, participants, final ceremony

 

DOWNLOAD FULL TEXT

BalticMuseus Hackathon Guide_20190805_FINAL

Bibliography

Jarvis, D. (2012) ‘MGT567 Creative Problem Solving’ [online], available: https://www.slideshare.net/dajarvis/mgt567-creative-problem-solving [accessed on 16 July 2018].

Leclair, P. (2015). Hackathons: A Jump Start for Innovation. Public Manager, 44 (1), 12–14.

Mergel, I. (2015). Opening Government: Designing Open Innovation Processes to Collaborate with External Problem Solvers. Social Science Computer Review, 33(5), 599–612.

Oxford University Press (2018). Hackathon. Retrieved from: https://en.oxforddictionaries.com/definition/hackathon (01.08.2018)

Piller, F., West, J. (2014). Firms, Users, and Innovation: An Interactive Model of Coupled Open Innovation. In: Chesbrough, H., Vanhaverbeke, W., and West, J. (eds.) New Frontiers in Open Innovation, Oxford University Press, Oxford, pp. 29–49.

Tauberer, J. (2018) ‘How to run a successful hackathon’ [online], available: https://hackathon.guide/ [accessed on 12 June 2018].

 

Co-creationHackathonUser Centric Hackathon in Museums

Related Articles

  • Baltathon – Series of hackathons as creative kick-starters for museums apps – Malmö
  • Hackathon in Museums – Feedback
  • Hackathon in Museums – Project Plan Template
  • Hackathon in Museums – Recommendations Communication

Categories

  • 9Hackathon in Museums
  • 18IT in attractions
  • 6Project Management
  • 9Webinars - BalticMuseums Xchange
  • 14Working Methods in attractions

Most Liked

  • Baltathon – Series of hackathons as creative kick-starters for museums apps – Gdynia 15
  • Lessons Learned in CHESS project – Maria Roussou I BalticMuseums Xchange 2018-10-19 13
  • Lessons Learned Lights on Project – Gamification I BalticMuseums Xchange 2018-04-03 11
  • Hackathon in Museums – Introduction 10
  • Hackathon in Museums – Concept Lessons Learned 9

Most Viewed

  • Generic Learning Outcomes – A way of working 3863
  • Hackathon in Museums – Recommendations Communication 2964
  • New Lahti Art & Design Center – Lessons Learned in (Digital) Service Development I BalticMuseums Xchange 2019-01-21 2206
  • Hackathon in Museums – Concept Lessons Learned 2003
  • Lessons Learned in CHESS project – Maria Roussou I BalticMuseums Xchange 2018-10-19 1787
Flatbase by NiceThemes © 2018 - BalticMuseums: LoveIT! University of Szczecin — Powered by WordPress.