HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 ByteMe User Testing"

From IS480
Jump to navigation Jump to search
 
(11 intermediate revisions by the same user not shown)
Line 14: Line 14:
  
 
<!--Banner Start-->
 
<!--Banner Start-->
[[File:ByteMe_Project_Documentation.png |900px|center|link=]]
+
[[File:ByteMe_Project_Documentation.png |900px|center|link=IS480 Team wiki: 2016T1 wiki testing]]
 
<!--Banner End-->
 
<!--Banner End-->
  
Line 28: Line 28:
  
 
<!--Body-->
 
<!--Body-->
<div style="background: #ffc113; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size: 32px;padding-top:25px"><font color=#FFFFFF>User Test 1</font></div>
+
 
 +
<div style="background: #ffc113; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size: 32px;margin-top:25px"><font color=#ffffff>User Test 1</font></div>
 +
[[IS480 Team wiki: 2016T1 ByteMe Main Page Test| <font face = "Arial" color="#000"><b><u> Main Page Test</u> </b></font>]]
  
 
==Test Plan 1 (Admin)==
 
==Test Plan 1 (Admin)==
Line 50: Line 52:
 
* User Interface is good, but some parts be improved on. Ideas and suggestions were given.
 
* User Interface is good, but some parts be improved on. Ideas and suggestions were given.
  
<b>Action Plan</b></br>
+
<b>Action Plan</b>
 
* Front-end development fixes were given to Michael.
 
* Front-end development fixes were given to Michael.
 
* Bugs were recorded and the team would fix the bugs accordingly.
 
* Bugs were recorded and the team would fix the bugs accordingly.
 
* The term function would have to be re-done.
 
* The term function would have to be re-done.
 
 
  
 
==Test Plan 1 (Student)==
 
==Test Plan 1 (Student)==
Line 79: Line 79:
 
<b>Action Plan</b><br>
 
<b>Action Plan</b><br>
 
* Bugs were recorded and the team would fix the bugs accordingly.
 
* Bugs were recorded and the team would fix the bugs accordingly.
 +
* Added HTML Function to make the project much easier to read
 +
 +
==Test Plan 2 (Admin)==
 +
<b>Number of Users: </b>4<br>
 +
<b>Date: </b>19th August 2016<br>
 +
<b>Venue: </b>SMU SR 2-3<br>
 +
<b>Duration: </b>30 mins per user<br>
 +
<b>Objectives: </b><br>
 +
* Analysing the usability of the Application (User Interface, Navigation Ease, etc.)
 +
* Improving the Overall Feel of new functions
 +
<b>Scope: </b><br>
 +
* Faculty Management
 +
* Export Functions
 +
* Notification Module
 +
<b>Procedure: </b>Users are given a document which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
* thoughts on the new functions was given, overall average results.
 +
* Ideas were given to improve usability and improve the navigation of coordinator function.
 +
 +
<b>Action Plan</b>
 +
* Front-end development fixes were given to Michael.
 +
* We intend to make the faculty management from 3 different navigation tabs into 1.
 +
 +
==Test Plan 2 (Student)==
 +
<b>Number of Users: </b>5<br>
 +
<b>Date: </b>15th August 2016<br>
 +
<b>Venue: </b>SMU Labs<br>
 +
<b>Duration: </b>Around 30 mins per user<br>
 +
<b>Objectives: </b><br>
 +
* Observation of user behavior when using our application
 +
* Identify usability issues that exist in the application
 +
* Improve our application based on user testing result
 +
<b>Scope: </b><br>
 +
* SSO Login using your SMU Account details
 +
* Edit their Student Details
 +
* Create/Join Team
 +
* Request to take up a Project
 +
<b>Procedure: </b>Users are given a document which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
* Many did not know how to accept a team invitation.
 +
* User Interface has improved, but still not acceptable to our team.
 +
 +
<b>Action Plan</b><br>
 +
* Intend to do a A/B Testing in our next user test.
 +
* Added a notification module to notify users of pending invitations.
 +
<!--Body End-->
 +
 +
==Test Plan 3 (Student)==
 +
<b>Number of Users: </b>13<br>
 +
<b>Date: </b>26th September 2016<br>
 +
<b>Venue: </b>SIS Classroom 3-1<br>
 +
<b>Duration: </b>Around 30 mins per user<br>
 +
<b>Objectives: </b><br>
 +
* Get better results for user test 3 after completing user testing 2
 +
* Identify usability issues that exist in the application
 +
* Improve our application based on user testing result
 +
<b>Scope: </b><br>
 +
* SSO Login using your SMU Account details
 +
* Edit their Student Details
 +
* Create/Join Team
 +
* Request to take up a Project
 +
* A/B Testing to determine a better colour scheme
 +
<b>Procedure: </b>Users are given a document which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
<b>Results from A/B Testing</b>
 +
[[File:Byteme_abtesting_results.png |600px|center|link=]]
 +
