CS247 - Human Computer Interaction Design Studio - Winter 2010 - Winograd/Verplank/Raffle

CS247 - The final push [revised version - additions in bold italic]

Here is a summary of what is needed for the end of the course:

1. Three minute presentation for Monday evening March 15

You will have three minutes to present and a couple more for questions/comments from the audience. Time will be enforced. For this presentation, emphasize what your design does, and how it developed through testing. Don't include a lot on all the steps of your process (brainstorming, etc.) Make it fun, but substantive (not just an infomercial).

In order to make the transitions smooth, we need to have all of the presentations (either slides or videos) loaded on one computer so there isn't a plugging/unplugging delay. Send them to Maria by Sunday midnight, so she can get them organized. I would suggest sending the slides as a PDF if you're not sure that the fonts will be the same, or you're using anything but Powerpoint. Videos can be uploaded to YouTube and send her a URL.

1.5 Poster to go with your demo for Monday evening March 15

You have all signed up for spaces for your demos. In that space you should have a poster so that someone who walks up and reads it but doesn't talk to you will have an idea of what you did, what's special about it, and what were the most interesting lessons and changes that came from prototyping and testing. You don't need a lot of detailed print: a few pictures/diagrams and bullet points.

2. Optional presentation at Nokia Thursday noon, March 18

For those groups that can, there will be a presentation for an audience that includes the head of Nokia research. Let Hayes know if you'll be able to do it. It only requires one team member.

3. Idea logs Monday evening March 15

Bring your logs to the final presentations and we'll collect them. We're planning to do grade them the next day, so don't forget.

Put postits to mark the places where the log led to new designs/insights. It is OK to include paste-ins of whiteboards, photos, etc. If they are done in a group, then mark them as so. For more, see the handout on idea logs.

4. Web site with materials from your project. SEND US THE URL by Friday March 19

Here is Hayes' message he sent out last week:

Hey class,

I know your projects are getting into the swing of thing, and you probably are already having a lot of documentation building up about your research with users, design documents, etc. Start thinking about which of these are really interesting snapshots into your process, because as one component of your final project, we'd like your team to create a web page or series of pages that document your work. We'll put it on the website for future classes to see what happens in cs247, and you may also like to point to it to show other people what kind of work you've done in the past.

Your final web page(s) should include:

• team name and members
• project name
• project goals
• video of your final project (I recommend a 2 minute video)
• process: not quite an online "idea log" but a snapshot of the process, e.g. photos / drawings of ideation, testing, prototyping, and the final project.
• USER TESTING SUMMARY: about a page overall, which lists the tests you did (who, when, where, what prototype) and the main lessons you learned from each.

Some teams may already be using online tools (blogs, google docs, email) as a way to communicate through the design process. If you keep these materials organized, they can feed right into the web page. For instance, the soundscrambler team kept a blog as they worked last year, and just submitted that as their final web page. http://cs247-2009.blogspot.com/ The web pages will be due at the end of the quarter.

You are welcome to use whatever tools are most convenient for you. We'll ask you to submit your html and supporting documents in a folder to us. You've all likely seen at least one or two project web pages at the class website from last year's class. What will you share about your project with future cs247 students and enthusiasts?

Happy prototyping!

5. Individual Team Writeup emailed to staff by Friday March 19

This is not to be taken as a chance to rant. Instead, it should be seen as a chance to exercise your constructive critiquing skills. You should write the critique as if your fellow group members would read it, although we will not share these with your fellow group members. We do not forbid you from sharing them, however. The goal is to give you experience in reflecting on a group work process and constructively evaluating your own performance as well as the performance of the others in your group. If you feel that dimensions outside of your group (e.g., TA, class organization, instructors) contributed positively or negatively to the process, please include these. However, the focus should be mostly on your group's dynamics.

The length should be no more than 500 words. Remember, this is to be a reflective and constructive evaluation of activities and contributions all around.

6. Bringing back materials by Friday March 19

Anything you bought on class funds that isn't expendable should be brought back (especially the Arduino kits, etc.). You can drop them off during daytime hours with Monica Niemec in Gates 366.