Please login or join to subscribe to this thread
UAT is owned and conducted by the business team.In all my projects and experience, once QA completes and handsover to UAT, as a PM you track the UAT progress by using the status meetings as the platform. The reports such as failed, passed, incomplete, complete etc in detail are produced by the business, if not, you as a PM can capture such detail in an excel sheet or pre-defined format and report to the PMO. We used Sharepoint for everything.
Each project should have an agreed test plan/strategy. Within the plan, the management of UAT should be covered. Such topics as minimal times each test script is run, how to report defects, threseholds for various severities, etc, should all be detailed. There are many commerical applications that will assist, or some manual (such as spreadsheets).
You have to make sure you have visibility into acceptance testing. You need to keep constantly up-to-date on the progress made as well as the reporting and fixing of defects.Consider having people shadow the testers to see if some of the problems are due to a lack of training.
What process phase is User Acceptance Testing (UAT)?
Some additional points to the already great feedback from Deepa, Gary, and Stephane above.
1. Make sure that the definition of "done" is circulated to all testers. UAT testers usually are not privy to the design and build phases and do not have the context of the project. They need to be made aware of what exactly they are testing (even if it doesn't match their personal expectations).
2. Ensure that a strict definition of non-conformance defects and one of new requirements is circulated. UAT testers often bring a fresh viewpoint that may lead to changes. The project team needs to be aware as to which observations are defects in the scoped build and which observations are fresh requirements. A hard stance might need to be taken on any new requirements.
all the comments above are useful, thanks. I´ll begin with UAT in a few weeks.
See the V model. (https://en.wikipedia.org/wiki/V-Model_(software_development) Not because I am saying you have to use it (I am using it in software and non-software products mainly today with Agile environments) just because I think is a good source to understand all related to validation and verification. Sorry for directing you to wikipedia.
Only one additional note: UAT isn't training, sometimes users forget that :)
Track UAT by first writing UAT strategy, plan, then scripts. Enter in PM database. Track progress & results. once approved, require use and managers signoff signature.
Please login or join to reply