We currently do User Acceptance Testing (UAT) at the end of the every sprint. I circulate an email to the team letting them know the features that have been developed. The idea is for them to report any bugs to the dev team for the features developed in that sprint.
I need to put a process in place to ensure that the team are doing UAT properly, since the team has trouble doing UAT. What checklists should I give the team?
I agree with @CodeGnome but not just with Agile. No matter the method, the product, or even the domain, UAT needs to belong to the users, in scope, conduct, and outcome. The client side needs to define how to conduct UAT, the scenarios it will run, procedures, training people, how to document findings, any criteria needed, etc. After all, UAT is a client risk and quality action.
The only caveat I would have to this is if their UAT action, or inaction, is adversely impacting your ability to get to production in some way. This is why I keep asking what you are observing in the comments above.
What checklists should I give the team?
From an agile perspective, you should not be giving the team a user acceptance testing (UAT) checklist at all. Your product's users (or at least a Product Owner or business analyst if you're not agile enough to work directly with your users) should be working with the development team to develop acceptance tests prior to the development of the feature.
Ideally, these acceptance tests should be executable (if software) or automatable (for example, via computer-vision validation). That way, there's no subjective question about whether the right thing was built, since the desired result was defined up front.
Even in legacy shops where UAT isn't automated, and basically involves a great deal of subjective poking around rather than formal validation, the criteria for what should be delivered—and perhaps more importantly, how it will be measured—absolutely must be defined first to ensure an effective delivery pipeline.
You are getting UAT done to check the functional flow of the program. The way is to get the test cases prepared by end user who has given the requirements. Request him/her to run through the cases during testing. This must include the additional cases which you should add during impact analysis. In case of a bug fix, user should test test cases prepared by you. UAT sign off should be only if the test passes through all test cases.
Don't forget to ask for all artifacts(screenshots) of test done.
Add these as RFC checklist before production release.
