Project Demos
Last updated
Last updated
Project Demos will be held on designated Mondays. Each demo will consist of:
Up to 5 minutes max of presentation and
use the remaining time for feedback
10 minutes total
Have a member of your accountability team take notes for you when your work is being critiqued and do not edit the responses, whether you agree with them or not.
You will demo the project in its current state.
The focus is on the actual artifact you are creating and nothing else.
Do NOT create a supporting presentation.
You can also show multiple things for your project demo. Put each one in a separate padlet card (see link below).
For UI/UX for websites and apps, your project demo could include user workflow, user journey, and/or customer journey, sitemaps, wireframes/schematics, and/or clickable prototypes in the software of your choice.
For animations/videos, your project demo could include storyboards, style frames, animatics, audio, and/or motion tests.
If you're working on a game, you could include the story, character & other object sketches, interaction tests, levels, maps, puzzles, etc.
Review the rules of the (AKA getting and giving feedback).
Because each student is working on individual projects, your may vary, but you need to show something visible and concrete.
The majority of you are working on either UI/UX for websites or apps or animations/videos. Make sure you review the resources.
This is an example of a good wireframe: with the exception of the one paragraph of lorem ipsum text. Also do not use color.
Always document any feedback you receive on your project management platform after any . This critique feedback post should include images of the current status of your project (prototype or version), a description of your project progress as it currently stands, and discussion of the feedback you received from the critique. How will this feedback improve your work and ideas?