HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 Period. Documentation - User Test 2"

From IS480
Jump to navigation Jump to search
 
(4 intermediate revisions by one other user not shown)
Line 36: Line 36:
 
! style="font-size:14px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="100px"| [[IS480 Team wiki: 2015T2 Period. Documentation - User Test 1| <span style="color:#3d3d3d">USER TEST 1</span>]]
 
! style="font-size:14px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="100px"| [[IS480 Team wiki: 2015T2 Period. Documentation - User Test 1| <span style="color:#3d3d3d">USER TEST 1</span>]]
 
! style="padding:0.25em;  font-size:100%; text-align:center; border-bottom:3px solid #696969;border-right:3px solid #696969;border-left:3px solid #696969; background-color:#ffffff; " width="30%"| USER TEST 2
 
! style="padding:0.25em;  font-size:100%; text-align:center; border-bottom:3px solid #696969;border-right:3px solid #696969;border-left:3px solid #696969; background-color:#ffffff; " width="30%"| USER TEST 2
 +
! style="font-size:14px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="5px"|
 +
! style="font-size:14px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="100px"| [[IS480 Team wiki: 2015T2 Period. Documentation - User Test 3| <span style="color:#3d3d3d">USER TEST 3</span>]]
 
|}
 
|}
 
<!---------------END of sub-header ---------------------->
 
<!---------------END of sub-header ---------------------->
Line 270: Line 272:
 
<br><br>
 
<br><br>
  
<b>home</b><br>
+
<b>Home</b><br>
 
<center>[[Image:Ut2home.JPG|600px]]</center>
 
<center>[[Image:Ut2home.JPG|600px]]</center>
 
For the Home page, we can see that many testers found the home page rather messy and overloaded with information.
 
For the Home page, we can see that many testers found the home page rather messy and overloaded with information.
Line 288: Line 290:
 
Our team have decided to implement changes for issues that has a severity level of at least 3 or those that resulted in a significant difference between the testers' timing and the expert's timing. Thus, these are the changes we have decided to make.<br><br>
 
Our team have decided to implement changes for issues that has a severity level of at least 3 or those that resulted in a significant difference between the testers' timing and the expert's timing. Thus, these are the changes we have decided to make.<br><br>
  
<b>1. To inform user that they have to select a date first, before clicking on the "Add Period" button</b><br>
+
<b>1. To return a prompt if a date is not selected</b><br>
Most testers click on the "Add Period" button first, expecting an event to happen to allow them to add a period. However, our application is designed such that users have to select a date first, before clicking on the button. Due to that, our team have included a message to prompt the user to select a date first, before clicking on the button. Thus, this will prevent users from tapping on the button first, without selecting a date.<br><br>
+
Most testers click on the "Add Period" button first, expecting an event to happen to allow them to add a period. However, our application is designed such that users have to select a date first, before clicking on the button. Due to that, our team have decided to prompt the user to select a date before clicking on the button.
 +
<center>[[Image:Calbeforeandafter.JPG|600px]]</center>
 +
<br><br>
  
 
<b>2. Allow the adding of period in "Period Log" page</b><br>
 
<b>2. Allow the adding of period in "Period Log" page</b><br>
Most testers head to the "Period Log" expecting to add a period there. However, our previous design did not allow users to add a period on that page. We have decided to include the adding of period functionality for the "Period Log" page. <br><br>
+
Most testers head to the "Period Log" expecting to add a period there. However, our previous design did not allow users to add a period on that page. We have decided to include the adding of period functionality for the "Period Log" page.  
 +
<center>[[Image:Logbeforeandafter.JPG|600px]]</center>
 +
<br><br>
  
 
<b>3. Reduce words on news feed to avoid clustering</b><br>
 
<b>3. Reduce words on news feed to avoid clustering</b><br>
Line 301: Line 307:
  
 
<b>5. Include a spinner for loading of news feed</b><br>
 
<b>5. Include a spinner for loading of news feed</b><br>
While waiting for the news feed to load, testers wanted a spinner to at least show that it is in process of loading. With that, our team will be implementing a spinner for the loading of our news feed on the Home page.<br><br>
+
While waiting for the news feed to load, testers wanted a spinner to at least show that it is in process of loading. With that, our team will be implementing a spinner for the loading of our news feed on the Home page.
 +
<center>[[Image:Homebeforeandafter.JPG|600px]]</center>
 +
<br><br>

Latest revision as of 16:30, 19 April 2015


Phome.png Home Poverview.png Project Overview Pmanagement.png Project Management Pdoc.png Documentation Pteam.png The Team
Diagrams Prototype Testing Project Documents
INTERNAL TESTING USER TEST 1 USER TEST 2 USER TEST 3

Description

Number of Users: 30 users
Gender: Female
Venue: At user's convenience
Date: 13 to 14 Mar 2015
Duration: 15 minutes per user
Test Platform: iPhone 6 (Provided by team)
Questionnaire Platform: Hard copy

Objectives

  • To compare the time users take carrying out the tasks, to the time of our experts
  • To identify tasks that take a significantly longer duration for users as compared to experts
  • To detect issues that users face in using our application
  • To learn more about the good and bad aspects of our application
  • To gather feedback regarding the usability of our application
  • To further improve our application based on the test results

