Project Presentation Guidelines

1. Presentation Signup

We will be doing final project presentations on this Friday Dec 4th, next Tuesday Dec 8th, and next Friday Dec 11th. Each team needs to sign up for a time slot to present their final project by this week Thursday the 3rd. You can use the link below to sign up for a presentation time. Groups that give their presentations on the 4th will get extra credit. Each group will get 8 minutes to present.

https://forms.gle/S2xqgFeFMZ39msGw9

2. Presentation Format

We will use the class Zoom link for presentations. Each team should create a slide deck that showcases the final project. The team will have 8 minutes to present the slides in screen share. You can include a short video at the end if you feel that’s important, but don’t make that the whole presentation. Try to leave a little time at the end of your 8-minute block to answer questions. Your slide deck should cover:

  • Motivation (1-2 minutes): what problem are you trying to solve? Why is it important?
  • Challenges (30 sec): why is your project nontrivial to implement?
  • Architecture (1-2 minutes): how is your solution organized? Give a high-level description, preferably with pictures. Please don't show us your code here.
  • Evaluation (1-2 minutes): does it work? Here’s where you can put a video of your project in action. If you do some more formal evaluation, for example with plots that characterize your project’s performance, you can put those here too. Formal evaluation with plots is good, and you should make some plots if possible.
  • Discussion (30 sec-1 minute): (optional) what lessons can we learn?

It's ok if you don't know exactly how your solution will work — most of the time when we are trying to solve hard problems, we don't know exactly how the solution will look in the end. If we did, the problem wouldn't be very interesting. The important thing is to lay out (a) some kind of general idea of what the process will be and (b) sketch what the solution will look like. The understanding is that things are likely not to work out as planned, and you will have to pivot to adapt to unexpected outcomes. Sketching a strategy up front will help you think about what could go wrong and how you might adapt.

3. Presentation Feedback

Each student will evaluate at least 20 presentations by filling out a Google form:

https://forms.gle/Y1jcYbbPuGountcF6

You will be graded on the number of presentations you evaluate (out of 20 points possible). If you review more, you will get some extra credit. I will use the feedback from the students to grade the final presentations. I will also evaluate presentations using the same criteria.

4. Group Member Reviews

For groups of multiple people, each group member will fill out a review of all their team members.

5. Guidelines for Making a good Presentation

These presentations are going to get boring, so here are a few tips to make your a little more interesting.

  • DON'T USE BULLETED LISTS. It is confusing to try and read slides while listening to the speaker also reading the slide.
  • Each slide should be centered around a picture. It's best if the picture is directly related to the point you're trying to make (like a graph or a diagram or a photo of your project), but it can also be a stock image that is indirectly related. As long as the slide is not solid text, you're fine.
  • Memorize what you're going to say — word for word — on the first three slides. That will give you some momentum during your presentation. After the frist slides, have at least a general idea of what you will talk about. Don't ever read from your slides. Your slides are visual aids for your audience, not cue cards for you.
  • Use an authoratative tone. Don't end each sentence with a question mark?