open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • 09:00 [team only breakout] Prepare first client meeting
  • 10:00 or 11:00 [client and team] Client meetings
  • 12:00 [coaches & student coaches only] Optional Fika
  • 13:00 [team only breakout] Scope Your Hackathon Goal
  • Why we do hackathons
  • What happens during a scoping session
  • 15:00 [team only breakout] Start Hackathon
  • 17:00 have a nice day 🥳

Was this helpful?

  1. Organisers
  2. On-site editions: 4 weeks of well-organised serendipity
  3. Calendar Example Remote Edition (BE)
  4. Week 1: Explore

Day 2: Meet the Client + Prepare for Hackathon

Get all the information you can from your client, and decide on your battle plan for the hackathon!

PreviousDay 1: Welcome (to the Madness 😏)NextDay 3: Hackathon & Pitching

Last updated 3 years ago

Was this helpful?

This is an example of the remote edition fo 2020. Go to the website of your specific edition if you want to figure out what's happening now!

09:00 [team only breakout] Prepare first client meeting

Prepare for your first client meeting!

  • Present your team members (students and coaches)

  • Check if you understood all needs and goals (you can reuse the pitch you made on day 1)

  • List all the questions you have

  • Decide who does the talking

  • Decide who takes notes

Some tips and tricks can come in handy if you've never attended a client meeting before:

10:00 or 11:00 [client and team] Client meetings

Depending on the team you are on, you will have a client meeting at 10:00 or 11:00.

If you need more meetings, you are free to book them with the team and client.

12:00 [coaches & student coaches only] Optional Fika

Talk about what's been going on your team; the good and the bad – in the Fika voice channel <3

13:00 [team only breakout] Scope Your Hackathon Goal

Why we do hackathons

We do hackathons at the start of osoc to...

  • ...really get to know each other. It's your time to shine, show what you can do and see how your other team members can bring a project to the next level ✨

  • ...run through a first cycle together; from defining what you're going to build, to building, to delivering a first valuable thing, which you will define during the scoping session.

  • ...make mistakes. Please make a lot of mistakes and learn, to do better in the next cycle 🔥

What happens during a scoping session

For example:

  • Refine the story

  • Create your wireframes/mockups

  • A first prototype

  • Try out a new technology

  • ... Surprise us

Take the time you need, the team decides when they are to start hacking!

15:00 [team only breakout] Start Hackathon

Let's get started!

17:00 have a nice day 🥳

The overview of the #osoc20 partner meetings, with a link to a room for each project:

Decide with the team what you want to create during the hackathon. This depends on your project, team members and goals! There's a .

Oh and remember the rule of π ()... When doing an estimation of a task, let's say, for an hour, it's most likely to take about 3.14 times longer. Thank us later.

Need to get the creative juices flowing first? Do a first!

https://cloud.openknowledge.be/s/RyD2T6acDy9aAXy
pi
brainstorm session
Tutorial: how to do a client meeting.
tutorial on how to do a scoping session