The topic of User Acceptance Testing (UAT) is an important one in CPM implementations. UAT is the point in an implementation where you as the client take time to go through a thorough examination of the solution and confirm that all aspects are working as intended. UAT testing is a key part of any CPM implementation because it gives you as the client the confidence to move into production knowing your system is working as expected.
Here are some important considerations when entering a UAT phase:
Prepare in advance
Ideally, testing preparations start at the requirements gathering state. While designing the solution components, data feeds, and output reports, it is encouraged that how to test the final solution is also being discussed. Typically, you’ll need the following key pieces to conduct testing appropriately:
- Test Plan
- Test Cases
- Test Scripts
- Test Users (outside of your core project team)
Keep an issues log
We cannot stress enough how important keeping an issue log is. An issue log is a way to track all problems, bugs, minor tweaks, etc. that have been found. It is important to keep track of these things so that the team can have a list of everything that needs to be solved before you can comfortably move to production.
- That date the issue was found
- The name of the person who found it
- A detailed description of the problem
- A severity rank
Think about edge cases when you are testing
The workflow may work for a standard user, but what about that one person who has multiple roles, and specific data permissions? Your report is pulling in data correctly in the main reporting currency, but what about at a subsidiary level using EUR or GBP?
It is important to test a system under the most strenuous circumstances it is likely to face in order to ensure that it works as expected.
Understand that there will be issues
Strong communication is crucial during these unprecedented times. If the content is not effectively communicated through video chat or emails, it may result in miscommunications and misinterpretations as they are common when working remotely. When concerns are expressed in advance, appropriate actions can be taken before the issues impact the overall project delivery.