User Acceptance Testing (UAT) Best Practices – The Missing Link in Agile Practices
In Agile, developers, testers, and business analysts build a working product through a series of short iterations. At the end of each iteration, the product owner accepts the software as working or not, and the team moves forward to the next iteration. This kind of acceptance is not the same as the User Acceptance Testing (UAT) traditionally done at the end of the development effort. Unfortunately, traditional UAT does not fit neatly into Agile. This often represents a missing link that causes significant pain for those implementing Agile. In this blog, we discuss how to solve this problem.