# Deliver Like a Pro ![](/files/-MB5uD_bvtLi4SeuHsvD) 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 😎 ![Showing something that works on the demo day is key.](/files/-MB5ujBxH2Fy_nnbCARf) ### 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. ![It can only work when it’s well-documented, and when the vision is crystal-clear.](/files/-MB5uz6eVGxSK_MMhTit) ### 3. Make the ship discoverable & traceable for interested audiences. 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 [Github Pages](/global/tutorials/how-to-deliver-like-a-pro/publishing-a-github-page.md), will help you here. ![Portfolio; students, coaches & oSoc / Making sure the project doesn’t disappear.](/files/-MB5v625lyTi-iQ2UXQp) ### 4. Support future teams by giving them the 411 in advance. ![Good documentation, assets & guidance help future teams.](/files/-MB5vIaAfz8OYILXnffH) 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 created a
deliverable checklist 
to help teams accomplish these steps.
](/files/-MB5vT3QH6Z8DiKbM_kd) Step 1: Go to your **project page** and find the link under "**File Storage**" ![Go to your project page; for example ABB](/files/-MdnecQSF_gWFBb_BJ6P) Step 2: Go to **Deliverables** ![There's a folder called "Deliverables"](/files/-Mdnes2hiqxzEqJyqSu4) Step 3: Find the deliverables **checklist** ![Find the excel with the expected deliverables!](/files/-MdnetQTT4xD9abG1g3U) Step 4: Start **checking** boxes! ![](/files/-MD6iPlP65D4XUOqQGqx) ## Some help ![There are some templates, examples & guidelines to help you out.](/files/-MB5xkrfzxfJeq5VwIjG) ### 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. ![](/files/-MB5yJ0BPdzS8omls_lX) * Find the template in your team folder * Find examples of the handover dossier here ### 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. ![](/files/-MB6-zKO6chAjvSIjCGr) * Find out how to [create a Github page](/global/tutorials/how-to-deliver-like-a-pro/publishing-a-github-page.md) * Get access to a [template](/global/tutorials/how-to-deliver-like-a-pro/publishing-a-github-page.md#picking-a-template) \[[example](https://osoc20.github.io/gh-pages/)] ### 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 – and a kind goodbye. ![](/files/-MB66Q3sMRbB-9Y2GsDx) ### 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! ![](/files/-MB60SxywlM0wOlyzqdV) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.osoc.be/global/tutorials/how-to-deliver-like-a-pro.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.