cs247

CS247 Final Presentations
Wednesday, June 4, 6-8:30pm at the Place yet to be determined

Your final presentation is an opportunity to share your project with the teaching team (for grading), celebrity judges (for project awards), your classmates, coaches, and guests from campus and industry. Your team should put together a compelling presentation and demo that communicates your process and results for the quarter. Specifically, your group should prepare the following:

Final working demo, to be graded in class on June 3

Each group will give a final demo in class. You will have a 5-minute time slot to give a demo to the teaching team in any format you would like. Think of this as how you will present your project to the guests at the final presentation. It would be best to engage the participants to be part of the demo, so that they get hands on experience with your project. Note that grading the implementation part of your final project grade (5%) will be completed during this grading session, so the final version of your working prototype must be ready for this grading session. This will also ensure that things will be ready for the final presentation the next day.

A 60-second (1 minute) presentation

Each group will be given one minute to pitch their project. Use this time to communicate the big picture for your project: what user needs does your project address, and how does your design solution address them? Obviously, you will not have time to communicate all the details. Rather, think of the presentation as a chance to engage the audience so that they will be excited to learn more from your poster and demo. There is no room for "fluff"! The format of the presentation should be:

You should script your presentation and practice it many times. The final presentation slide deck will be automatically timed so that no team will be allowed to go over your allotted time!

A 20"x30" poster describing what you learned from the use studies of your project

Your poster should go into greater detail on the use studies of your project. The poster should introduce the project so visitors can understand what the project is about as they walk up to the poster. Use the poster to tell what you learned from the use studies and how that affected your design process and the final application. What is the user need? What insights did learn from use studies? How did that lead to design aspects of your application?

For each of the above, provide only the salient highlights on your poster – you do not have room to go into excruciating detail. Avoid being text-heavy. Use photos, screenshots, and sketches to help communicate your process.

To help get started, keeping in mind that previous years did not have the use study focus that we are asking for this year, you may be interested in viewing CS247 2013 teams and a CS147 example. The poster should be printed out and mounted on a stiff backing so that it can stand alone on easel next to your demo station.

Where do I get the poster?

If you have a Costco card or access to one, we recommend Costco, which charges $24.99 for a 20"x30" posterboard (with a stiff backing, which solves the mounting problem) with 1-2 day turnaround. You can order online and pick up the posterboard at the Mountain View Costco.

Alternatively, you can print at Meyer and pick it up on campus. Printing at Meyer is $50 per poster and has a 3 business day turnaround.

Finally, you can try FedEx Office (previously named Kinko's), though we haven't been able to confirm pricing or availability there, or find your own printing service.

If you choose Meyer or FedEx, you will have to mount your poster somehow. That's up to you.

A short demonstration of your application

As guests visit your poster, each team member should be prepared to describe your project and provide a short demo (roughly 2-3 minutes). Think through how you are going to explain your application to people.

Remember to motivate why you built the app you did. Describe the experience you intended to enable, show your application, and then describe what is unique about your approach along with any salient results from use studies. Think about setting up the context, the task, and the set up of the application so that the visitor will have a compelling first hand experience with your application. This demo experience is what the celebrity judges will be using to designate project awards at the end of the evening.


Grading Rubric

Check minus Check Check plus
Implementation Unexplained demo failures, flaws in UI flow or logic in accomplishing core tasks, demo hard to followDemo performed as expected, accomplishing core tasks was clear and well designed, clear setup of demo Highly functional and polished UX, clever demo setup to engage visitor
Presentation Unclear communication of the goals of the project orhow the prototype worked3-line scene set up the user need and context, video showed how the prototype met the user need Creative, engaging 3-line scene, creative video demo of how the prototype worked
Poster Unclear about the main insights learned from use studies, did not demonstrate findings through evidence, did not connect with design changes or features in the prototype, hard to browse information from poster designHighlighted main insights from use studies with evidence collected from the studies, related to design features in the prototype, appropriate poster layout and design Clean and attractive layout and presentation of use study insights, data, and design implications
Design Solution Unconvinced about user need or how the prototype fulfilled it, missed opportunities to use the design process to refine project idea Clearly expressed user need and the demo, user study, and presentation worked together to demonstrate that the prototype fulfilled it, responded to insights from the design process to refine project idea Took initiative throughout the design process to refine the project to meet the user need and create a polished UX

Action Items

Poster Session Setup

You should bring your physical poster to the demo site prior to the start of the poster session. We will provide easels for the posters. Please come a half hour early, at 5:30pm, to get set up.

Post-Course Reflection

After the poster session, we'd like each of you to reflect on your project and your experiences in the class, including your working dynamics of your P4 final project team. Please fill out the Google Form by 10am on Thursday, June 5. Note that this is an individual assignment, not a group assignment.

The form will ask you to reflect on what you learned through the design process this quarter, what you would change about the course, and the distribution of work on your project team. This is an opportunity to give kudos to team members who went above and beyond, or flag areas in which individual contributions or team dynamics might have been improved.

Reflections are due on Thursday 6/5 by 10am. You should address the following questions: What provided the most valuable learning experiences in the course? What would you change about your own design process if asked to do it again? What would you change about the course itself? Finally, please also comment on the distribution of work on your project team.

 


Please feel free to e-mail us at cs247@cs.stanford.edu if you have any questions.