According to Wikipedia, "User acceptance testing (UAT) consists of a process of verifying that a solution works for the user.". Why is it important? Because lots of things can happen without UAT.
Here are a few examples of risks when we do not consider UAT:
During the UAT activities, the Business Analyst will create:
Have you ever worked in BDD environment? Can you imagine the beauty of UAT in BDD? I mention that I captured all the needed cases for User Acceptance in the Gherkin files. If you value the UAT and want to learn more, please read this article.
3 Comments
Robert Keating
5/11/2018 04:23:49 am
A well-defined FRD (Functional Requirements Document) and/or user stories are key foundations for good downstream UAT cases in conjunction with linkage back to the upstream requirements.
Reply
Vijay
8/7/2018 10:51:48 am
I need this
Reply
Curtis Goldhagen
12/16/2019 09:29:23 am
While User Stories are key foundations for UAT cases they hold little value is they are not written originally with strong and testable Acceptance Criteria from the outset. It is up to the Scrum Team (with the CSM heavy guidance) to ensure they work hand in hand with the Product Owner and/or the Product Owner delegates to document and clearly define acceptance criteria for each and every User Story.
Reply
Leave a Reply. |
ArticlesCategories
All
Archives
October 2016
SearchKeep up to date
|