maandag 6 januari 2014

Test Plant *UPDATED*



To-do-list

Cherio Kalloe
Peter Ehiorobo
Tochi Odikanwa
Franklin van de Vlies

 

Test plan


Minor   Smart Life Rhythms
Project Test     

Coördinator project                Meggie Williams, Hanneke Hovels




Index:
- Summary of test plan
- Introduction
- The product
- The prototype
- Aim
- Research questions
- Think aloud protocol
- Interview
- Test: Participants
- Location
- Tasks
- Registration
- Analysis
- Protocol


Summary of test plan

PROGRESS
During the pilot tests we got a lot of information about the application. The application was already organized in a way the working student would like to use it. But some points had to be better to ease the user of the product. The test on friday is based on the feedback we got from the pilot test. 
Next week the application will be made digital (starting by this week already). The plan is to make it in Flash so the application is also usable on a mobile phone or the computer. When the product is finished there will be some interviews with students from our own minor to talk about the application we designed. We are also going to ask them to use it so they can give us feedback about the finalized product. So mabye we can add some last details in the application before the end presentation.

WHO are we testing?
We are testing working students from the University of Applied Sciences The Hague. The product will be available and directed for working students in general. Asking a table of 6 people to talk about the application and use it is a good way to weigh the arguments. In this way there is the possibility to arrange the ultimate application. The test will be take place with approximately 10 students. This amount could expend, this depends on the data we already got.

WHAT are we testing?
We are testing a paper prototype. This paper prototype contains symbols and pictograms of the application. The user of the paper prototype is also free to draw their own "button" and place it in a place they would like to have it.
- Interface of the main menu (Triangle, Clock, 3 categories).
- Add a task or assignment with empty spot.
- Interface of the school category. 
- Information sign.
- Triggers


WHEN are we testing
The test will be held on friday the 10th of January.


WHERE are we testing?
We are testing the application in the audatorium and the audatorium of IPO and Human Technology from the University of Applied Sciences The Hague.



WHY are we testing?
The test is taken place because we want to develop the application. At the pilot test there was a lot of positive feedback, but there are still some things that has to be improved to have a fair chance at the market.



HOW are we testing?
The testing setup is the following:
- 1 testleader (talks with the user)
- 1 observer with extra info about the application
- 2 observers to make notes
"Wonderful day" is an application that is based on a to-do-list. The interesting part of this application is the rewarding part. This application is focussed on doing the usual habits of a day. There is a pre-set menu where you can add different kind of tasks. This application motivates the users by coloring points green or red. When the user completed the task, the point will turn into green. If not, it will turn into red.

More information about this application in the link below:
https://itunes.apple.com/us/app/wonderful-day/id502432398?mt=8
                                                                     
The to-do-list is based on working students and can also be used for the social life of the student. During the end presentation will be shown some futuristic implementations for the application. For instance: students can track eachother during the day. Another interesting feature social chat about the assignments. Students with the same kind of assignments could be set into 1 chatroom. Like this the students can talk about their assignments and give eachother advice.



Introduction
In this test plan we will show what will be testing on Wednesday the 8th. During the pilot test on the 20th of December we got some interesting insights. There were a few things that should be better in the application. On Wednesday the 8th we will test the outcome and analyze it again.

The productThe focus of this product will be one specific moment in the life of a working student. The focus of the test will be the insights from  December the 20th. We tried apply the insights from the pilot test into the application and will test it.  After more research of the target group, it is evident that it is not the time that is blocking the students to do their tasks, but the tasks itself. During the pilot test we found out that working students like 3 kind of images as the design for the application.
- A triangle
- A clock
- Based on 3 pictograms (school, work, social life)


On Wednesday the 8
th we want to know which image for the interface working students like the most and why.

The triangle as an example


The application is a to-do-list for students to manage their tasks. If students could manage tasks properly, they  have more free time in general. The triangle is based on school, work and social life, the three main activities in the life of a working student. In the application the user can click on school. In this part of the application the user can add tasks and assignments related to school. In this way you can separate schoolwork with school. This also means for work and social life. If you have something you need to do at work, put it in your to-do-list so you won’t forget it. The application will send you a reminder to trigger the student to start working on the assignment.

