# Tech for Better, Prepare Me ---           --- # TFB Presentation Guidance The purpose of this document is to provide advice about how to prepare a Tech for Better project presentation. Practice is the best preparation! Reach out to FAC students, alumni, and staff for feedback on your presentations! ## Content tips Consider using a template slide kit (Canva has lots) Discuss design challenges your team faced Show the evolution of your project: Pen and paper --> Figma prototype --> MVP Consider showing DB schema, flow diagrams, other graphics if they add to the story you're telling Weave standout quotes from user research/testing into the story Talk about your processes, including: How you structured your work (project kanban board) User story estimation, and how this compared with actual time taken How you stayed on track (stand ups, retros, sprint reviews, planning) Show your tech stack: Which technologies you used (logos are handy for showing this) Why you opted to use those ones vs others GIF screengrabs are great for showing how UI components work (Have a look at Loom) Data viz (i.e. stacked bar charts, burndown charts) is a great way to show estimated vs actual velocity Make sure code snippets really are snippets! (viz. keep them short) Mention any interesting work you'd tackle if you had more time Have a ‘Thank you/Questions?’ slide so that your audience knows when to clap at the end of your presentation! ## Structure tips Introduce yourselves and your role in the project Give a brief overview of what your presentation will cover at the start Use the rule of three to highlight key points on slides Have some kind of progress indicator on your slides - helps your audience to keep track of what you're talking about ## Delivery tips Spread talking time equally between you It looks slick when everyone knows who’s delivering each part of the presentation. Try to work this out beforehand Designate someone to change slides Talk about team achievements first, individual achievements last... ...but make sure everyone has a chance to talk about an individual contribution that they are proud of. This could be phrased as a challenge related to your role that you overcame. Explaining code that someone else wrote is a good way to credit your teammates while showing off your own understanding of the codebase Refer to line numbers to make it clear which part of the code you're talking about Practice your presentation at least once together ## Example slide decks ​Team LsX Partners Day Canva slides​ ​Team SquareCircle Partners Day slides​ ## Handy Tools ​Canva - professional presentation templates ​Excalidraw - make "handdrawn" mock ups of your UI ​Creately - create process diagrams (i.e. to map the flow of your app) ​Dbdiagram.io - visualise your db schema ​Gyazo - record GIFs of your screen ## Team Achievements We designed and built a useful product in three weeks. "We will be using this, even unfinished it is still really useful" - Trina, our PO We learned how to use a lot of new technologies in a very short time. We kept thorough project documentation. Notion, README, code comments. Very strong working relationship with PO. Helped keep focus on what the MVP was and what the priorities were. Made sure to stretch often! ## Invividual acheivements ### Kat ### Roger - Developed a deeper understanding of React - Particularly hooks, state management and context - Fallen in love with styled components - Work life balance / evening fun time ### Chloe ### Ako