-
Notifications
You must be signed in to change notification settings - Fork 1
Sprint 2 User Testing (team 1)
In this sprint, team 1's main task was to consult with the other teams to merge the existing character images with all the characters from the backstory and to create the missing characters so that all the characters from the backstory would appear in the game.
After all characters are determined, we made animations of all characters to further improve the completion.
Therefore, this user test will mainly focus on the fit between the character and the background, as well as the animation quality, and through this user test, we will have the opportunity to further discover the goals of the next work
This test will focus on the fit between the characters and the background story and the quality of the animations as the main test goal, this will be measured by user satisfaction and opinions
- Introduce in-game characters to users (This step is to let the user know the identity of the characters in order to test the degree of identity fit)
- Display animated characters in the game for users (The purpose of this step is to allow the user to directly evaluate the character and animation)
Collect feedback via questionnaire form and interview
The participants in this test are mainly from other classmates and acquaintances, as well as some other members of the same studio. Additionally, all tests are online via zoom due to the conditions required for the test. A total of 13 people participated in the test.
Overall, the process went according to plan, first introducing the user to all the current characters and their identities, and then showing the user how the animated characters would look in the game. After the demo, the user is provided with a questionnaire. After the questionnaire is submitted, we conduct another interview with the user for further feedback.
The link of questionnaire: https://forms.gle/XTznTDZqVxwxjSn67
Q1, Q2, and Q3 are all about the fit between characters and their identities, so they should be analyzed together. Through the results of Q1, it can be found that the vast majority of users are satisfied with the fit, and through Q2 and Q3, we can see which characters caused the difference, and it can be seen that the relevant suggestions are concentrated on the mysterious woman and musical actors.However, after the answers to Q3 and the interview questions, it can be found that the options for musical actors are mostly due to the impression of the prototype character(Xukun Cai) of the character, rather than the character design itself, and for mysterious woman, it should be further improved.
For Q4 and Q5, these two questions reflect the quality of the existing animation effects, where the results of Q4 show that users are mostly satisfied with the current animation quality, and Q5 provides further suggestions for our follow-up work, so in the next step, Extra animations when idle, Interaction, can be the priority development object in the next sprint, and more emotional expressions may be less important, and from other suggestions, a user proposes to attack animation, however, considering the game mechanics, maybe the attack animation is not necessary.
Overall, this test reflects that the work we planned at the beginning of this sprint has basically been completed, but it has additionally led us to further discover the work that needs to be done in the next sprint, This includes adding additional interactive animations, etc. as the game develops further. Therefore, we will add these tasks to our next sprint as part of what needs to be done.
Based on the information gathered in this sprint, we can plan some features that may need to be tested in the next sprint, including:
- Extra animations when idle
- Interaction animation
- Based on game mechanics, other interactive animations added later
Therefore, it is necessary to maintain communication with other teams, we need to communicate with other teams to know other required animations. More respondents from more diverse backgrounds may provide more suggestions for our next test. The difficulty of each task should be assessed in a timely manner to ensure the progress of the work
- Uniform Pixel Grid Resolution
- Storyline
- Instruction
- NPC info
- NPC Communication Script
- Inventory-System-and-Consumables
- Storyline User Test
- Traitor Clues
- Game Characters
- Player Profile User Test
- Player Eviction Menu Sprint1: User survey (Team 7)
- Player Eviction Menu Sprint2: User survey (Team 7)
- Sprint3 - Win/lose Condition: User survey (Team 7)
- Sprint4 - Polishing-tasks: User survey (Team 7)
- Transition Animation/Special Effects/Sound Effects: Feature Overviews
- Transition Animation and Effects: Design Process & Guideline
- Sprint 4 User Testing
- Transition Animation & Effect: Code Guideline-Sprint4
- Sound effect when players complete npc tasks and hover over npc cards
- Fixing the clue bug
- Music Test
- Player Eviction Menu: Design Process & Guideline
- Player Eviction Menu (Feature Overviews)
- Player Eviction Menu: Code Guideline - Sprint1
- Sprint 1 User Testing
- Detailed Eviction Card: Design Process & Guideline
- Detailed Eviction Card: Feature Overviews
- Sprint 2 User Testing
- Player Eviction Menu: Code Guideline - Sprint2
- Sprint 2 Inventory System and Consumables Items User Testing
- Sprint 2 Inventory System and Consumables Items Functionality
- NPC interaction testing plan sprint3
- NPC interaction testing results sprint3
- NPC Dialogue Scripts
- Code Guideline
- Win/lose Condition: Design Process & Guideline
- Win/lose Condition: Feature Overviews
- Sprint 3 User Testing
- Win/lose condition: Code Guideline - Sprint3
- Enemy List
- User Testing 1: Enemy Image Filter
- User Testing 2: Enemy Animation and AI
- User Testing 3: Basic Attack