From the A/B Testing on 4 different colour schemes. There was 3 who preferred our original colour scheme, 6 preferred the B's colour scheme, 3 preferred C's colour scheme and 1 preferred D's colour scheme. The result was conclusive with more people preferred B's colour schemme.
 +
 +
<b>Other Results</b>
 +
* 11/13 users did not find any problem with doing the basic process flow. (Rated Easy and Very Easy in the survey)
 +
* 10/13 users felt that creating team process was intuitive (Rated Easy and Very Easy in the survey)
 +
* 9/13 users felt that the system was intutive when they are proposing a project (rated Easy and Very Easy in the survey).   
 +
* From this user test, it can be seen that the usability of the is480 management has significantly improved, in addition, that our system was easy to use as the icons, naming, etc. was clear and well understood.
 +
 +
<b>Action Plan</b><br>
 +
* Intend to change color scheme of the current is480 system to the same color scheme as B. This would be allocated to Michael and Yingnan who are the UI/UX Analyst.
 +
* User Test 4 will be focusing on improving the user test results for basic process flow, creating a team and proposing a project. In addition to these functionalities, we will add the IS480 information survey function for users to test.
 +
* We intend to also solve some bugs which we were able to discover in User test 3. The list has been given to Huimin, Chong Wei and Kun Sheng to complete.
 +
<!--Body End-->
 +
 +
==Test Plan 4 (Student)==
 +
<b>Number of Users: </b>33<br>
 +
<b>Date: </b>1st November 2016<br>
 +
<b>Venue: </b>SIS Classroom 3-1<br>
 +
<b>Duration: </b>Around 30 mins per user<br>
 +
<b>Objectives: </b><br>
 +
* Observation of user behavior when using our application
 +
* Identify usability issues that exist in the application
 +
* Improve our application based on user testing result
 +
* Calculate the time taken for each process.
 +
<b>Scope: </b><br>
 +
* SSO Login using your SMU Account details
 +
* Edit their Student Details
 +
* Create/Join Team
 +
* Request to take up a Project, with admin accepting/rejecting projects
 +
* Do the IS480 Information Survey
 +
<b>Procedure: </b>Users are given a document which contains information on how to go about with the user testing.<br>
 +
 +
<b>Results & Comments</b><br>
 +
* 22/26 users felt it was easy to navigate through the whole IS480 System (Rated 7 or more out of 10 in the survey)
 +
* 25/26 users felt that viewing and updating their own IS480 student profile is very simple and intuitive (Rated 7 or more out of 10 in the survey)
 +
* 22/26 users felt that creating, inviting and editing an IS480 group is very simple and intuitive (Rated 7 or more out of 10 in the survey)
 +
* 21/26 users felt that proposing projects and project notification for the team is very simple and intuitive (Rated 7 or more out of 10 in the survey)
 +
* 14/26 users felt that the IS480 information survey is simple and intuitive (Rated 7 or more out of 10 in the survey)
 +
* We noticed that most of the overall feedback was mostly directed at the IS480 information survey.
 +
 +
<b>Action Plan</b><br>
 +
* We intend to make the IS480 Information survey much more simple and intuitive for all users, this can be achieved by having more specific error messages, making some questions more clear, better ways of visualising the answer. This task is given to Yingnan.
 +
* We intend to also solve some bugs which we were able to discover during User test 4. The list has been given to Huimin, Chong Wei and Kun Sheng to complete.
 
<!--Body End-->
 
<!--Body End-->

Latest revision as of 11:18, 28 November 2016

ByteMe Logo.jpeg
ByteMe Home icon 2.png
ByteMe About me icon 2.png
ByteMe overview icon 2.png
Management icon.png
ByteMe Documentation icon 2.png
ByteMe Project Documentation.png
Technical Documents Design & UI/UX Process Flows Meeting Minutes User Testings


User Test 1

Main Page Test

Test Plan 1 (Admin)

Number of Users: 4
Date: 4th August 2016 & 5th August 2016
Venue: Benjamin Gan Office (SMU SIS 5034) & Fiona Lee's Office (SMU SIS 4056)
Duration: 30 mins per user
Objectives:

  • Analysing the usability of the Application (User Interface, Navigation Ease, etc.)
  • Identify any bugs or issues that users may face during the user testing.
  • Improving the IS480 application based on the user testing result.
  • Identify any other functions that the course coordinators of IS480 may find useful.

Scope:

  • Create Term
  • Create/Edit Milestones in Terms
  • Export Student-Team.csv

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • The System still contains bugs that our team did not successfully fix.
  • User Interface is good, but some parts be improved on. Ideas and suggestions were given.

Action Plan

  • Front-end development fixes were given to Michael.
  • Bugs were recorded and the team would fix the bugs accordingly.
  • The term function would have to be re-done.

Test Plan 1 (Student)

Number of Users: 7
Date: 6th August 2016 & 7th August 2016
Venue: SMU School of Information Systems
Duration: Around 30 mins per user
Objectives:

  • Observation of user behavior when using our application
  • Identify usability issues that exist in the application
  • Improve our application based on user testing result

