User Acceptance Testing (UAT),one of the most stressful stages of quality assurance
summary
Claims a practical UAT governance framework with concrete thresholds and tools, not vague advice: use SonarQube for code quality, require INVEST stories and traceability between requirements tests and issues, measure 90–95% defect containment and keep reopened defects near 10%, enforce defect lifetime limits (30–40 days) and P1 SLA responses within 1 hour, run UAT dry runs with a named UAT test manager, maintain QA dashboards and an execution log, and hold daily kickoff and end‑of‑day ceremonies for monitoring and issue escalation.
AI-written summary · about
chapters (13)
- 0:00UAT stress and goals
- 1:09QA before UAT
- 3:39QA dashboards and metrics
- 6:07UAT pitfalls to avoid
- 8:16Entry/exit criteria risks
- 10:22UAT governance framework
- 10:44Scope, schedule, risks
- 11:50Roles, responsibilities, RACI
- 12:54SLAs for UAT support
- 13:38UAT guidelines and logs
- 14:43Monitoring UAT ceremonies
- 15:47UAT acceptance and exit
- 17:13Q&A
related talks
48mWhat is UAT and, more importantly, what it isn’t
24mCustomer Testing and Acceptance
29mUAT Validation in Production
36mDevising a Project Test Approach
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
43mLean QA: Automation, Monitoring, Experiments
51mQuality Assurance vs. Testing
56mThe End Game