Update Usability Tests
parent
29919e878b
commit
4f712efbb5
@ -1,16 +1,19 @@
|
|||||||
## Usability test 28.02.2022 – 1st Iteration (Wireframes)
|
## Usability test 28.02.2022 – Initial test (Wireframes)
|
||||||
|
|
||||||
#### Purpose
|
#### Purpose
|
||||||
|
|
||||||
- Test UI and UX of the wireframe prototype to find improvements to implement in the MVP.
|
- Test UI and UX of the wireframe prototype to find improvements to implement in the MVP.
|
||||||
- Test color scheme and other elements that needs to be WCAG 2.1 - 1 compliant
|
- Test color scheme and other elements that needs to be WCAG 2.1 - 1 compliant.
|
||||||
|
|
||||||
#### Given tasks
|
#### Given tasks
|
||||||
|
|
||||||
1. Create Tournament and manage it
|
1. Create Tournament and manage it
|
||||||
2. Create and manage teams and players
|
2. Create and manage teams and players
|
||||||
3. See tournament overview and overview of finished matches
|
3. See tournament overview and overview of finished matches
|
||||||
4. Give feedback on color scheme/contrasts and button sizes etc.
|
4. Give feedback on color scheme/contrasts and button sizes etc.
|
||||||
|
|
||||||
#### Results
|
#### Results
|
||||||
|
|
||||||
1. The tester successfully created a tournament and navigated to the manage window.
|
1. The tester successfully created a tournament and navigated to the manage window.
|
||||||
- _Comments:_ User could not quickly find the “Create Tournament” button.
|
- _Comments:_ User could not quickly find the “Create Tournament” button.
|
||||||
2. The tester successfully navigated to the team and player management window.
|
2. The tester successfully navigated to the team and player management window.
|
||||||
@ -24,16 +27,17 @@ The customer was quite happy with our MVP but had a few things they wanted to be
|
|||||||
- The brackets need to show winners, and how to select and change them if the wrong team is picked more clearly.
|
- The brackets need to show winners, and how to select and change them if the wrong team is picked more clearly.
|
||||||
- The Navigation between pages should be improved. We implemented a navigation bar to fix this.
|
- The Navigation between pages should be improved. We implemented a navigation bar to fix this.
|
||||||
|
|
||||||
<br />
|
|
||||||
<br />
|
<br />
|
||||||
|
|
||||||
## Usability test 29.03.2022 – 2nd Iteration (MVP)
|
## Usability test 28.03.2022 – 1st Iteration – internal (MVP)
|
||||||
|
|
||||||
#### Purpose
|
#### Purpose
|
||||||
|
|
||||||
- Test UI and UX for the MVP to find improvements to implement in the final product.
|
- Test UI and UX for the MVP to find improvements to implement in the final product.
|
||||||
- Test color scheme and other elements that need to be WCAG 2.1 - 1 compliant.
|
- Test color scheme and other elements that need to be WCAG 2.1 - 1 compliant.
|
||||||
|
|
||||||
#### Given tasks
|
#### Given tasks
|
||||||
|
|
||||||
1. Create tournament
|
1. Create tournament
|
||||||
2. Manage tournament
|
2. Manage tournament
|
||||||
3. Delete tournament
|
3. Delete tournament
|
||||||
@ -44,6 +48,7 @@ The customer was quite happy with our MVP but had a few things they wanted to be
|
|||||||
8. Maneuver around the web application without issues
|
8. Maneuver around the web application without issues
|
||||||
|
|
||||||
#### Results
|
#### Results
|
||||||
|
|
||||||
1. Tournament was created with expected size
|
1. Tournament was created with expected size
|
||||||
2. Tournament details were altered and saved, as expected
|
2. Tournament details were altered and saved, as expected
|
||||||
3. Tournament was deleted, as expected
|
3. Tournament was deleted, as expected
|
||||||
@ -60,3 +65,73 @@ The customer was quite happy with our Wireframe but had a few things they wanted
|
|||||||
- The contrast ratio of some of the colors we picked for the prototype was to low, new colors needs to be picked.
|
- The contrast ratio of some of the colors we picked for the prototype was to low, new colors needs to be picked.
|
||||||
- Buttons needs to be more visible and obvious.
|
- Buttons needs to be more visible and obvious.
|
||||||
|
|
||||||
|
<br />
|
||||||
|
|
||||||
|
## Usability test 29.03.2022 – 2nd Iteration (MVP)
|
||||||
|
|
||||||
|
#### Purpose
|
||||||
|
|
||||||
|
- Test UI and UX for the MVP and discover improvements for final iteration.
|
||||||
|
- Test navigation of the site for an external user.
|
||||||
|
- Gather feedback of overall feel and look of the website, including color scheme and layout.
|
||||||
|
- Gather comments and concerns from the customer regarding future implementations.
|
||||||
|
|
||||||
|
#### Given tasks
|
||||||
|
|
||||||
|
1. Maneuver around the website
|
||||||
|
2. Create a tournament
|
||||||
|
3. View a tournament
|
||||||
|
4. Manage a tournament
|
||||||
|
5. Delete a tournament
|
||||||
|
6. Manage teams
|
||||||
|
7. Create a team
|
||||||
|
8. Edit a team
|
||||||
|
9. Delete a team
|
||||||
|
10. Select winners of matches and “complete” a tournament
|
||||||
|
11. Comment on the overall feel of the product
|
||||||
|
|
||||||
|
#### Results
|
||||||
|
|
||||||
|
1. The users maneuvered the site quite well, with minor hiccups
|
||||||
|
- _Comment_: We had a menu button that the users clicked quite frequently, at the time it did not do anything, so we removed it for the MVP showcase to the supervisor. It will be implemented it with function later in the production.
|
||||||
|
Comment: The first user had issue returning to the front page, as the “Home” icon did not have any complementary text to guide the user to click on it, this will be added in future iterations of the product.
|
||||||
|
2. The users were able to create a tournament smoothly at the expected size with the expected values
|
||||||
|
- _Comment_: When choosing the time for the tournament the user rarely pressed the calendar button to easily select a time, and rather wrote it down manually, leading to us finding a “bug” with the time selection input, which will be fixed in future iterations. We will also overhaul the input field for time & date to prevent manual input, while still making it accessible.
|
||||||
|
3. The users had no trouble viewing the tournaments
|
||||||
|
- _Comment_: The user had comments on how the brackets were presented and did not like the feel of it as it were nowhere near perfect at the time of review. We will overhaul the bracket system completely to make the user experience better.
|
||||||
|
4. The users were easily able to go into the manage tournament and navigate within the system
|
||||||
|
5. The users were able to delete a tournament, as expected
|
||||||
|
6. The users navigated to the “manage teams” section without minor issues
|
||||||
|
- _Comment_: The user tried adding a team by clicking on the bracket directly at first, which they were then prompted with a “no team selected” alert, which confused them at first. This is something we will improve on and perhaps add in future iterations of the bracket system.
|
||||||
|
7. The users were able to create a team without issue
|
||||||
|
- _Comment_: They liked that they couldn’t add more teams than they chose for the tournament
|
||||||
|
8. The users were able to edit a team without issue
|
||||||
|
- _Comment_: The users were pleasantly surprised that the bracket updated automatically and found the edit process very intuitive
|
||||||
|
9. The users were able to delete a team successfully and without issue
|
||||||
|
10. The users were confused about how to complete a tournament to begin with, but after a while they were able to complete it, although they found it not very intuitive
|
||||||
|
- _Comment_: We will make it more clear how to complete a tournament with buttons, as well as making it clearer who has won and proceeded in the tournament.
|
||||||
|
11. The users were very happy with the overall layout
|
||||||
|
- _Comment_: They did not like the brackets, which will be changed.
|
||||||
|
|
||||||
|
#### Conclusion
|
||||||
|
|
||||||
|
The overall impression the customer had after the user test was very positive, and they had more ideas for what could be added next rather than complaints. The things that they felt needed improvement have been added as comments under the given tasks, for future development they gave us quite a few ideas to work with.
|
||||||
|
- Bracket system needs to be completely overhauled.
|
||||||
|
- Minor additions need to be added to certain elements, mostly specified in the result section above.
|
||||||
|
|
||||||
|
We will discuss further implementation of functionality both internally and externally with the customer, to ensure they will be happy with the product. They also gave an impression of things they want added or changed that did not directly influence the product but are more Quality-of-Life changes.
|
||||||
|
|
||||||
|
- Better art or find a different cover for the tournaments
|
||||||
|
- The possibility to add an image or map in the tournament description
|
||||||
|
- Tournament history tab or page to view completed tournaments
|
||||||
|
- Needs to be searchable and if on the main page should be quite small
|
||||||
|
- Tournament archiving should be flexible as they could drag on, that way they don’t get archived the minute they “expire” according to the date and time set.
|
||||||
|
- A nice addition would be a log that the managers can overlook to view who changes or creates what on the tournament, not a necessary addition but a nice one for sure.
|
||||||
|
- The possibility for adding prices to the tournament, as most have them and the participants are always asking what they can win or get by participating.
|
||||||
|
- A login system
|
||||||
|
- This is something that is already planned to be implemented
|
||||||
|
- A possible feedback page, not very high priority
|
||||||
|
- A countdown until a specific tournament starts
|
||||||
|
|
||||||
|
All these comments and suggestions are things that will be taken into consideration when continuing development of the project. Some of the suggestions might not be achievable in the time we have to complete the project but we will do our best to adhere to the customers wishes.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user