Each talk will occupy 12 minutes , followed by 6 minutes for questions, comments, and transition. Given the time limit, you must stick carefully to your message, and practice your talk multiple times with your group members. Each team member should speak for a portion of the presentation time. Keep in mind that you have been thinking about your project for a while, but your audience has not. So, it is best to start with a big picture of your project (e.g., background, motivation, etc.) and explain the overall objective and the structure of the system that you have built before going into technical details.
Your talk should be accompanied by 8-12 carefully prepared slides. You may use any tool that you like to create slides, but you must email a draft of your slides to me in PDF or PPTX format by 2 pm Mar. 16 (Monday) so that I can take a look and give you some feedback if needed. After that, please email me the final version of your slides by Noon on the day of your presentation so I can upload them to the computer in the classroom. (There won't be time for mucking around with laptops, cables, etc.) However, if you plan to do a demo on your own laptop, please let me know ahead of time, we can arrange for it.
Use your slides to back up what you say to the audience. Don't just write out the words that you plan to say; that gets odd quickly. Instead, give a diagram of the components of your system and describe how they interact. Or, give a screenshot of your system in action and explain what it is doing. Or, give a code snippet on the screen and explain what is interesting about it.
A typical structure of the talk would include: Introduction/Motivation, Overview/Challenges, States-of-the-Arts/Related Work, Methods, Initial Results and Dicussions, Plan of Actions for Remaining Milestones.
Finally, be considerate of your classmates -- be present at all of the class sessions, ask thoughtful questions about these exciting projects and finish an evaluation/feedback form of all presentations except your own.