The screencast is intended to be an actual record of what your project does, exercising the real app.
There are various free tools available for creating screencasts, including Screencast-O-Matic (Google "free screencast software" for many more choices), plus the UC Berkeley campus has a site license to Adobe Creative Suite, including Adobe Premiere which has high-end video production facilities, and ETS.berkeley.edu even gives free workshops on how to use it.
- Include team member photos, names, GitHub repo
- ~15-30 sec to describe basic customer need
- Demonstrate salient functionality/features & how they relate to customer need
- Don't demonstrate "generic" features like logging in, unless there is something special about the implementation of that feature as it relates to the specific customer need (i.e., why would this feature be different in any other app)
- Please select HD resolution (1080p)
- Clear audio, understandable narration. Even a smartphone headset mic is better than speaking in the general direction of your laptop's built-in mic. A separate USB mic (headset or standalone) is even better, and becoming a practical necessity for distributed teams who use Skype or Google Hangouts regularly.
Post the final version to YouTube, make it public, and submit URL
See examples of previous screencasts here.
For more detailed advice, see the lecture segment "How to Do a Bad Demo or Screencast".