Description
Acceptance testing, also known as User Acceptance Testing (UAT), provides the customer with an opportunity to validate that the product increment or released system is able to handle real-life scenarios and transactions. Some of this can be addressed in Sprint Demos/Reviews, but often systems become so complicated that more formal acceptance testing is required. To get the most valuable feedback, testing should be performed by an actual end user, or qualified designate, and should be conducted on the production system in the actual or simulated production environment. The goals of UAT include gaining the customer’s approval of the system or product and clearly identifying any defects or issues, and capturing changes to existing use cases or user stories.
Typical Roles
Customer
End User
Product Owner
Scrum Master
Team Member
Desired Behaviors
- 1.
Conduct UAT at least once in the product development cycle. UAT can be performed during Sprint Reviews and/or at the conclusion of planned releases.
- 2.Engage one or more end users to perform the testing.
- a.
If an end user is not available, have another customer do the testing.
- b.
If the customer is not available, have the product owner do the testing.
Note: The risk of not having an end user or customer participate in testing is that the user community may identify defects after product delivery.
- a.
- 3.
Agree upon the test procedures and acceptance criteria before UAT begins.
- 4.
Understand usability problems and any desired changes by having the development team observe the testing activities.
- 5.
Document defects and desired changes. Relate defects and changes to user stories or use cases.