May 25, 2022
Hackathon — generate and develop innovative ideas for the financial world together!
Did you know that? The first hackathon took place in 1999 at the JavaOne conference in San Francisco, where programmers, developers, and engineers came together to develop a program for the Palm V, a state-of-the-art PDA at the time. The idea came from computer scientist John Gage. Alternative names are “Hack Day”, “Hackfest” or “Codefest”. Based on this exciting approach, we at PPI.X have developed a vision for 2021 with a two-part event (1. an internal event and 2. with a customer and potentially a partner):
The aim was to jointly produce useful, creative, and entertaining products or to find solutions to given problems during the hackathon.
What was required was the inventiveness of all participants, their creativity, enthusiasm for development, and the fun of trying something new with this event.
Relevant questions for our 1st hackathon in advance and on the two event days:
1. Which problems to be solved and ideas to be implemented do you see as the most relevant?
2. What types of outcomes are we addressing?
3. What information do you need and what concerns do you possibly have?
4. Which methodological elements do we need in the preparation, implementation, and follow-up?
5. Which preparatory steps for our hackathon are (still) necessary?
Based on this, a common agenda was created, which was iteratively and incrementally adopted during the event:
- day — impulse
9.00 a.m. — 9.30 a.m.: Presentation of the topic and joint prioritization, coordination/impulses
9:30 a.m. — 10:30 a.m.: Joint planning for day 1
…
5.45 p.m. — open end:
evening event
2. day — impulse
9.00 a.m. — 9.30 a.m.: Start the day together / coffee together
…
5 p.m. — 6 p.m.:
Presentation of the prototype (30 minutes) and the sales presentation (30 minutes) to PPI internal “customers” for feedback
6:00 p.m. — 6:30 p.m.: Conclusion and concrete next steps
Desired Result Types
a) Cross-skill, cross-functional team 1, 2, 3:
- Prototype for the jointly prioritized topic
b) Approximately three suitable user stories and associated technical tickets including an architectural diagram
c) Sales presentation including lean canvas or business canvas, white paper, and potential intranet contribution
A good success always needs some nerve food. The participants received a little “food” for their souls in a small shipping box! 😊
