Team Feedback for Mid-Quarter project Displays

During our project displays today, please provide me with feedback on your impressions of the displays via the Web form at

https://docs.google.com/spreadsheet/viewformformkey=dEtpWEJnWHhENW5LX0FObW1yY0FNb1E6MA ; it is also reachable through the schedule on the class Web site. 

For each of the displays, your team can either submit multiple, individual feedback forms, or get together and submit one single form by the team as a whole. I'd also appreciate a self-evaluation of your own team; it's often a good exercise to critically examine one's own work, especially in comparison with that of others in a similar situation.

This collective feedback may influence my assignment of scores, but it is not just a simple calculation of the averages or some similar formula. I typically use it as a consistency check to make sure that my assessment is not significantly different from that of the team's peers.
0 Comments

Mid-Quarter Project Displays on May 3

For the mid-quarter project displays on Thursday, May 3 during our usual class time from 3:10 - 6:00 pm, I expect all the teams to prepare a display including the following:
- a title sheet with class number, team number (and name, if your team has one), and the topic; this should be large enough and prominently displayed so that it can be viewed easily even from across the room;
- a brief overview of the project (such as goals, context and background, intended users, approach)
 - design alternatives considered
- design artifacts (such as paper/whiteboard/computer sketches)
- prototype (low to mid fidelity; limited functionality)
- an opportunity for visitors to interact with your product, or to give feedback on the design (e.g. via a questionnaire).

For the six projects, we have the three pod-shaped tables which fit one project each, the movable tables near the wall with the one-way mirror, and the smaller participant room. That room will be used by the Morae team, and we can do the assignment of the other teams in class tomorrow. 

Since the Morae team is not really developing a product, but rather exploring the effective use of a usability evaluation tool, they are planning to do a trial run of experiments for the other teams. The plan is to offer each of the other teams a slot of about 20-30 minutes for quick experiments with their products, to be conducted using Morae and with the assistance of the Morae team. So the other teams should have a task description and evaluation plan for a simple experiment (e.g. something similar to the first assignment), and the Morae team will help them put the experiment and evaluation plan onto the Morae framework, and then run the experiment. This serves multiple purposes: First, the Morae team will gain experience in assisting others with the use of the software. Second, the other teams will get an introduction into the use of the Morae tools, and at the same time have an opportunity to collect more data for their project. Third, it is a trial run for the data collection activity in the respective Assignment 4.

We'll discuss this again in class on Tuesday next week. 

F.K.
0 Comments