User acceptance testing (UAT) provides validation that a project has delivered a workable solution. UAT is a common testing procedure in software projects, but it also makes sense as a quality check in cross-functional projects and supply chain projects. Identifying scenarios and testing them is part of managing project change.
- User acceptance testing or UAT is a process that's often used in IT projects but the same approach is used in other places too and in this video we'll learn how to use UAT to complete the change to the new system in your projects. The idea behind UAT is to actually see your new system in action. Doing the things that it's supposed to do before you sign off and accept that the system is complete.
UAT involves testing the system by working through scenarios that resemble the real processes that the new system will need to support. So let's take a look at how the team at our example company, H Plus Sport, is using UAT to support their project. The project is centered around handling online orders so one of their UAT scenarios is that a customer logs on to the H Plus Sport website and places an order. Then the order is directed to the right people in the company, step by step, all the way through until the product is shipped out to the customer.
Since they're opening a new distribution center another scenario in their UAT is ordering products from a supplier, receiving them into the facility and making them available for shipment. Testing these scenarios will provide assurance that everything works the way they expect it to. If they run into any surprises they'll add them to the action item log and make a decision about how to resolve them. Their UAT will end with a sign off from the functional team leaders and the project manager, confirming that everything worked as planned in each of the scenarios.
The benefit to doing UAT is that it reduces the risk of an unexpected problem, either during Go Live or once the system is up and running. But every scenario costs money and takes time so be selective about your scenarios. Here are two suggestions to keep in mind when developing your own UAT plan. First the goal of UAT is to test the new processes, the new system of the building and everything related to the project in a realistic setting.
So try to avoid taking shortcuts or skipping over steps that will need to occur in your live process. Second, each of the functional teams has probably done a lot of testing already on their pieces of the project but that's different from UAT because UAT tests whether the essential processes work from beginning to end. User acceptance testing is a great way to validate that things are working the way they're supposed to. When you're making a change planning and executing an effective UAT will reduce the risk for your project and make you more successful as a project leader.
- Name who is responsible for approving the resources for the project.
- Recall what the spine of a fishbone diagram represents.
- List characteristics of the environment.
- Identify the tools used for mapping processes.
- Recognize what needs to be captured on the action item list.
- Recall what project metrics should be related to.