# Deliver Like a Pro ![](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5uD_bvtLi4SeuHsvD%2FScreenshot%202020-06-30%20at%2022.26.27.png?alt=media\&token=e2bf72bd-31f6-4a88-aba1-c65accb89423) 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.](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5ujBxH2Fy_nnbCARf%2FScreenshot%202020-06-30%20at%2022.27.13.png?alt=media\&token=fe2cda11-6546-4cb9-a053-30f7cc321e90) ### 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.](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5uz6eVGxSK_MMhTit%2FScreenshot%202020-06-30%20at%2022.27.23.png?alt=media\&token=b6d65699-65c5-405e-b813-9bee717948ce) ### 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](https://help.osoc.be/global/tutorials/how-to-deliver-like-a-pro/publishing-a-github-page), will help you here. ![Portfolio; students, coaches & oSoc / Making sure the project doesn’t disappear.](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5v625lyTi-iQ2UXQp%2FScreenshot%202020-06-30%20at%2022.27.31.png?alt=media\&token=d8fe48a3-b491-4c9d-a9f4-3ba6edcebd63) ### 4. Support future teams by giving them the 411 in advance. ![Good documentation, assets & guidance help future teams.](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5vIaAfz8OYILXnffH%2FScreenshot%202020-06-30%20at%2022.27.37.png?alt=media\&token=dee6f2d5-702d-474b-862e-859880cafdcc) 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.
](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5vT3QH6Z8DiKbM_kd%2FScreenshot%202020-06-30%20at%2022.31.43.png?alt=media\&token=7f3faf7a-f1c8-4471-aef5-eb8251c41804) Step 1: Go to your **project page** and find the link under "**File Storage**" ![Go to your project page; for example ABB](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MdneP0Tj4KQRszM9umh%2F-MdnecQSF_gWFBb_BJ6P%2FScreenshot%202021-07-05%20at%2000.34.06.png?alt=media\&token=cb254fbc-f70f-4351-98b4-10aef7a6060c) Step 2: Go to **Deliverables** ![There's a folder called "Deliverables"](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MdneP0Tj4KQRszM9umh%2F-Mdnes2hiqxzEqJyqSu4%2FScreenshot%202021-07-05%20at%2000.34.25.png?alt=media\&token=416b4aa4-6dd0-44fa-bbb0-af1f07098f45) Step 3: Find the deliverables **checklist** ![Find the excel with the expected deliverables!](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MdneP0Tj4KQRszM9umh%2F-MdnetQTT4xD9abG1g3U%2FScreenshot%202021-07-05%20at%2000.34.54.png?alt=media\&token=496419d8-6503-4415-bfb4-5cc3aa19e470) Step 4: Start **checking** boxes! ![](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MD6g7UTEoUK55aynt3G%2F-MD6iPlP65D4XUOqQGqx%2FScreenshot%202020-07-25%20at%2022.45.54.png?alt=media\&token=b75ead59-3643-4a92-befd-133b36d221f1) ## Some help ![There are some templates, examples & guidelines to help you out.](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5xkrfzxfJeq5VwIjG%2FScreenshot%202020-06-30%20at%2022.41.46.png?alt=media\&token=047c171e-b5fb-44bd-8a90-2942f38d56e8) ### 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. ![](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB5tHTeUaen_agujtQ8%2F-MB5yJ0BPdzS8omls_lX%2FScreenshot%202020-06-30%20at%2022.41.05.png?alt=media\&token=0d5dfb4f-5cf4-430f-87b3-70ca757fea6d) * 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. ![](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB6-qlGT9TWaD3l6vIZ%2F-MB6-zKO6chAjvSIjCGr%2FScreenshot%202020-06-30%20at%2022.55.58.png?alt=media\&token=5fa06a0c-0cbe-483b-819b-10f49feab566) * Find out how to [create a Github page](https://help.osoc.be/global/tutorials/how-to-deliver-like-a-pro/publishing-a-github-page) * Get access to a [template](https://help.osoc.be/global/tutorials/publishing-a-github-page#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. ![](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB65aDCw6vMXswvPBAq%2F-MB66Q3sMRbB-9Y2GsDx%2FScreenshot%202020-06-30%20at%2023.24.00.png?alt=media\&token=787f9ada-ca7c-415d-83c8-747da78139c5) ### 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! ![](https://2165017364-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LckflnxdoFGRNgQmj50%2F-MB6-qlGT9TWaD3l6vIZ%2F-MB60SxywlM0wOlyzqdV%2FScreenshot%202020-06-30%20at%2022.40.31.png?alt=media\&token=f2bcedc5-88d8-421a-8343-74b8ccf330b7)