User Testing (final reminder!)

Brent J. Dahlen (dahlen@cs.umn.edu)
Sun, 22 Feb 1998 13:58:53 -0600 (CST)

Date: Sun, 22 Feb 1998 13:58:53 -0600 (CST)
From: "Brent J. Dahlen" <dahlen@cs.umn.edu>
To: "Sun 1:00 Group 7" <ameet@wonderwonks.com>, asbu0003@itlabs.umn.edu,
Subject: User Testing (final reminder!)
Message-Id: <Pine.GSO.3.95q.980222135812.9282A-100000@nebula.cs.umn.edu>

Reminder:

User testing is due by Monday--that's tomorrow! If
you haven't contacted your assigned group yet, I strongly urge
you to do so. Failure in this regard will greatly affect your
group grade. I've received several comments from some group
members that say their assigned group hasn't responded yet
(Groups 0 & 8 were mentioned).

Remember, at this point you're probably looking at meeting
sometime this weekend or Monday (if you haven't met already).
That's not much time and your assigned group may have conflicts.
If not all of your members can make the meeting, make sure that
those missing go through the testing process by setting up an
alternative time with a few of the other group's members. That's
all I'll say on this--I shouldn't have to beg you to get this done!
Ideally, this should be looked at as an excellent opportunity
to see if your design is as intuitive as you probably think it
is. Remember--you *want* to pinpoint errors, so make sure you
log everything the user is hesistant or confused about, etc.

Besides the testing itself, you have the following due by next
week's meeting:

o Heuristic Eval. Done individually. Look at each of the
Nine Heuristics and write a paragraph of analysis on
each based on your current system prototype. As always,
keep a separate report of problems found and possible
solutions.

o Critique of the Other Group's System. Based on your
testing experience in front of their system. Emphasize
problems with possible solutions, citing the design
principles wherever appropriate.

A group heuristic eval is due at the end of the term and should
go in your group's Final Project Report. I would suggest getting
together soon after doing the individual reports--the following
week you will be asked to collect and prioritize ALL problems
with their solutions based on all the problem reports you will
get from the group walkthrough, user testing, and the group heuristic
evals, so that group report needs to be done in the next week or
so.

Let me know if you are having any problems with testing or
otherwise. Be prepared to discuss the process in next week's
meeting. Good luck.

Brent