HeaderSIS.jpg

IS480 Team wiki: 2016T2 LickiLicky User Test and Survey User Test 4

From IS480
Jump to navigation Jump to search

LickiLicky Logo v2.png

HOME   ABOUT US   PROJECT OVERVIEW   PROJECT MANAGEMENT   DOCUMENTATION
Technical Documents Design Documents User Test & Survey Meeting Minutes Course Deliverables


User Test & Survey
User Test 1 User Test 2 User Test 3 User Test 4 User Test 5
User Test 4

Test Plan

Number of Users: 11
Date: 7 March 2016 - 16 March 2016
Venue: Anywhere convenient for the Financial Consultants and LickiLicky
Duration: 45-90mins
Objectives:

  • Discover impact of existing functions, planned improvements & features
  • Receive suggestions for improvements and new functions and gather feedback on them
  • Determine if using Tictacts improves productivity by collecting specified task timings

Scope:

  • Contacts & Notes
  • Reminder & Notification
  • Create Event
  • Attach Media to Notes
  • Hashtag & Mention
  • Birthday Reminder
  • Filter Search

Action Table for Existing Functions

Score Description Action
6.00 - 7.00 Very useful GOOD! 👍
4.00 - 5.99 Slightly useful Ask for improvements to the existing function
0.00 - 3.99 Not useful Feature is not useful, stop improvements and consider removing it feature list after FYP

Action Table for Planned Functions & Improvements

Score Description Action
6.00 - 7.00 Very useful Add to plan feature list and collect more data
4.00 - 5.99 Slightly useful Ask why they suggested it then. Review and include if effort is low and passes the feature threshold
0.00 - 3.99 Not useful If it is a interface or usability issue, then backlog it.If feature, then nevermind it.

Action Table for New Functions & Improvements

Score Description Action
6.00 - 7.00 Very useful Feature is useful and no action is needed
4.00 - 5.99 Slightly useful Can become useful if it is improved. Calculate score with the improved feature impact to determine whether to do it.
Place the improved feature above the original feature for rating to avoid bias. Cannot be improved. Get more data.
0.00 - 3.99 Not useful Feature is not useful and remove it from planned features list

Procedure: xxx

Results & Analysis

Details of participants:
Total of 11 sign ups.
[[File:|400px]] [[File:|400px]]

Findings: Contacts & Notes
We find out about their as-is process of taking and retrieving notes
Ut4 note taking.png Ut4 note retrieve.png]

Insight
Ut4 note insight.png

Current Process:

  • CRM: Need to re-run program if password is wrong
  • Hardcopy: Messy, disorganized


Why not e-form:

  • Comfortable in using paper survey form
  • E-form may be too structure, paper offers flexibility
  • Easier to use paper to pitch, more professional


Comments:
10/11 commented that notes function helps improve their work. It is a single access point for individual contact. However, more effort has to be invested in creating notes.


Next, we introduce Tictacts and test how will participants approach the same scenario using the app.

[[File:|600px]]

Reminders
We find out about their as-is process of keeping and retrieving reminders
Ut4 note taking.png [[File:|400px]]]

Next, we introduce Tictacts and test how will participants approach the same scenario using the app.

[[File:|600px]]

Create Event
We find out how individual remember and note down future event with another person.
[[File:|400px]]

xxx
[[File:|600px]]

Attach Media to Notes
We find out how individual store a contact's details, that was recorded in hard copy. On the hard copy, the contact's birthday was also recorded.
Attach Media to Notes As Is.png [[File:|400px]]

We observed that only 13 participants took a picture of the hard copy details and attached it to the note for the contact. 15 feedback that they are unsure of what does the "attach" icon represent. For birthday reminder, 4 mentioned that they prefer to type in the dates manually and another 4 mentioned that the birthday reminder idea is useful.
[[File:|600px]]

Hashtag & Mention

Birthday Reminder

Filter Search
We also find out how individual locate the hard copy details, based on the method which they mentioned previous. The following is a summary of our findings
[[File:|600px]]

Ranking of Current Functions
Towards the end of UT3, we asked our participants to rank the importance the functions which they had tested.
[[File:|600px]]

Ranking of Current Functions
We also surveyed our participants to validate the ideas of some of our possible future functions.
[[File:|600px]]

Action Plan

  • Evaluate feedback and prioritise functional and usability issues to resolve.
  • Improve on reliability and user experience
  • Analyse which future function is most preferred by testers and determine which feature to be added / remove from timeline
  • Identify participants work processes towards the scenarios given and analyse if current product will improve productivity