HTW Berlin Fachbereich 4 Internationaler Studiengang Internationale Medieninformatik (Bachelor) WT2: Usability Winter Term 2017/18

We are not done yet! We will continue today with preparations for the usability test..

Week 1, Exercise 5a

1. What sorts of things do you want to test? We call these tasks. Write them down! For example, there might be field for logging in—what happens when you put in a wrong answer? This is a mini-test and is not the same as a scenario!
   
   
2. Prepare an exact script for your test. Which scenarios and mini-tests are you going to use? The script should be quite detailed and list the tasks that you will be asking the tester to perform. You need to give a name to every concrete task that you will be doing. It is sufficient, however, to have some sort of numbering system, T1, T2a, T2b, T3c, etc. For each task:
   
   • Define any prerequisites.
   • Define successful completion criteria.
   • Specify maximum time to complete each task, after which help may be given.
   • Define what constitutes an error.

   This task list might look like the one Keith Andrews did for Harmony. The first test should be one that the user can do successfully, so that they don't think that they are stupid! The tasks should be in a realistic and in a typical order for using the site to complete the scenario. If sequential ordering is not crucial, then randomize the presentation order in order to counterbalance any learning effect. Put each task scenario on a separate sheet of paper, you will hand them to the user one at a time! Example: Using the 3D landscape, navigate to the collection about the city of Graz and open it (please do not use a search query for this task). You will need at least as many task sequences as you have persons in your group. Prepare a few extra, just in case you are done early.

1. What do you expect the reactions of the users to be for each concrete test? Assign shorthand codes to expected activities so that you have a list available. This will help you in recording what happens during the test.

2. Now prepare your test plan. This is a written document that has the following sections:
   
   1. Purpose of the test
   2. Problem Statement
   3. Background Questionnaire*
   4. User Group Profile* and example personal scenarios
   5. Method (Test Design)*
   6. Task List (this is from last week)
   7. Test Environment*
   8. Data to be Collected (prepare a checklist and a form to fill out during the formal evaluation)
      
      * These are documents you have previously prepared and submitted.
      
      
3. When you are finished with a test series you will want to interview the test person. For this you will need either a questionnaire for the tester to fill out after the test, or a debriefing topic guide, so that you don't forget to ask the user anything important. You will also need a checklist for the entire test—Prepare this now!
   
   
4. Make sure that you have everything available that you will need for the next exercise:
   • Test Materials
   • Nondisclosure Form
   • Orientation Script
   • Training Script (if any)
   • Task Scenarios
   • Data Collection Forms
   • Post Test Questionnaire or Debriefing Topic Guide
   • Checklist

All materials should be printed and ready to go when you begin the formal evaluation next week (please be on time!).

Your collected documents need to be posted to the Moodle room by 22.00 the night before the formal evaluation.

At least one member of the group needs to have a stopwatch or digital watch that can count seconds with them for the formal evaluation!

Some rights reserved. CC-BY-SA 2017 Debora Weber-Wulff (weberwu@htw-berlin.de)