Challenge Project

Stakeholder analysis

Create a planning resource for future organizers of hackathons.

 Stakeholder map

The mapping above was created during our Hack:Org:X session.

Challenge

  • Teilnehmenden identifizieren
  • Challengers
  • Sponsoren
  • Was bewegt diese Gruppen?

See also:

Retrospectives
Hack:Org:X v.2 Project

Bring your team together, collect feedback after event, share it with the community!

Stakeholder Analysis

A Hack:Org:X project. See https://hackorgx.dribdat.cc/project/12

Motivations

> Identify your internal stakeholders and set expectations. Hackathons are cross-functional. No hackathon is run by a community person alone. It is important to ensure everyone is aligned on the goals, what is required to achieve them, and that the necessary resources are committed.

-- Hackathon Guide (opensource.com)

Further Literature

This content is a preview from an external site.
 

Repository updated

24.08.2023 08:34 ~ loleg

Research

Edited (version 6)

23.08.2023 09:28 ~ loleg

Project

Added Stakeholder map that we designed in our workshop.

23.08.2023 09:28 ~ loleg

Event finished

Event started

Edited (version 4)

17.08.2023 16:24 ~ loleg

Challenge

 
All attendees, sponsors, partners, volunteers and staff at our hackathon are required to agree with the Hack Code of Conduct. Organisers will enforce this code throughout the event. We expect cooperation from all participants to ensure a safe environment for everybody.

Creative Commons LicenceThe contents of this website, unless otherwise stated, are licensed under a Creative Commons Attribution 4.0 International License.