Customer Testing and Acceptance
summary
Claim: make customer acceptance continuous, not a phase, with sprint-by-sprint validation and measurable satisfaction. Shows concrete practices: persona definition via a mandatory questionnaire, mind map as a living test/QA strategy artifact, and satisfaction survey after each sprint that must trigger action. Recommends supporting UAT with test data and seats-at-the-keyboard sessions, recording acceptance in JIRA or the mindmap, and aiming for continuous UAT even inside iterations (Kanban example) so acceptance is verifiable and repeatable.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:26Defining our goal
- 0:59Identifying people
- 3:29Customer Satisfaction
- 4:00Four Typical Phases
- 7:08How to Help
- 8:11Planning
- 10:45Feedback
- 13:23Satisfaction
- 14:53Education
- 16:15Test Strategy
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
01h 00mAcceptance Testing Sounds Easy, But Is Hard to Get Right
09m"How to be a customer obsessed tester?"
48mWhat is UAT and, more importantly, what it isn’t
01h 08mTesting Is Your Brand: Sell It!
58mAppendix A: What We´ve Learned Since Agile Testing
49mThe Secret to Successful Testing