A10: Show & Tell Team submission

In this assignment, you will prepare presentation materials for your final presentation. Create a 30 second pitch of your prototype for the audience and jurors. Create a slide that will be displayed as a visual aid alongside your pitch. Create and present a portrait-orientation poster to share your process and compare with alternative approaches. Create a 1-minute video walkthrough of your prototype, which you will use when you discuss and demonstrate your prototype in the final poster session. Lastly, you will polish your prototype, cleaning up the interface design and squashing usability bugs.

There is no dress code for the final presentations. Wear whatever you feel most comfortable in when presenting and talking to jurors.

Any pitch that goes over 30 seconds will be cut off. While all team members must be on stage, not everyone is required to speak. Pitch should cover 1) What is the problem? 2) Why doesn’t the obvious thing available today address it? 3) What is one concrete feature of your app that achieves it. (Avoid laundry lists: “it slices, it dices, it’s a TV remote!” Privilege concrete examples over vague flowery language.)

The purpose of the poster is to depict your process. We do not require them to be slickly produced. Each poster will be visited by two critics (staff and/or jurors). After the presentation, the staff will keep your poster for archiving and display. Consider the 4 ways in which you are presenting: The slide, verbal pitch, poster, and video walkthrough. Distribute layers of information across these mediums to convey the problem your prototype is addressing, and the unique proposition of your idea. While we encourage everyone to stay through the award announcements at the end of the show, you may leave after your poster has been visited by both reviewers.

You will only need to bring your poster to the final show location. We will provide all mounting supplies.

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.

Evaluation Rubric

Note: if you are a rare group of 2: pursue a dev plan that meets the rubric with a reasonable workload. If you are unable, you may propose an accommodation to this on Piazza; include a link to your dev plan.

  1. Pitch
    1. Write and submit the script to your pitch
    2. Pitch is well-rehearsed, audible, and effectively utilizes, while remaining strictly, 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
  2. Slide
    1. 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
    2. Contains one or two screens of the user interface, illustrating the prototype's functionality
    3. Slide has a high-level overview of the prototype, and is not cluttered by having too many words or too much detail
  3. Poster
    1. Poster illustrates your design process, e.g. design decisions, iterations, and what you learned from users
    2. Poster highlights the features that make your prototype's solution to a user problem unique, e.g. displaying the competitive analysis from previous assignments
    3. Poster communicates core features of prototype, and stands on its own without explanation
    4. 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
  4. Walkthrough
    1. Write and submit the script for 1 minute walkthrough of your prototype
    2. 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
    3. Walkthrough fluidly demonstrates use of the prototype in a logical and sequential manner in strictly less than one minute
  5. Post Mortem
    1. 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
    2. Final prototype meets the functionality and aesthetic requirements from all previous assignments
    3. Final prototype is bug free and has a clear interaction flow, with no major heuristic violations
    4. There are no spelling or grammatical errors in the slide, pitch, poster, walkthrough, and prototype
  6. Development Plan
    1. A clickable or easily typed link, or a readable, properly oriented, and complete snapshot of your dev plan. Make sure the grader has access by the deadline. All tasks are actionable, prioritized, assigned an owner*, and given a time estimate. In your comments column, identify tasks that were newly added or removed/updated. Includes a sum of the expected and actual number of hours for each teammate. Outliers should be justified
    2. 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
  7. Submit
    1. 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
    2. Submit a clickable or easily typed link to your project repository on GitHub. Make sure the grader has access by the deadline
    3. 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
    4. Make ixd@ucsd.edu a collaborator on Heroku so that we have access to your deployment history
  8. Above and Beyond
    1. (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

Student Examples

Here are some randomly selected examples from prior years. Note assignments change from year to year, so use these examples as a reference, see where they succeed/breakdown, and make sure your final submissions adhere to the rubric for this year.

Slides: (1) (2) (3)

Posters: (1) (2)

Poster session and posters: (1)

Walkthroughs: (1) (2)

Final pitches: (1)


Must be completed in studio.

Team Assessment (one per team, do it together)

Self Assessment