Distribuerede Systemer - Hackathon

Transcript

1. Hackathon
2. “ Et hackathon (eller hack day) er en begivenhed hvor it-udviklere mødes og samarbejder intensivt om udvikling af prototyper, konceptudvikling eller videreudvikling af eksisterende it-projekter. Ofte indenfor et specifikt emne, eller centreret om enkelte data.
3. Hackathon - How to... Success Factors: ◦ Clearly articulated ◦ Attainable ◦ Easy to onboard newcomers ◦ Led by a stakeholder ◦ Organized From hackathon.guide
4. Articulated Projects should have a clear question or problem they are trying to solve plusa reasonably specific proposed solution.
5. Attainable Most projects will accomplish about 25% of what they think they can accomplish in the limited time they have. Manage each project’s goals so participants are able to feel accomplished at the end of the session, not interrupted.
6. Noobs Projects should have ready-to-go tasks for newcomers with a variety of skills and at a variety of skill levels. For coding projects, these tasks can’t require an intimate understanding of the code base, and make sure the build environment can be spun up in less than 20 minutes. Make a list of tasks or create github issues ahead of time!
7. Stakeholder A stakeholder (or “subject matter expert”) guides a project to real-world relevance. Projects without a stakeholder can “solve” a problem that doesn’t exist. Ideally the leader (or one of the leaders) is a stakeholder, or a good proxy for a stakeholder.
8. Organized For projects with four or more members, especially newcomers, the project leader’s role should be to coordinate, ensuring each team member has something to work on and helping to welcome new team members.
9. “ Once hacking has begun, do not interrupt the hackers except to ensure that the hacking is going smoothly, to check that everyone has something to do, and to keep people on the overall schedule. Mid-day activities such as lunch-time speakers and video calls with people off-site are incredibly distracting for participants who are now eager to get working on a problem.
10. 340.000 Så mange penges udvikling forbruger I på disse to dage - per projekt!
11. YOUR PROCESS IS EASY Prepare Execute Plan
13. HACKATHON - THE MASTERPLAN 5. Oktober Kravspec og review af eventuelt klassediagram, E/R-diagram og rollefordeling. Herefter planlægning af hackathon i hver gruppe. 10. Oktober Udarbejdelse af API-kald, opgavelister og projektplan. Deadline for indsendelse af kravspec til Henrik på mail kl. 17:00. 11. Oktober 12:00 : Offentliggørelse af eksamensprojekt på Learn med kravspec for hvert projekt. 12. Oktober Gennemgang af endelig kravspec for hver gruppe. Opsætning af alle udviklingsmiljøer, samt oprettelse af grundlæggende strukturer for koden. 30. oktober Code-freeze for server-applikationen. Det vil herefter være en individuel opgave at lave eventuelle mangler færdig.. 16. december Eksamensaflevering. Der skal afleveres en serverapplikation, klient-applikation og en rapport.