What is UAT and, more importantly, what it isn’t
summary
UAT claims to answer whether the system is fit for business purpose not whether it meets every requirement so the talk shows concrete practice: run three-cycle UAT (tech, scripted SME, cold users), plan 10–20 tests per business process, allow six weeks minimum for fixes and retest, staff one test lead plus 2–5 users, use a production-like environment, prioritize scenario and exploratory tests, and refuse to accept incomplete releases (analogy: a car with missing wheels).
AI-written summary · about
chapters (23)
- 0:00Introduction
- 6:06What UAT isnt
- 8:07Typical consulting engagement
- 10:35What UAT is not
- 11:52System tests
- 12:50Supplier doesnt software
- 15:17Take courage
- 16:47Another classic
- 17:41Its not about finding defects
- 18:56Users worst enemy
- 22:13What UAT is about
- 23:01Its not hard
- 24:49Usability testing
- 25:58How to do UAT properly
- 28:25Getting the users in
- 30:27Training the users
- 33:02Design reviews
- 35:44Plan properly
- 38:50Allow sufficient time
- 40:10Engage with business users
- 41:32Resources
- 42:42Pragmatic
- 45:29What we have to do
related talks
22mUser Acceptance Testing (UAT),one of the most stressful stages of quality assurance
01mUAT, one of the most stressful stages of quality assurance
29mUAT Validation in Production
36mDevising a Project Test Approach
24mCustomer Testing and Acceptance
25mTIMING OF USABILITY TESTS
01h 08mTest Automation != Less Testers || Faster Testing || More Time For ET
56mThe End Game