Thank you very much for your feedback and encouragement on my blog post series titled “My Interactions with Customers”. The customer is one of the best sources to learn from. I am just sharing that learning with you all.
In many IT organizations, it is a standard practice that the unit testing is performed by the development team and the User Acceptance Testing (UAT) by the end users of the applications. The remaining testing activities, such as System, Integration, Performance and Security Testing are executed by the Testing team. However, in most of the product development organizations, the UAT often gets replaced by the beta release and the subsequent real life beta testing.
The beta testing phase in the case of a product development organization is justified, primarily because the customer base is external and the deployment scenario is not under the control of the development and the testing teams.
For most IT organizations, a separate UAT phase looks redundant. It is expected that the testers are independent. They are expected to possess the domain knowledge; in other words an insight into the end-user’s needs. These are the expectations in addition to the need for Testing expertise and knowledge of technologies. In summary, the testing team is expected to be the Voice of Quality.
Why can’t the testing team validate the business process and certify the applications for the final release? Is adding this responsibility on the testing team long overdue? Only then, the testing team will truly become the Voice of Quality! It will save a significant amount of money for the organization and time for the end users of the applications.
Hence, the necessity for a separate UAT phase needs to be relooked at. I will be happy to know your thoughts.