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
  • Prepare for the Pitching Rehearsal: Instructions
  • During the pitches, when your team is not up
  • During the pitches, when your team is up
  • After the Pitches: Project Breakouts
  • 09:00 [team only breakout] Plan/scope for Delivery Week
  • 11:00 [coaches and student coaches only] Optional Fika
  • 13:00 [all teams] Pitch stream
  • 15:00 [team only breakout] Team learnings
  • 15:30 [team only breakout] Retro
  • 17:00 have a nice day 🥳
  • [optional After Work Event] 18:00 Movie Night

Was this helpful?

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

Day 4: Pitch & Battle Plan

See all pitches, zoom out and prepare for next week 🔥

PreviousDay 3: Build, test, document, shipNextWeek 4: Deliver

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!

Prepare for the Pitching Rehearsal: Instructions

During the pitches, when your team is not up

We show 3 pitches, and then interview 3 teams. Sit back and enjoy 🤩! Show ♥️ and give feedback in #pitch-chat.

During the pitches, when your team is up

  1. After those 3 pitches we'll ask one team member of each team we just saw to answer one question.

  2. The three representatives of those teams go to the waiting room when their pitch is up.

  3. They'll be introduced to the pitch arena, where they answer the question.

  4. Leave when the 3 team representatives have answered the question 😘.

How to prepare:

  • Select one team member of your team.

  • That team member prepares a very short answer to that question.

Example:

  • Pitches of Team 1 (Bridges), 2 (ArTIFFact Control) and 3 (Simplification of election procedures) are shown

  • Representatives of Team 1, 2 and 3 go to the waiting room during those pitches.

  • Representatives of Team 1, 2 and 3 are introduced to the pitch area, and answer the question in that sequence.

  • They all leave at once when the answers have been given.

  • Next team pitches: 4, 5 and 6. During those pitches their representatives go to the waiting toom.

After the Pitches: Project Breakouts

After the pitches, you get the opportunity to discover more and perhaps view demos 😻.

The selected teams show demos or give more information, other teams can roam & discover! Recommended when roaming: switch every 5 minutes 😉

Select a Host

  1. Go to the breakout room first to get moderator rights. Keep it open in your browser tab from the moment the pitch stream starts 😁

  2. Mute visitors Only people that are presenting or ask questions should have their mics on.

  3. Ask visitors to write down questions.

  4. Read those questions out loud & invite the writer to speak whenever their question gets addressed, so they can have a conversation.

  5. Something wrong? Have someone report to Miet in #practical-questions.

  6. If you have no visitors, think of a game you can play 😁 👯‍👯

0-15 mins: Teams 1-9

  • Selected teams demo and answer questions.

15-30 mins: Teams 10-19

09:00 [team only breakout] Plan/scope for Delivery Week

Do apply the rule of π!

11:00 [coaches and student coaches only] Optional Fika

Cancelled due to hard work!

13:00 [all teams] Pitch stream

15:00 [team only breakout] Team learnings

You get some time to reflect on the hackathon and on the feedback you got on your pitch.

What did we learn? How can we work better as a team?

15:30 [team only breakout] Retro

Pick a retrospective:

17:00 have a nice day 🥳

[optional After Work Event] 18:00 Movie Night

We'll show 3 pitches of 3 teams ()

Write down the team member and answer here:

Your job is to make things go smoooooth. .

1 Bridges

2 ArTIFFact Control

3 Simplification of election procedures

4 BetterBikeBrussels

5 WalkByBrussels

6 Urban Brussels

7 Fitigai

8 Comms Team

9 NMBS Route Planner

10 Serendipity Engine

11 Bike Data Project

12 Cyclofix

13 Fast and Slow

14 FRIS

15 Job match

16 Shmdoc

17 RML.io Dashboard

18 Get Engaged

19 Bitoftrust

We will show off all of our pitches! Go to the to see what needs to happen.

Create some room for each other to talk about what's good and what could go better. .

See "retrospective"

sequence found here
https://docs.google.com/spreadsheets/d/1LEOFnsOYX1sOJuNBzhD277bCgdci9O_vAOphsx2vnGE/edit?usp=sharing
Write down who will
meet.openknowledge.be/1
meet.openknowledge.be/2
meet.openknowledge.be/3
meet.openknowledge.be/4
meet.openknowledge.be/5
meet.openknowledge.be/6
meet.openknowledge.be/7
meet.openknowledge.be/8
meet.openknowledge.be/9
meet.openknowledge.be/10
meet.openknowledge.be/11
meet.openknowledge.be/12
meet.openknowledge.be/13
meet.openknowledge.be/14
meet.openknowledge.be/15
meet.openknowledge.be/16
meet.openknowledge.be/17
meet.openknowledge.be/18
meet.openknowledge.be/19
http://www.frederikvincx.com/8-sticky-note-walls-keep-team-track/
http://www.funretrospectives.com/
instructions
A 7-minute tutorial