Sample Hackathon Schedule

Your Hackathon schedule will vary greatly depending on how long you are planning for your day and what your theme/prompt/activity is. The things we recommend most are:

• 'Chunk' the day - have clearly defined code sprints. Integrated breaks, games, or other activities between them so participants don't burn out.

• Encourage brainstorming time before actual work begins. If students have mentors, they may need sign off before they begin their projects.

• Incorporate feedback sessions whenever possible, or other moments for teams to step back and examine their work.

• Set clear expectations for each section of the day, including what can reasonable be expected to be accomplished.

A sample schedule may look something like:

• 8:30 - 9:00: Entry, breakfast, get settled in teams

• 9:00 - 9:20: Welcome, norms framing, prompt

• 9:20 - 9:45: Brainstorming, mentor check-in

• 9:45 - 10:30: First Code/Work Sprint

• 10:30 - 10:45: Brain break (games, team builder, something else)

• 10:45 - 11:45: Second Code/Work Sprint

• 11:45 - 12:00: Mini feedback session - partner with group or with mentor

• 12:00 - 12:45: Lunch

• 12:45 - 2:00 - Final Code/Work Sprint

• 2:00 - 2:15 - Presentation Prep

• 2:15 - 3:00 - Presentations/Judging

• 3:00 - 3:15 - Judges Deliberate, participant brain break

• 3:15 - 3:30 - Award ceremony

• 3:30 - 3:45 - Thank you, clean up, exit.