I've been asked to come up w/ a few slides that explain/describe why we should have a different group do our User Acceptance Testing, and ideally, it would be performed and owned by the business team, rather than IT.
What are your thoughts on this? Hope it turns into an interesting discussion, thanks!!!! ;-)
Apart from the onces mentioned above you can have an important slide which would be "Does the Software meet business needs", this can be judged only by the UAT team.
We have tested "Does the software meets Business requirements" in System test phase. So i think "Does the Software meet business needs" would be a slide which would make your management understand why UAT is required.
User Acceptance Testing is awesome. I think that the only problem with it is that it's not started earlier. Your internal business customers should be engaged and encouraged as early and often as possible to keep constant feedback and improvements.
Too often I've observed the UAT testers asking all sorts of questions regarding why something works a certain way. Or during a product demo that was deferred until the end of a sprint (after QA has completed) business stakeholders are talking about how the customers will hate how a certain aspect will work.
UAT will give the people who essentially make and define the requirements a chance to confirm that the product looks and feels as they expected (in addition to meeting QA and DEV's interpretations and being functionally/operationally correct).
However, as I've alluded to above, customers (internal or external) should be engaged throughout the development process. This is one area where spoilers should be welcomed!