SWEN303 2024 Group Project - Part 2 - User Testing

Change Log

CHANGE LOG
24.04.2024 Added suggested workload
22.04.2024 Group Project Part 2 release date.

Group Project Part 2 Due: 23:59 Monday 10 June 2024 (Start of Week 14)
Weight: 25%
Suggested Workload: 25 hours (see Course Outline)
Submission System: https://apps.ecs.vuw.ac.nz/submit/SWEN303
Extensions see notes on Slip Days and Extensions.

1. Description: Part 2 - User Testing of the Prototype

In this Part 2 of the Group Project, you will be testing the prototype from Group Project Part 1. The user testing will be on members of the class who are in different teams. Every member of the class must participate in testing at least one other team's project. You will document the testing methodology including a test plan. You will report the results of the user testing. Your individual reflections of the process and the learning will be submitted separately in the reflection part of the final project. See ProjectGroups for group formation and user testing for Part 2.

2. Submission Requirements

You will be submitting a link to the gitlab.ecs repository for the project and a link to your reflections on the work you contributed to the projects, and what you were responsible for.

2.1 Required content:

  1. Usability Test plan. This is the plan you used to test the prototype. This includes:
    • Methodology - How many users and what you are testing
    • The script - What you say to the users
    • Roles - Who is doing what
    • Tasks - What are you testing
    • Metrics - How you are measuring (e.g. SUS, NASA TLX)
    • Usability Goals - what is the level you are happy with on the above metrics
    • Problem Severity - How bad are the problems
  2. Usability Test Results
    • The results from the tests, based on metrics, compared to goals and how severe each issue is.
    • Issues that will be updated for the second version of the prototype - listed as issues in gitlab. These issues will be associated with group members.
  3. Updated prototype based on user testing
    • Clearly identified updates from the original update based on user testing with text justification
    • Description of the rationale for the update (e.g. prioritization of issues) and how they benefit the project
    • You do not have to make these updates to your prototype, this is out of scope for the project.
  4. Usability Test Discussion
    • What were the most interesting things you found from user testing?
    • What did you learn from conducting the user testing?
    • What were the most significant results you found from user testing?
  5. Individual Contribution
    This is where you can discuss your contribution to the group work both from the project perspective and group work perspective. This will include:
    • Which role(s) you had in the group.
    • Your evaluation of your performance in the role.
    • Evaluation of the other members of the group as to roles and contribution
    • Evidence for the work you have done, for example a link to the list of issues which you were responsible for in Gitlab
  6. Individual Reflection
    • The contribution you are most proud of in the project/course, and why you are proud of that piece of work.
    • The key things you learnt about User Experience that you will take forward into other projects
    • How the group collaboration functioned as a whole and how you contributed to functional and/or dysfunctional aspects of the group.
    • What were the main differences you learned from user testing vs. the user evaluation methods in Part 1 (i.e. Discount Usability Methods: heuristic evaluation and cognitive walkthrough)

Please submit your assignment into the following submission assessment items:

3. Assessment Criteria

Group Project Part 2 - User Testing is worth 25% of the course grade, with 5% out of the 25% total a group mark. There are two main components that are graded about the user testing part:
  • Group User Testing (60%)
    • Part 1. Usability Test Plan (20%)
    • Part 2. Usability Test Results (20%)
    • Part 3. Updates from Results (10%)
    • Part 4. Discussion of Results (10%)
  • Individual Reflection (40%)
    • Part 5. Individual Contribution (20%)
    • Part 6. Individual Reflection (20%)

We will be using a rubric for this assignment, see GroupProjectPart2Rubric.

The assessment will consider both presentation and content. The presentation will be based on how easy it is to read, correct spelling, grammar, punctuation, clear diagrams, and so on. The remaining content will be assessed according to its clarity, consistency, relevance, critical engagement and your demonstrated understanding of the material in the course. We will not mark you down because you missed a detail that covers a fairly minor situation, but we will if the missing detail is important to the strength of your argument.

Gitlab is compulsory for this assignment. Students should use gitlab to document their process during the development of this assignment. Documenting work will make it easier to show who was responsible for which tasks.

4. Q&A

  • Q: If I have a question about the Group Project Part 2 where shall I ask?
  • Q: Is there a sample report for this project? The following show some responses to what we are looking for, it is not complete but should guide you into what we are looking for. Definitely chart your data and add quotes from participants correctly labelled. Please don't use pie charts!