Milestone 12: Presentation and Demo
Final demos presentations will be on Reading Day which is Saturday December
7 in Storey 1400. There will be 2 sessions, 9am and 1pm, which should last no
more than 2 hours each. You must attend the session in which you are presenting.
Presentations should be about 5 minutes, never more than 10.
Everyone in the team must attend. Not everyone has to speak (but you
will next semester.)
Bring a laptop from which to show your slides and do your demo.
Bring any dongles you might need to connect your laptop to the
projector. HDMI is most common.
Your demo should be done in the same way a real user would use it. So, if you
are building a phone app then demo it on a phone, if possible.
If you have a phone app, be prepared to demo it on your emulator in your
laptop in case the phone has problems or there is no overhead projector.
In the presentation you will cover:
- Who is your client? What your app is meant to do? What problem does
it solve? (1 slide)
- What technologies are you using? Why? (1 slide)
- A quick demo of what you have working so far. (0 slides)
- What features you will be implementing next semester.
||Failed (< 65)
Holds attention of entire audience with the use of direct eye contact, seldom looking at notes
Speaks with fluctuation in volume and inflection to maintain audience interest and emphasize key points
Consistent use of direct eye contact with audience, but still returns to notes
Speaks with satisfactory variation of volume and inflection
Displays minimal eye contact with audience, while reading mostly from the notes
Speaks in uneven volume with little or no inflection
Holds no eye contact with audience, as entire report is read from notes
Speaks in low volume and/ or monotonous tone, which causes audience to disengage
|Content / Organization
Provides clear motivation for the app and its design, clearly explains features so anyone can understand, covers all important aspects of the app
Provides some motivation for the app and its design, explains features somewhat well, covers some important aspects of the app
Attempts to provide some motivation for the app and its design, explains features poorly, covers some aspects of the app
Does not provide good motivation for the app and its design, does not explain how features work, poorly overs aspects of the app
|Enthusiasm / Audience Awereness
Demonstrates strong enthusiasm about project during entire presentation
Significantly increases audience understanding and knowledge of app and problem domain; convinces an audience that this is a useful and easy to use app
Shows some enthusiasm about project during the presentation
Gives the audience some understanding and knowledge of app and problem domain
Shows little enthusiasm or mixed feelings about project during the presentation
Gives the audience little understanding and knowledge of app and problem domain
Shows no interest in project during the presentation
Gives the audience no knowledge of the app or problem domain