📁
Cityhacks
  • Welkom op Cityhacks!
  • De Uitdaging
  • De Manier van Werken
  • Samenwerken zonder samen te zitten
  • Wie zit hier achter?
  • Programma
    • 28.10 - Datadive
    • 13.11 - Cityhacks
      • 8u45 - Kick-off op Youtube
      • 9u00 - Start
      • 9u30 - [optionele talk] Open street maps
      • 10u00 - Sportieve break
      • 11u00 - Sparren met sportprofessionals
      • 12u00 - Lunch
      • 14u00 - Eerste pitch
      • 14u30 - [optionele] talk Leren pitchen
      • 15u00 - Fika of koffieklets
      • 16u00 - Sportieve break
      • 18u00 - Dageinde Stand-up
      • 20u00 - Dansen achter uw bureau
      • 21u00 - Sportieve break
      • 23u00 - Disney zangstonde
    • 14.11 - Pitches
      • Hackathon pitches
      • Hosting
      • Interviews
  • Tools & Resources
    • Open Data
    • Discord
      • Discord etiquette
      • Je gebruikersnaam aanpassen
      • Managing notifications
      • Offering and Receiving Help
    • YouTube stream
    • Pitch Tricks
    • Deliver Like a Pro
      • Publish a Github Page
  • Coaching
    • Je bent een coach op Cityhacks
    • Praktisch: Waar, wanneer, ...
      • 14/10 - Coach the coach
      • 28/10 - Datadive
      • 13/11 - Cityhacks
      • 14/11 - Pitches
    • The Coaching Job
      • Kennismaking met je team
      • Taakverdeling
      • Team-management
      • Motivator, inspirator, coach
      • S.O.S. voor coaches
    • Jurybeoordeling
Powered by GitBook
On this page
  • Most important
  • 1. Make sure you ship something.
  • 2. Make sure your client can find & reuse that ship.
  • 3. Make the ship discoverable & traceable for interested audiences.
  • 4. Support future teams by giving them the 411 in advance.
  • The checklist
  • Some help
  • The Handover Dossier
  • Github Pages
  • The Other Deliverables
  • The Handover Email
  • We use the last week to get it done

Was this helpful?

  1. Tools & Resources

Deliver Like a Pro

We created osoc to give students and newly graduates a first relevant work experience. We'll help you with communicating and delivering like a pro.

PreviousPitch TricksNextPublish a Github Page

Last updated 4 years ago

Was this helpful?

You and your other team members will create a lot of valuable things for the client in these 4 weeks. It's important that they get to see it, use and reuse it (we are open!).

That's why you, as a student, are responsible to make sure you gather and communicate about this!

Most important

1. Make sure you ship something.

Make it something you'll be proud of, and you can show off in your portfolio 😎

2. Make sure your client can find & reuse that ship.

Gather everything, document it well and make sure they can find out about where to find everything (in the team's deliverables folder) via a handover email at the end of osoc.

3. Make the ship discoverable & traceable for interested audiences.

4. Support future teams by giving them the 411 in advance.

Giving someone the 411 means you give them all context and updates they need to hit the ground running; to make sure that they are as informed as possible. It definitely is possible your project returns next year.

So if you are working on a project that has been around the year before, make sure you get your hands on that information!

The checklist

We have changed from Nextcloud to Drive because of editing issues. Sorry for the inconvenience!

Step 2: Go to Deliverables

Step 3: find the deliverables checklist

Step 4: Start checking boxes!

Some help

The Handover Dossier

Gather all the knowledge of the team’s project in this dossier. This will help the client understand what kind ship the team has built, how they got to that ship, and where to find everything.

Github Pages

The internet is volatile. Things disappear. Your effort should not. We want to make sure the project remains findable & traceable even after it’s removed from its domain name, and is still legible by people that don't want to dive in the code.

The Other Deliverables

Contacting press, user tests, .. Not everything has a guide. But we have many coaches, student coaches and even students to help out. Get in touch!

The Handover Email

Write a clear, professional email with a link to your deliverables at the end of open summer of code (see calendar) – and a kind goodbye.

We use the last week to get it done

Yes, it’s a lot. This is why we have the last week available to do that. our team is not just to “code”, “write”, “business”. They are here to learn to see the bigger picture, create a project, to grow. It’ll help them do that!

Make sure your project can survive on the internet, and you can refer to it in your portfolio. A link that can won't suddenly be taken down, like for instance on , will help you here.

Step 1: Go to the drive folder for students ****

Find the template in your team folder

Find examples of the handover dossier here

Find out how to

Get access to a []

Github Pages
https://drive.google.com/drive/folders/1n4SAYpis-DJbNmb5zPcaw6bjP-aQEFRm?usp=sharing
https://drive.google.com/drive/folders/1n4SAYpis-DJbNmb5zPcaw6bjP-aQEFRm?usp=sharing
https://drive.google.com/drive/folders/16z6e39rb6t7AAgYl0InFLsG09o8BI3BC?usp=sharing
create a Github page
template
example
Showing something that works on the demo day is key.
It can only work when it’s well-documented, and when the vision is crystal-clear.
Portfolio; students, coaches & oSoc / Making sure the project doesn’t disappear.
Good documentation, assets & guidance help future teams.
We created a
deliverable checklist 
to help teams accomplish these steps.

There are some templates, examples & guidelines to help you out.