The final presentations and demos are scheduled for various days, details to appear on the front page.
Every team member must take part in the presentation/demo. Everyone must stay for the duration of all the presentations in the day they are presenting. You can take turns, or alternate, as you see fit. Make sure every one of you says his or her name before speaking (for the first time) so I know who is who.
The complete presentation must be no longer than 15 minutes, shoot for somewhere between 10 and 15 minutes.
Bring your own laptop, phone, whatever you need for the demo and presentation. Amoco hall has HDMI and VGA inputs.
The points you have to cover:
- Introduce your team
- Explain the problem your client wanted you to solve (second most important part)
- Explain the problem they had, or the problem your team decide to address. Use examples. Remember that we know nothing about your client.
- Describe how they handle it know, without your app
- Specify the goals of your app. Which user pain points are you addressing?
- Demo (most important part)
- Show the major features.
- If possible, have an ongoing story for the user(s): why is he using your app?
- Make sure you explain what you are doing as you tap on buttons
- Make sure we can see what you are doing, and the results
- Mention the technologies you used in building and deploying your app.
- Give some details into how they fit together
- Any technologies that did not work out? explain.
- Close with a slide on "things we would do differently next time".
Optional: If there is a particular technology or technique you can spend some time discussing it: how to use it, how it saved you time, etc. This would be like a very short tech talk. Alternatively, maybe it is a technology you would not recommend. Do this only if you find that there is not enough to talk about given the above points.
Oral Presentation Grading Rubric
|Area||Excellent (90-100)||Good (80-89)||Bad (65-79)||Failed (< 65)|
|Content / Organization||
|Enthusiasm / Audience Awereness||
Based on rubric from readwritethink.org