Project: Presentation

Each project group will present their work during our scheduled final exam time. Your group will have up to 25 minutes to present your work, plus five additional minutes for questions at the end of the presentation. All group members must participate in the presentation; speaking time does not need to be divded into perfectly-equal pieces, but each group member should contribute to required elements of the presentation. Presentations will be graded on their completeness (not duration) so make sure you include the following components:

Goals: What was the goal for your project? Your final goal may have changed since you wrote your proposal, but there should still be a clear objective to the work you are doing. Make sure it is clear to the audience what achieving this goal enables: what is possible now that your project is (nearly) done?
Approach: At a high level, how did you try to achieve the goals you set for yourselves? Describe the major components and how they fit together to create a working system. Try not to include too many technical details at this point, unless they are absolutely necessary to understand the approach you took.
Demo: Show us the result of your efforts. It is okay if your project isn’t 100% working, but you should craft a demonstration that shows at least some element of your project in a working state. If it is not possible for you to show any running example of your project we can discuss an alternative approach. You are welcome to include interactive pieces or live coding in your demonstration if it helps you show the impact of your project.
Challenges: Choose two interesting challenges that you had to solve when working on your project. Describe each challenge at a high level, explain why it comes up in your project, and discuss how you solved (or tried to solve) it. Include enough technical details that the audience could come up with a solution to each issue with minimal effort if they were ever asked to implement something like your project.
Conclusion: Finish your presentation with a brief recap of the most important pieces of your talk. You’ll feel like you are just repeating yourself, but the audience will appreciate a short recap before asking questions.

Rubric

Component	3	2	1	0
Style	The presentation is clear, organized, and entertaining. The entire presentation makes effective use of visuals, whole-group interaction, and technical details where necessary.	The presentation is mostly clear, organized, and entertaining. Some elements of the presentation were less effective, but the main components of the presentation were still understandable.	The presentation was difficult to understand or follow. The presentation may use slides or visuals, but these do not add significantly to the content of the presentation.	The presentation was unclear and disorganized. Major elements were missing or difficult to discern.
Goals	The presentation clearly describes the goals of the project. The impact of achieving the stated goals is made clear to an audience of CSC 395 students.	Goals are still clear, but the presentation includes unnecessary technical detail that makes it difficult to understand the high-level objectives.	The presentation may convey goals clearly, but does not describe the impact/importance of those goals.	The presentation includes a minimal discussion of project goals, or no discussion at all.
Approach	The presentation clearly described the approach with the bare minimum set of technical details. The audience will understand the main points of the project implementation based on this section of the presentation, and is prepared to delve into technical details later.	The presentation describes the approach welll, but includes extraneous technical details or leaves out some key information required to understand the demo and/or later technical discussions.	Only parts of the approach to the project are conveyed clearly or at all. Major pieces are missing, and those missing pieces make it difficult to follow the later demo or technical discussion.	The approach was not discussed, or was missing so much detail that it was almost entirely unclear.
Demo	The presentation includes an effective demonstration of the project's functionality. The demo may not show the entire system, but it connects with at least some part of the project's stated goals in a way that is clear to the audience.	The presentation includes a working demonstration of some project functionality, but that functionality is not obviously connected to the project goals/impact.	The presentation includes a demo that seems disconnected from the project goals, or was non-functional to the point that it could not be understood.	The presentation does not include a demo, or the demo is not connected to the project goals at all.
Challenge 1	The presentation describes an interesting challenge with enough detail to appreciate the solution. The discussion of the solution would help a future implementer of a similar project prepare for this challenge in the future.	The presentation includes a clear and effective discussion of a challenge in the project, but the challenge/solution was not especially deep or surpsising.	The presentation discusses a challenge but does not include a thorough discussion of a solution to that challenge.	The presentation does not discuss a challenge encountered during the project.
Challenge 2	Same as above, but for second challenge.
Questions	The group understands and answers questions from the audience. Answers are honest, clear, and to the point. An answer of "I don't know" is always acceptable, but the answer can still address parts of the question where you have some understanding.	The group answers questions, but may not directly answer the questions intended by the audience, or includes inappropriate technical details that distract from the core of the answer.	The group offers answers that do not directly address questions from the audience.	The group does not effectively answer questions asked after the presentation.