← A9

In this assignment, we will prepare a 30 second elevator pitch of your prototype for the audience and jurors. We will create a slide that will be displayed as a visual aid alongside your pitch. We will create and present a poster to demo our prototype to jurors and the class. We will create a 1 minute video walkthrough of our prototypes, which we will use when we discuss and demonstrate our prototypes in the final poster session. Lastly, we will polish our prototypes, cleaning up the interface design and squashing usability bugs.

For final presentations, we will have a timer running, and any pitch that goes over 30 seconds will be cut off. Each poster will be visited by two critics (staff and/or jurors). After the presentation, your poster will be kept by the staff for archival and display purposes

The following rubric items are independently assessed. In general, evaluation works such that if the student/team meets, for instance, 9 out of 10 rubric items, then they have earned a grade of 90%. The assignment will not be graded unless it is submitted on a single, well-formatted, and easily readable PDF.

This assignment requires one submission per: team

Pitch
1. Write and submit the script to your pitch
2. Pitch is well-rehearsed, audible, and effectively utilizes, while remaining stricly, under 30 seconds
3. Pitch conveys final point of view of prototype, portrays the underlying user needs, why they aren't met elsewhere, and how the prototype meets them (don't just assert that it's awesome)
4. Pitch has a "hook," using unique and creative elements that will interest people and persuade them to find the poster. This might be an example or scenario

Slide
5. Create a visual aid for your pitch in the form of a single slide image (1920x1080 JPG or PNG), including the final app name of your prototype, excluding any audio or animation
6. Contains one or two screens of the user interface, illustrating the prototype's functionality
7. Slide has a high-level overview of the prototype, and is not cluttered by having too many words or too much detail

Poster
8. Poster illustrates your design process, e.g. design decisions, iterations, and what you learned from users
9. Poster highlights the features that make your prototype's solution to a user problem unique, e.g. displaying the competitive analysis from previous assignments
10. Poster communicates core features of prototype, and stands on its own without explanation
11. Poster is 24" wide, 30" high (portrait orientation) and everything on it is visible and legible. Butcher paper will be provided for you to make your poster

Walkthrough
12. Write and submit the script for 1 minute walkthrough of your prototype
13. In studio, to demonstrate you are well-practiced for jurors visiting your poster and prototype, TAs will video record your walkthrough during the last studio
14. Walkthrough fluidly demonstrates use of the prototype in a logical and sequential manner in strictly less than one minute

Post Mortem
15. Write five to six sentences describing what you learned from working with your team, what you would do differently if you did it all again, mistaken and successful planning choices you made
16. Final prototype meets the functionality and aesthetic requirements from all previous assignments
17. Final prototype is bug free and has a clear interaction flow, with no major heuristic violations
18. There are no spelling or grammatical errors in the slide, pitch, poster, walkthrough, and prototype

Development Plan
19. Verify all tasks are actionable, prioritized, assigned an owner, given a time estimate, has actual time spent and completion date recorded, and every member of the team was assigned and completed at least one programming task
20. In your comments column, identify tasks that were newly added or removed/updated, and add/identify any new stretch goals for development beyond the scope of the class

Submit
21. Submit a clickable or easily typed link to your final prototype of the form “a10-projectname.herokuapp.com”. If your prototype is changed before grading is completed, you will receive no credit for the assignment
22. Submit a clickable or easily typed link to your project repository on GitHub. Make sure the grader has access by the deadline
23. Submit each of the following items: zipped file of your final functional code (for archival/educational purposes), a high resolution photo/image of your poster, and your slide
24. Submit a clickable or easily typable link to -- or a readable, properly oriented, and complete snapshot of -- your dev plan. Make sure the grader has access
25. Make ixd@ucsd.edu a collaborator on Heroku so that we have access to your deployment history

Above and Beyond
26. (Bonus) This point is reserved for teams with prototypes that met all of the above rubric items and went outside the box in their performance, at the discretion of the TA