# Hackathon day 2 — 4

## Example structure

1. Teams prepare client meeting (day 1 and 2)\
   \- Get briefing from coach\
   \- Prepare questions and meeting
2. Teams meet with client (day 2)\
   \- Ask questions, take notes, ask input
3. Teams prepare hackathon (day 2)\
   \- Set up dev environment\
   \- Read up on briefing, study client\
   \- Prepare battle plan
4. Brainstorm (day 3, but not for well-defined projects)\
   \- Only for projects that need brainstorming for their project
5. Scope (day 3)\
   \- Define what you're going to build during the hackathon.
6. Hack (day 3 for well-defined projects, day 3 and 4 for brainstorm projects)
7. Present to other teams (day 4)
8. Feedback from other teams (day 4, but not for brainstorm-type projects). Clients can see the result on the next client meeting.

A more detailed agenda can be found on the website.

Belgium: <https://2019.summerofcode.be/practical.html>\
Spain: <https://2019.summerofcode.es/whoweare.html>

### Day 2

![Example of day 2](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-LhcJ71VpQjdsnHr4MNy%2F-LhcJsu3sFA2_NzpuwDo%2FScreenshot%202019-06-17%20at%2022.02.39.png?alt=media\&token=c1361b2c-851f-4891-be5e-0167d99c738d)

### Day 3

![Example of day 3](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-LhcJ71VpQjdsnHr4MNy%2F-LhcJyDMaCBhlikb9usN%2FScreenshot%202019-06-17%20at%2022.02.19.png?alt=media\&token=7b702840-804e-42a5-97e7-2d0743ec6d53)

### Day 4

![Example of day 4](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-LhcJ71VpQjdsnHr4MNy%2F-LhcK0_QMpigWj7dLDNf%2FScreenshot%202019-06-17%20at%2022.02.26.png?alt=media\&token=6d0285d7-02f4-4fcf-881b-f8162190e505)