Update Usability Tests, added second iteration and conclusions
parent
3fa6f4d879
commit
6c6817236b
@ -1,13 +1,16 @@
|
||||
## Usability test 28.02.2022 – 1st Iteration (Wireframes)
|
||||
### Purpose:
|
||||
|
||||
#### Purpose
|
||||
- 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
|
||||
### Given tasks:
|
||||
|
||||
#### Given tasks
|
||||
1. Create Tournament and manage it
|
||||
2. Create and manage teams and players
|
||||
3. See tournament overview and overview of finished matches
|
||||
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.
|
||||
- _Comments:_ User could not quickly find the “Create Tournament” button.
|
||||
2. The tester successfully navigated to the team and player management window.
|
||||
@ -15,5 +18,45 @@
|
||||
3. Tester was presented with the tournament overview after creation, overview of tournaments was also a part of the home page.
|
||||
4. Briefly commented on a button, with green background color and white text, which had too little contrast. This was expected and part of our color scheme testing.
|
||||
|
||||
#### Conclusion
|
||||
|
||||
The customer was quite happy with our MVP but had a few things they wanted to be changed.
|
||||
- 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.
|
||||
|
||||
<br />
|
||||
<br />
|
||||
|
||||
## Usability test 29.03.2022 – 2nd Iteration (MVP)
|
||||
|
||||
#### Purpose
|
||||
- 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.
|
||||
|
||||
#### Given tasks
|
||||
1. Create tournament
|
||||
2. Manage tournament
|
||||
3. Delete tournament
|
||||
4. Create team
|
||||
5. Edit team
|
||||
6. Delete team
|
||||
7. Select winners of matches
|
||||
8. Maneuver around the web application without issues
|
||||
|
||||
#### Results
|
||||
1. Tournament was created with expected size
|
||||
2. Tournament details were altered and saved, as expected
|
||||
3. Tournament was deleted, as expected
|
||||
4. Teams created with given name. Feature for adding members was not yet implemented.
|
||||
5. Team details were altered and saved as expected
|
||||
6. Team was deleted as expected
|
||||
7. The selected winner was picked and automatically filled in the next tiered match.
|
||||
- _Comment_: No intuitive way of knowing how to select winners, and no obvious option for undoing selections. Brackets will be changed to make this more intuitive.
|
||||
8. All buttons lead to the expected page.
|
||||
- _Comment_: None of the pages had a “back” button which made navigating back to the previous page cumbersome. A tournament bar was added to fix this.
|
||||
|
||||
#### Conclusion
|
||||
The customer was quite happy with our Wireframe but had a few things they wanted to be changed.
|
||||
- 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.
|
||||
|
||||
## Page will be expanded with further usability tests once MVP is finished
|
||||
|
Loading…
Reference in New Issue
Block a user