October 12, 2011 Leave a comment
User Acceptance Testing (UAT) is a significant milestone in software development lifecycle. It is during UAT that the users get to see the system “in action”, in many cases for the first time. Their acceptance and sign off are required to proceed with the production deployment. How formal and extensive is the UAT activity depends on the size of the project, user audience as well as the software development approach adopted by the delivery organization.
A key first step in the planning of UAT is to understand and establish a well-defined acceptance criteria. There is a general tendency amongst teams to focus on the “testing” and not on the “acceptance” part of UAT. This typically leads to too much attention being given to defects in the system, rather than the functionality and user satisfaction with the system. The goal of UAT is to showcase the functionality that the system offers in order to get an acceptance to move ahead with implementation, rather than asking the users to test the system for us. Therefore, emphasize the user acceptance as the primary objective of this activity and plan the UAT scripts accordingly. Read more of this post