{"id":1986,"date":"2017-11-24T14:15:41","date_gmt":"2017-11-24T19:15:41","guid":{"rendered":"http:\/\/cs4760.csl.mtu.edu\/2018\/?page_id=1986"},"modified":"2018-12-15T13:33:15","modified_gmt":"2018-12-15T18:33:15","slug":"usability-test-assignment-2-usability-test-schedule","status":"publish","type":"page","link":"http:\/\/cs4760.csl.mtu.edu\/2019\/usability-test-assignment-2-usability-test-schedule\/","title":{"rendered":"Project Evaluation and Usability Test Assignment 2 \u2013 Usability Test Schedule"},"content":{"rendered":"

Scheduling<\/h1>\n

The usability test sessions must be scheduled three weeks before the actual testing because many individuals must be coordinated and space made available. Your CS\u00a0team\u00a0members must coordinate with you, and you\u00a0may also need to\u00a0coordinate with the graduate\u00a0students who are conducting usability testing on the same app. Also, space for the testing must be coordinated–we should be able to utilize the new usability lab within the HDMZ, but this is dependent on other scheduling needs.\u00a0Dr. Pastel will\u00a0seek participants for the tests, which also takes time, and you may need to round out your cadre of test participants if Dr. Pastel’s efforts don’t yield enough student volunteers.<\/p>\n

Number of Sessions and Team Assistance<\/h2>\n

You should schedule\u00a0five (5) test sessions for the thirteenth week of the semester with people who represent the target user group for the app you’re working with. Each session should be scheduled for an hour, and at least three team\u00a0members should\u00a0participate during each session. Each team\u00a0member should attend at least three\u00a0usability test sessions; the following are roles needed for the test session.<\/p>\n

    \n
  1. Test administrator\/product owner<\/span><\/strong>: Oversees the scheduling of test sessions, communicates with professors, schedules participants, reminds participants the day before. Probably plays a dual role during testing.<\/li>\n
  2. “Receptionist”: Check in, do paperwork. Someone should register the participants,\u00a0 make sure they get their extra credit, if applicable, and collect signed permission slips.<\/li>\n
  3. Observer\/explainer (HU student): Demonstrate the application to the participant; help guide them (e.g. prompt them to speak aloud as they work, if that is part of your test design).edu<\/li>\n
  4. Observer\/note-taker (HU student): Observe interactions and take notes.<\/li>\n
  5. Tech support (CS 4760 student or other designated techie): Sometimes the application does not work properly, so you will need a student to troubleshoot and repair the application, clear the cache and reset the “visited links,” etc.<\/li>\n<\/ol>\n

    When tests are conducted in the HU usability lab, extra group members can watch via video feed in the adjacent room. We’ll make sure the lab is scheduled on Tuesdays and Thursdays from 2-5 (at least) during Week 13. Other times can be arranged.<\/p>\n

    Schedule and Participant Registration Process<\/h2>\n

    The process for scheduling your usability test sessions and for participants to register for usability test sessions is:<\/p>\n

      \n
    1. Team\u00a0determines session times and testing locations.<\/li>\n
    2. When Dr. Pastel emails you access to a google\u00a0sheet called the \u201cUsability Test Sessions,\u201d enter session times, your name, the app name, and location. Make sure the information is correct and that you meet the deadline for entering the information. See Google\u00a0Sheets Details section below.<\/li>\n
    3. After the deadline for entering usability test times has passed,\u00a0Dr. Pastel will give participating instructors\u00a0 access to \u201cUsability Test Sessions\u201d google sheet instructions for using it.<\/li>\n
    4. Students from lower level classes will receive the URL for the\u201dUsability Test Sessions\u201d google sheet. They will reserve a usability test time by entering their names, emails, and the class(es)\u00a0for which they wish to receive credit for participating into the google sheet.<\/li>\n
    5. After the deadline for participants to register for usability tests has passed, teams will have access to the \u201dUsability Test Sessions\u201d google sheet.\u00a0The google sheet also contains a column for you to indicate whether the participants attended or not.<\/li>\n
    6. A day before each usability test, look up the email address of the participants and email\u00a0them a reminder of the usability test time and location.<\/li>\n
    7. After you have conducted a usability test, enter on the \u201cUsability Test Sessions\u201d google sheet whether or not the student attended your usability test session.<\/li>\n
    8. After the deadline for entering the attendance in the \u201cUsability Test Sessions\u201d google sheets has passed,\u00a0Dr. Pastel will give the participating instructors access to the \u201cUsability Test Sessions\u201d google sheet, so they can\u00a0decide who should receive credit for participating.<\/li>\n<\/ol>\n

      Google\u00a0Sheets Details<\/h2>\n

      Usability Test Sessions google sheet<\/h3>\n

      Prior to the usability testing, I will email\u00a0you access to the \u201cUsability Test Sessions\u201d google sheet\u00a0that\u00a0you will use to record a usability test sessions. The \u201cUsability Test Sessions\u201d google sheet has headings:<\/p>\n

        \n
      • Adminstrator<\/b>\u00a0\u2013 you should enter your first and last name in this field. Be consistent with the name so that later you can order the google sheet by appName and find your usability test sessions.<\/li>\n
      • Appy<\/b>\u00a0\u2013\u00a0 you should enter the app name that you are testing. Be consistent with the app name.<\/li>\n
      • Testing Date<\/strong>\u00a0\u2013 you should enter the usability test time and date. The formatting of the test date and time is very specific because\u00a0the \u201cUsability Test Signup\u201d web app will convert it to a Date object. The format is MM\/DD\/YYYY HH:MM AM or PM. For example, suppose that you wish to schedule a usability test session for April 17, 2017, at 10:05 am, then your should enter the data as 4\/17\/2017 10:05 AM. If you want to schedule the date April 19, 2017 at noon, then you would enter 4\/19\/2017 12:00 PM. The google sheet will try to validate your entry, but you are responsible for entering the correct date and time. Otherwise, the wrong date and time will be displayed in the \u201cUsability Test Signup\u201d web app.<\/li>\n
      • Location<\/strong>\u00a0\u2013 you should enter the location of the usability test. Be sure to give the room number and building so that the participant can find the location.<\/li>\n
      • Name<\/strong>\u00a0\u2013 Participants enter first and last names.<\/li>\n
      • Email<\/strong>\u00a0\u2013 Participants\u2019 emails as they entered it. Use this email address to remind participants of the usability test time and location.<\/li>\n
      • Course<\/strong>\u00a0\u2013 This is the course that the participant wishes to get extra credit for.<\/li>\n
      • Attended<\/strong>\u00a0\u2013 This is a column for you to enter weather the participant attended the usability test session or not. If the participant attended then enter \u201cyes\u201d. If not then enter \u201cno\u201d.<\/li>\n<\/ul>\n

        Enter this information correctly, or the data will not display properly in the \u201cUsability Test Signup\u201d web app.<\/p>\n

        <\/h2>\n","protected":false},"excerpt":{"rendered":"

        Scheduling The usability test sessions must be scheduled three weeks before the actual testing because many individuals must be coordinated and space made available. Your CS\u00a0team\u00a0members must coordinate with you, and you\u00a0may also need to\u00a0coordinate with the graduate\u00a0students who are conducting usability testing on the same app. Also, space for the testing must be coordinated–we […]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1986","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/pages\/1986","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/comments?post=1986"}],"version-history":[{"count":18,"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/pages\/1986\/revisions"}],"predecessor-version":[{"id":2315,"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/pages\/1986\/revisions\/2315"}],"wp:attachment":[{"href":"http:\/\/cs4760.csl.mtu.edu\/2019\/wp-json\/wp\/v2\/media?parent=1986"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}