Scope

  • Onboarding
    • Create account
  • Period Tracker
    • View countdown
    • View cycle stage
    • Manage symptoms
    • View promotions
  • Calendar
    • View calendar
    • Manage periods
  • Profile
    • Manage period log
    • Manage notifications
    • Manage profile
    • Sync calendar


Timeline

Phase Date Range Description
Pre-test 09 to 12 Mar 2015
  • Sourcing for users
  • After sourcing, an email will be sent to confirm venue and timing
Test 13 to 14 Mar 2015
  • Users will use team’s iPhone to carry out the user test


Documentations


User Test 2 (UT2) Consolidated Results

Methodology

As our testers carry out the 8 different tasks, our team takes their timing down, along with some observations by the team. These observations may include issues that are faced by the testers, or incorrect clicks by testers to carry out the tasks. In addition to that, the team also collects comments regarding usability and functionality from the testers.

These results are then compared to our expert's timing (Our team's timing in conducting the tasks). Differences between the average testers' timing and the expert's timing that is calculated to be above 300% will be considered as significantly different by our team, and thus we will look into the cause of such huge differences.

Quantitative Results

Task 1: Find out the Number of days to period/Period day number

Task1.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
12.2s 13.5 3.5s 247%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is 247%. As this is not above 300%, it will not be of main concern to our team.


Task 2: Add a past period

Task2.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
47.1s 29.2 10.1s 366%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is 366%. As this is above 300%, our team have decided to look into the cause. As from our observations, we see that there are two main reasons for this huge difference and they are:

  • Tester presses the "Add Period" button on calendar and expect the adding of period to be triggered. However, our application is designed such that a date has to be selected before tapping on that button.
  • Testers head to the "Period Log" page as they feel that it where they can add a past period because of the word "Log". However, users are not given an option to add a past period in that page.




Task 3: Log your symptoms with these inputs

Task3.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
22.5s 10.0 12.9s 74%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is just 74%. This shows that testers have no issues with this task.


Task 4: Edit and put your last name as “SMU”

Task4.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
8.5s 5.1 6s 41%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is just 41%. This shows that testers have no issues with this task.


Task 5: Turn on the notification to inform you about your period 3 days before it arrives

Task5.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
9.4s 5.8 6.5s 44%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is just 44%. This shows that testers have no issues with this task.


Task 6: View the latest promotion and news

Task6.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
18.3s 22.6 3.2s 471%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is 471%. As this is above 300%, our team have decided to look into the cause. As from our observations, we conclude that the one main reason for this huge difference is:

  • Tester do not know that the latest news and promotions is on the home page because information is too clustered and unclear to them.




Task 7: Sync your period calendar to iCal

Task7.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
9.1s 5.6 6.3s 43%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is just 43%. This shows that testers have no issues with this task.


Task 8: Find out your cycle stage

Task8.JPG
Average time by participants (s) Standard Deviation of participants Expert timing % Differences between average and expert time
24.7s 22.4 10.6s 133%

As seen from above, the percentage difference between the average testers' timing and the expert's timing is 133%. This shows that testers have no major issues with this task.

Qualitative Results

Severity Ratings
To evaluate the severity of our qualitative results, we will be looking at:

  • The frequency with which the problem occurs: Is it common or rare?
  • The impact of the problem if it occurs: Will it be easy or difficult for the users to overcome?
  • The persistence of the problem: Is it a one-time problem that users can overcome once they know about it or will users repeatedly be bothered by the problem?

With that, we will be categorizing issues into these 5 severity rating levels.

Severity ratings.png



Onboarding

Ut2onboarding.JPG

For the Onboarding process, we can see that many testers had issues with the scroller for the cycle length choice. They found that the scroller was hard to use and not sensitive.

Home

Ut2home.JPG

For the Home page, we can see that many testers found the home page rather messy and overloaded with information.

Calendar

Ut2cal.jpg

For the Calendar page, many users pressed the "Add Period" button and expected a period to be added. However, our application is designed such that users must select a date first.

Me

Ut2me.JPG

Overall, there are no issues with this page.

Changes from UT2

Our team have decided to implement changes for issues that has a severity level of at least 3 or those that resulted in a significant difference between the testers' timing and the expert's timing. Thus, these are the changes we have decided to make.

1. To return a prompt if a date is not selected
Most testers click on the "Add Period" button first, expecting an event to happen to allow them to add a period. However, our application is designed such that users have to select a date first, before clicking on the button. Due to that, our team have decided to prompt the user to select a date before clicking on the button.

Calbeforeandafter.JPG



2. Allow the adding of period in "Period Log" page
Most testers head to the "Period Log" expecting to add a period there. However, our previous design did not allow users to add a period on that page. We have decided to include the adding of period functionality for the "Period Log" page.

Logbeforeandafter.JPG



3. Reduce words on news feed to avoid clustering
Many testers find the news feed very clustered and some could not find the feed because of that. To solve the issue, we have decided to limit the header to just one-liner concise sentences. With that, the news feed will not appear so clustered anymore.

4. Reduce lag on application
Many testers find the loading of the application rather slow because of the news feed. With this, our team developers have reviewed our codes to make it more efficient and thus, reducing the lag for the application.

5. Include a spinner for loading of news feed
While waiting for the news feed to load, testers wanted a spinner to at least show that it is in process of loading. With that, our team will be implementing a spinner for the loading of our news feed on the Home page.

Homebeforeandafter.JPG