User acceptance testing in software implementation

UAT: The best way to go about a potentially painful process

Even for a computer programmer who is fluent in the language of the software development cycle, the time-consuming and tedious process of user acceptance testing (UAT) can be frustrating. But when the users involved in the testing are all accustomed to using a computer system that already works, and has been de-bugged of all potential glitches the UAT process becomes even more of a challenge, as developing test plans, conducting tests, and reporting results is not in the users' usual comfort zone of work related tasks. Users must critique what they usually take as givens, when using software.

But the UAT definition of using and accepting new technology and software as the end product of the development cycle and its end location in the overall process can still be a productive one. Key to making the process as painless as possible is to remind the test users that with a new system, problems will occur -- thus the users must be prepared and act with caution when dealing with important and valuable documents and information. Beta-testing or outsourcing the UAT stage to willing companies and experienced testers is one potential way to minimize in-house discomfort, but if this is not a viable option and familiarity with the specifics of the company and individuals is a priority, then in-house UAT can also be productive, if not more productive, when users have some knowledge and input from the beginning, regarding the lifecycle of the product, and have a clear idea what reported results are helpful to programmers.