The prototype
The prototype will be made out of paper and cardboard. The product is an application. Paper prototyping is a used method in the user-centered design process, a process that helps developers to create software or products that meets the user’s expectations and needs. The prototype will be an application for working students. It is not possible to make an application in the amount of time there is available. So this is the reason why there will be a paper prototype. By replacing the screens of the paper prototype, the user will be given the idea that he is using a real phone and application.

The test aim, the research question (s) and the test plan were used to help build the type of prototype that will be used for the test. The prototype is made out of paper showing the screen of a mobile phone. The other components/contents will make up the application interface  will also be made out of paper. These components/contents are the different activities like school, work and social life, will be text and images and blanks too to enable participants provide us with possible contents that will be included in the application . These different contents on paper/post-it and the blank for possible contents will allow the participants to arrange the different content on the mobile phone screen. This test will provide insights on the contents and interface development.


Aim
Getting insights about:

-       What image should be used in the application (main design)
-       How to add a new assignment for school. (+add .. click on an empty spot.. etc)
-       How to visualize the school part. Different folders for your subjects, all the assignments together, both?
-       The information sign. How to get instructions about the application?

Research questions
In order to receive information from the research, there are some questions that need to be answered.
 

The main research question is:
How does / will  the interface and content make the working students interact with the application?

Sub questions:
1 What elements or functions should be in the application?
2 Why should these elements and functions be in the application?
3 How will these elements and functions help you in organizing, managing and execute your tasks?

During the test will be shown presumptions about the interface for the application. With the feedback from the upcoming test, we will advance the product to a next level. This user test is to receive feedback about the assumption students made about the application. At the “tasks” you can read what kind of tasks we let the students do with the application.


Think aloud protocol
Before the test starts, the user will be asked to think aloud. This means that every action the user takes, will be combined with a short explanation. This gives the designers an opportunity to ask about those actions during the interview after the test. When something is wrong about the interface, together with the interview, and the thoughts of the user, the designers can solve the problem.


Interview
After the test it’s important to understand why something went wrong or right. The camera recorded the actions and emotions of the user, but it didn’t record the reason why the user did something. That’s why you need an interview to perceive the information.- How did you think it was going?

- What did you like about the product?
- Where there any struggles?
- Do you have any experience using products like this?
- Would you like to add something to the product?
- What did you think about the functions of the product?
- Would you purchase this product?
- Would you recommend this product?
- Do you have any announcements or questions about the product?
- Are there any questions about the test itself?
- How would you want to be reminded of your task and deadlines?
- How do you want the to-do list interface to look like
- What will be the steps you would take to perform specific action like, place your task and deadlines on the to-do lists?
- What should the contents of the three activities be? What do you want in the contents?

Test
> Participants       
During our First test there will be four participants. The target Group for the application is working students. On Friday the 20th of December there will be four students from the minor “alle tijd”. These students will test the product and give feedback about how it can be improved.



Location
The prototype 
will be tested in the auditorium of IPO and Human Technology in the University of Applied Sciences The Hague.
The test will 
approximately take one hour. The people we are going to test are random students from the University of Applied Sciences The Hague. The students should work and have a little bit of time to do the test. We also would like to test a bigger group of (around) 5 people, so they will discuss about the application to gain more information. 

NOTE: A part of the tasks are still the same as the test tasks on Friday the 20th of December. The feedback of the students has been implied into the application to test how effective it will be.

> Tasks
The participants will be asked to do several tasks. The most important part of the tasks are the content and the interface. By placing pictograms and pictures in the application, we try to understand why the participant choose to have those pictograms and pictures at that specific location.
-          - Welcome and ease
When the participant joins the room, there will be a little chat about work and school. This information will be written down so it can be used later for the interview. This chat is supposed to ease the participants to make them feel comfortable.
 


-         -  Introduction about the topic, concept and the test
After the small chat, the assignment will be introduced. This helps the participant understand why this test is held. The target group will be explained.


-         -  Show participants pictograms of the various activities
The participants will have the opportunity to arrange their own application. But first we need to hand them the pictograms and pictures


-          - Tasks for participants( about the interface arrangement)
In this stage we ask the participant to place the pictograms and pictures to arrange their own application. The meaning of the shapes is open for the participant itself. They will create an interface and explain why they think this would work.


