As the last link before the product is launched, let's take a look at the acceptance and review stage after the project is landed, and how to do the overall product acceptance.
This article focuses on the acceptance and review stage after the project is landed, and the main content revolves around [product acceptance], which is divided into:
First, the overall description of product acceptance
Second, the product acceptance content framework
3. UAT acceptance report template
1. Introduction: Introduce the objectives and background of the version
2. Purpose of acceptance:
Verify whether the new requirements of the system are consistent with the product requirements, and determine whether the system meets the online standards.
The report is intended for: development, testing, product, operations, etc.
3. Acceptance type & personnel & acceptance time
4. Scope of acceptance:
- Requirements document (with online documentation)
- Core Test Scope
- Core Test Process (with UAT Acceptance Use Cases)
- Description of the test device (Windows and iOS models, system versions)
5. Acceptance conclusion:
- Product Acceptance Conclusion Form (Header: Acceptance of the main process module, design problems, whether the investigation has been resolved)
- Overall evaluation conclusion: For example, the current acceptance results meet the online conditions, so the acceptance conclusion: passed.
- Implementation: A total of 33 use cases were designed and 33 were approved. There are 5 bugs in total.
- Defect Statistics Table:
- Header: version number, fatal number, severe number, common number, prompt number, and total count
- Use case coverage statistics: For example, the current version of all module use cases has been designed to cover the function points involved in the test scope as much as possible, and the coverage rate has reached 100%.
- Performance test evaluation
- Safety testing and evaluation
- Usability test evaluation
- Compatibility test evaluation
6. Evaluation of the test process
7. Statistical table of test results
8. UAT legacy issues and related tips
9. Other risks and avoidance measures
10. Attach the source file of the product acceptance use case
This article was originally published by @刘一手 on Everyone is a Product Manager. Reproduction without the permission of the author is prohibited.
The title image is from Unsplash and is licensed under CC0.
The views in this article only represent the author's own, everyone is a product manager, and the platform only provides information storage space services.