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 [all teams] Hackathon pitch stream
  • 11:00 [team only breakout] Team learnings
  • 12:00 [coaches and student coaches only] Optional Fika
  • 13:00 [team only breakout] Plan/scope for next week
  • 15:00 [team only breakout] Retro
  • 17:00 have a nice day 🥳
  • 18:00 [optional] Let's Hang Out

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 4: Pitch & Battle Plan

See all hackathon results, zoom out and prepare for next week 🔥

PreviousDay 3: Hackathon & PitchingNextWeek 2: Build

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 [all teams] Hackathon pitch stream

In the morning we will show off all the pitches created by the teams during their teams 💪

Give the pitches you like a vote with your emoji in the #pitch-vote channel! 👍

Hype each other in the #pitch-chat channel ♥️

Give us your feedback in the form below 👀

  • what you liked about each pitch

  • what needs work for each pitch (constructive feedback!)

11: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?

12:00 [coaches and 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] Plan/scope for next week

What do we build?

To put all those learnings into action, and to make sure the entire team knows what to expect next week, you can plan what to work on in the first build week.

Do apply the rule of π!

15:00 [team only breakout] Retro

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

Pick a retrospective:

17:00 have a nice day 🥳

18:00 [optional] Let's Hang Out

Board game night, boiler room, cozy room ... TBD 🤔

See "retrospective"

http://www.frederikvincx.com/8-sticky-note-walls-keep-team-track/
http://www.funretrospectives.com/
https://agilestrides.com/blog/40-ideas-to-spice-up-your-retrospective/
Vote - Love - Rate