-          - Interviews  during participants performing the tasks
The participants will be asked to think aloud. While the participants think aloud and tell us what they think of the product, we will ask them several questions why they are doing these activities. 


-         -  Questions about the contents, what extra, what they will include, how it will work
After the tasks, the participants will be asked some questions about the content of the application. What does the application need as an extra? What would they want to include in the application?


-          - Show the participants our group concept and ask for feedbacks
After the test and the questions the participants will be shown our group concept for the application so far. There will be asked for feedback, what do they think of the concept?

> registration
To improve our chances of gaining insights with this test, it is the goal of this test to provide us answers to our test question(s). To get these answers, we will be using camera to take pictures, mobile phone recorder to record interviews, and note-taking to record insights from participants. With these we intend to gain insights to what the contents and how the interface of the Application should look like.

> analysis
The photos, the audio from the interviews and the note-taking from the interviews will be analyzed by the group to answer our test question(s) and the result will thereafter be presented through a report/presentation.


Protocol
Before the Test, the user has been asked to participate for a Test. The only thing the user knows is that he/she will use a product to support their daily life. The target group is: working students.

“Welcome. My name is … and we are…

Would you like something to drink?

We follow the minor 
Smart Life Rhythms. Here is a short introduction of the minor: Nowadays, professionals who work flexible hours (Dutch: het Nieuwe Werken) have much more individual freedom to organize the what/where/when of their work. Although ICT and social media enable the development of these new rhythms professionals still indicate unsolved problems with synchronizing the new rhythms. In the minor we will use user test and service design methods to develop an app, product or service that supports Smart Life Rhythms and helps solve these problems.

During the test I will stay here, in the same room as you so you can contact me if you have any questions about the product. Do we have your permission to audio tape the test? The tapes will only be used for this test and will not be published on the internet. During the test I will write down some notes so I can ask questions after the test. We ask you to think aloud during the test. This means: what are you doing, and why. What are your thoughts about the product when you use it? It sounds a bit weird maybe, but you will help us a lot with it.

For our minor Smart Life Rhythms we have to test a product or service. We have made the product by ourselves and would like to receive feedback about it. In a minute we will ask you to use the product. After your first impression, I will give you a task to perform. Try to act natural. Just say everything that comes up in your mind. That’s why we ask you to think aloud. We would like to know your thoughts about the product. After the test, we would like to ask you some questions about how it went. Do you have any questions beforehand?

Let’s start. Here is a product that is called the “to-do-list”. Try to use the product and to detect how it works and where you can use it for.

“Think aloud interaction”

Tell me: what you think this product does? And what are your first impressions?

“…”

This application is a digital agenda for working students to manage their time. When you wake up, you will see a picture of your day, this makes it more like an adventure than just going to school or work. With the icons you can change your daily schedule, check times for the public transport, add a to-do-list and spot friends. Has my explanation changed your way of experiencing the product?

“…”

Now I am going to give you a task. Could you set up your own day with the icons and actually take part in that day? (24 hours in 20/30 minutes).

Now you have used the product, I would like to ask you some questions about how it went.

- What did you like about the product?
- Where there any struggles?
- Do you have any experience using products like this?
- Would you like to add something to the product?
- What did you think about the functions of the product?
- Would you purchase this product?
- Would you recommend this product?
- Do you have any announcements or questions about the product?
- Are there any questions about the test itself?
- How would you want to be reminded of your task and deadlines?
- How do you want the to-do list interface to look like
- What will be the steps you would take to perform specific action like, place your task and deadlines on the to-do lists?
- What should the contents of the three activities be? What do you want in the contents?

Added interview questions:

-          What would be your ideal arrangement of the App interface?
-          How would you preferred the interface of the application?
-          Where would be the right position for the clock?
-          Describe how you would use this app to note down your important tasks?
-          What steps would you take to add a task to “To-do list” and what content do you need for each step?
-          What do you think about the interface of the APP with pictograms ( school, work, and social life) ?
-          What would you prefer to see when you click on one of the pictogram?
-          How would you like to see all the tasks on your to-do list? What sign would you use to represent “all tasks”?
-          What would be your perfect sign for “information”, “info” or “?”
-          Demonstrate the task of adding a task to your “to-do list”?

“…”

Thank you for your participation!”

Geen opmerkingen:

Een reactie posten