Milestone 18: Demo Days

The final presentations and demos are scheduled for various days, details to appear on the front page.
Grading: Individual

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 Good Bad Needs Improvement
Delivery
  • 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
  • Based on rubric from readwritethink.org