User Acceptance Testing
The ultimate guide
Retrospective
There will always be things that could have gone better, and during this phase, it’s important to reflect on these for improving future projects. Hopefully, the project will have been a triumph, and with the successful implementation, you will need to positively feedback the project’s success to all stakeholders to encourage future UAT participation within the organisation.
Analyze and critique the project
- What was the level of issues found and was it acceptable?
- What was the level of defects found and was it acceptable?
- Where was time lost or gained?
- How effective was the communication process?
- How was the quality of the delivered results perceived?
- Consider the level of questions and concerns after/during the UAT
- Praise users and stakeholders where appropriate
Organize assets from the plan and results for future use
Collate assets and organize for future use
Test cases
Test scripts
Automated scripts
Creation of automated regression
Data and results
Adapt test policies if necessary
Once the reflection has been completed, adapt your test policy for future UATs
- What strategic changes would have created a better framework?
As with any Testing process, not all phases need to be implemented within every project, but each should be considered to achieve the best possible outcome.
Over the coming weeks, we will cover the whole approach to UAT in a step-by-step guide. If you have just found us you can catch up here on the Overview, Scope, Strategy, Planning, Preparation and Initiation, Detailed Plan, Execution, Review and Manage, and Repeat.
Coming up next – Conclusion
Let's talk User Acceptance Testing
Our user Acceptance Testing solutions ensure your software is delivered 60% faster with fewer errors, saving you thousands of dollars.
Fill in the form below or schedule a chat at a time to suit you
The post Guide to User Acceptance Testing. Retrospective appeared first on Original Software.
