Given we will do research on this app, the team needs to do usability testing and prototyping. The biggest risk with the app right now is we don’t know if people will want to use it, if the interface is understandable or discoverable, etc. We will talk about this at the scoping meeting and get a shared understanding.
I won’t force it for the class, but really as a professor and an experienced professional I can say definitively the benefits are huge for doing usability testing and prototyping. It’s the difference between going to play a game with some new plays having drilled and refined them, versus you never even tried them out at practice.
Usability Testing / Focus Group (/20) - Extra Credit - Can be done in Deliverable 4 or 5
You may do your first round of usability testing.
If you have already done that, you should already have gotten feedback about prior usability testing plans and results, then you may do another round of usability testing, including any tasks I gave prior feedback.
Usability Testing
You may do your first round of usability testing or do another iteration of testing
Do this sooner in the sprint rather than later
Write/update your usability testing script ( /5)
Here is a template to use, edit it to fit your application.
Choose the most important features of your app, which you have created mockups for. Have at least 5 tasks.
Once you write your script, @ the professor in your team channel to get feedback, before you do the usability testing.
-5 points if you do not do this, not recoverable
This can be a combination of the completed features and also wizard of oz / paper or digital prototype session. Focus on learning as much as possible and refining your mockups/UI/UX and features to better match your users’ needs.
For any of the items that are missing, deduct -2 points.
If there is no permission form, give 0.
Do usability tests with at least 3 other people, and write up consolidated notes on the results of the testing and planned revisions ( /10)
Make major progress on those revisions by the deliverable due date by revising your mockups and any associated use case descriptions
Given we will do research on this app, the team needs to do usability testing and prototyping. The biggest risk with the app right now is we don’t know if people will want to use it, if the interface is understandable or discoverable, etc. We will talk about this at the scoping meeting and get a shared understanding.
I won’t force it for the class, but really as a professor and an experienced professional I can say definitively the benefits are huge for doing usability testing and prototyping. It’s the difference between going to play a game with some new plays having drilled and refined them, versus you never even tried them out at practice.
Usability Testing / Focus Group (/20) - Extra Credit - Can be done in Deliverable 4 or 5
You may do your first round of usability testing.
If you have already done that, you should already have gotten feedback about prior usability testing plans and results, then you may do another round of usability testing, including any tasks I gave prior feedback.
Usability Testing
You may do your first round of usability testing or do another iteration of testing
Do this sooner in the sprint rather than later
Write/update your usability testing script ( /5)
Here is a template to use, edit it to fit your application.
Choose the most important features of your app, which you have created mockups for. Have at least 5 tasks.
Once you write your script, @ the professor in your team channel to get feedback, before you do the usability testing.
-5 points if you do not do this, not recoverable
This can be a combination of the completed features and also wizard of oz / paper or digital prototype session. Focus on learning as much as possible and refining your mockups/UI/UX and features to better match your users’ needs.
For any of the items that are missing, deduct -2 points.
If there is no permission form, give 0.
Do usability tests with at least 3 other people, and write up consolidated notes on the results of the testing and planned revisions ( /10)
Make major progress on those revisions by the deliverable due date by revising your mockups and any associated use case descriptions