Scope:

  • SSO Login using your SMU Account details
  • Edit their Student Details
  • Create/Join Team
  • Request to take up a Project

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • There were some bugs in the system, but none serious.
  • User Interface is good, but some parts be improved on. Ideas and suggestions were given.

Action Plan

  • Bugs were recorded and the team would fix the bugs accordingly.
  • Added HTML Function to make the project much easier to read

Test Plan 2 (Admin)

Number of Users: 4
Date: 19th August 2016
Venue: SMU SR 2-3
Duration: 30 mins per user
Objectives:

  • Analysing the usability of the Application (User Interface, Navigation Ease, etc.)
  • Improving the Overall Feel of new functions

Scope:

  • Faculty Management
  • Export Functions
  • Notification Module

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • thoughts on the new functions was given, overall average results.
  • Ideas were given to improve usability and improve the navigation of coordinator function.

Action Plan

  • Front-end development fixes were given to Michael.
  • We intend to make the faculty management from 3 different navigation tabs into 1.

Test Plan 2 (Student)

Number of Users: 5
Date: 15th August 2016
Venue: SMU Labs
Duration: Around 30 mins per user
Objectives:

  • Observation of user behavior when using our application
  • Identify usability issues that exist in the application
  • Improve our application based on user testing result

Scope:

  • SSO Login using your SMU Account details
  • Edit their Student Details
  • Create/Join Team
  • Request to take up a Project

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • Many did not know how to accept a team invitation.
  • User Interface has improved, but still not acceptable to our team.

Action Plan

  • Intend to do a A/B Testing in our next user test.
  • Added a notification module to notify users of pending invitations.

Test Plan 3 (Student)

Number of Users: 13
Date: 26th September 2016
Venue: SIS Classroom 3-1
Duration: Around 30 mins per user
Objectives:

  • Get better results for user test 3 after completing user testing 2
  • Identify usability issues that exist in the application
  • Improve our application based on user testing result

Scope:

  • SSO Login using your SMU Account details
  • Edit their Student Details
  • Create/Join Team
  • Request to take up a Project
  • A/B Testing to determine a better colour scheme

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments
Results from A/B Testing

Byteme abtesting results.png

From the A/B Testing on 4 different colour schemes. There was 3 who preferred our original colour scheme, 6 preferred the B's colour scheme, 3 preferred C's colour scheme and 1 preferred D's colour scheme. The result was conclusive with more people preferred B's colour schemme.

Other Results

  • 11/13 users did not find any problem with doing the basic process flow. (Rated Easy and Very Easy in the survey)
  • 10/13 users felt that creating team process was intuitive (Rated Easy and Very Easy in the survey)
  • 9/13 users felt that the system was intutive when they are proposing a project (rated Easy and Very Easy in the survey).
  • From this user test, it can be seen that the usability of the is480 management has significantly improved, in addition, that our system was easy to use as the icons, naming, etc. was clear and well understood.

Action Plan

  • Intend to change color scheme of the current is480 system to the same color scheme as B. This would be allocated to Michael and Yingnan who are the UI/UX Analyst.
  • User Test 4 will be focusing on improving the user test results for basic process flow, creating a team and proposing a project. In addition to these functionalities, we will add the IS480 information survey function for users to test.
  • We intend to also solve some bugs which we were able to discover in User test 3. The list has been given to Huimin, Chong Wei and Kun Sheng to complete.

Test Plan 4 (Student)

Number of Users: 33
Date: 1st November 2016
Venue: SIS Classroom 3-1
Duration: Around 30 mins per user
Objectives:

  • Observation of user behavior when using our application
  • Identify usability issues that exist in the application
  • Improve our application based on user testing result
  • Calculate the time taken for each process.

Scope:

  • SSO Login using your SMU Account details
  • Edit their Student Details
  • Create/Join Team
  • Request to take up a Project, with admin accepting/rejecting projects
  • Do the IS480 Information Survey

Procedure: Users are given a document which contains information on how to go about with the user testing.

Results & Comments

  • 22/26 users felt it was easy to navigate through the whole IS480 System (Rated 7 or more out of 10 in the survey)
  • 25/26 users felt that viewing and updating their own IS480 student profile is very simple and intuitive (Rated 7 or more out of 10 in the survey)
  • 22/26 users felt that creating, inviting and editing an IS480 group is very simple and intuitive (Rated 7 or more out of 10 in the survey)
  • 21/26 users felt that proposing projects and project notification for the team is very simple and intuitive (Rated 7 or more out of 10 in the survey)
  • 14/26 users felt that the IS480 information survey is simple and intuitive (Rated 7 or more out of 10 in the survey)
  • We noticed that most of the overall feedback was mostly directed at the IS480 information survey.

Action Plan

  • We intend to make the IS480 Information survey much more simple and intuitive for all users, this can be achieved by having more specific error messages, making some questions more clear, better ways of visualising the answer. This task is given to Yingnan.
  • We intend to also solve some bugs which we were able to discover during User test 4. The list has been given to Huimin, Chong Wei and Kun Sheng to complete.