Keep in mind as objective of your project: build deep rather than wide, i.e. try focusing on a single thing to build so that you have a workable demo.
At the end of the EUhackathon, a time slot is foreseen for contestants to pitch their project’s end-result to the other participants and the jury.
We cannot sufficiently stress the importance of these pitches in convincing the jury, and greatly encourage to take into account the guidelines below when preparing your pitch.
We ask all participants to follow a given structure, in order to facilitate the work of the jury members.
The presentation should hence include the following information in the given order:
We are very strict when it comes to keeping your pitch to 5 minutes, so if you go beyond you will be interrupted. Make sure your pitch is concise, cut to the chase and put any elements that could be of less value to the audience (e.g. the list of used codes, APIs, etc.) at the end so it matters less if you can ramble the whole list off.
Consider that everything that technically can go wrong, could go wrong during your presentation. The Internet connection could crash, your software could be buggy, the microphone could die … the simpler your presentation, the less likely it will be affected by such events.
If you work in team, take into consideration that the pitch needs to be made in English, which may not be your native language and/or your team members’. Choose the person most comfortable at speaking in English under time constraint as your spokesperson. You can obviously switch between team members but do ensure such transitions are smooth and streamlined, so you don’t loosed valuable time.