Conducting User Acceptance Tests
By Tessa Holland and Mikaela Robertson 14 January 2020 Way of Working
An outline of how to conduct user acceptance tests once development is completed.
Once an iteration has been completed, it requires User Acceptance Tests (UATs) to be conducted by the product manager against all the issues which were completed (and deployed onto beta) during the iteration. User Acceptance Testing involves the product manager reviewing each ticket which was completed and confirming that it meets the acceptance criteria which they defined at the beginning of the iteration.
This can be done in two ways:
- The product manager joins a member of the development team in a walkthrough session in person. This allows a member of the team to see any issues which occur as they occur, which can be very valuable when testing. This is the preferred method, as it ensures that the tests are completed quickly and completely, and the team can be sure that any issues which occur are truly issues, and not just user error.
- The product manager does this process in their own time and submits their findings remotely. This has advantages in that if they struggle to make into the office or isn't available during work hours, it can still be completed in a timely manner.
The results of a UAT session are recorded against each issue, and if all pass, then a release to production can be prepared. However, it is not uncommon for a product manager to provide feedback which needs to be addressed. Depending on the urgency of the change, it can be handled in three ways:
- Urgent Resolution - This is when the customer requires an urgent fix which must be resolved in the current beta version. In this situation the development team will pause the current iteration and apply the fix. It should be noted that this will create a delay for the end of the next iteration.
- Next Iteration Resolution - This is when the customer is willing to wait for the fix to be in the next version of the beta environment. In this situation the defect or minor change request will be added to the next iteration's backlog.
- Backlog Resolution - This is when an issue has been deemed to be a low priority. In this situation the UAT feedback will be added to the product backlog and be brought up during a future planning session for.