Conduct User Acceptance Testing

If you’re implementing OOTB apps, skip this step.

After integration and system testing, the adoption team (or person responsible for organizational change management) should train a small group of key users on how to use the app. This training will prepare them for user acceptance testing (UAT) in which you’ll test whether the app meets users’ needs and satisfies the use case.

For UAT, train the users who:

• Participated in your wireframe design tests and contributed to the use case and requirements definitions
• Are power users who are familiar with the data and whose insights will be valuable during UAT
• Are project team members, such as the project manager, project sponsor, stakeholders, and admins

Use the training materials you created earlier and provide documentation to these users as needed.

If you’re implementing OOTB apps, skip this step.

The purpose of UAT is to make sure the app meets users' needs and satisfies the use case.

UAT test results should answer questions like:

• Can users use the app and complete the test cases easily?
• Does the app solve the problem outlined in the use case?
• Is there any data or functionality missing?
• Did the app function correctly during the test?
• Does the app work on supported browsers?

To get the most accurate test results, complete UAT in a QA environment that matches your production environment as much as possible.

Instruct users to complete the test cases that you wrote earlier. Key users and project team members should participate in UAT. Developers and designers should observe. 

If you’re implementing OOTB apps, skip this step.

Document and review your findings from UAT. Compare the test results to the user needs and the use case you documented earlier. The project team should be involved. Include the project manager, sponsor, stakeholders, IT, admins, developers, and designers.

Discuss whether the app needs further development or if you’re ready to go live as-is.

Take extra care to control the scope of potential changes so that you do not end up in a perpetual development cycle without going live. Determine which changes are enhancements or bugs to avoid confusion. You may identify potential improvements during UAT and choose to act on them later, after deployment.