Product Owner In Test
summary
Proposes a new role, Product Owner in Test, that owns product‑level testing, release signoffs and org standards independently of engineering; requires ~5 years QA/dev experience and basic programming. Demands entry criteria (DB/API access, unit‑test counts), delivers documentation and demos, renames pass/fail scripts to check cases, and treats issues as improvement opportunities. Cites finding 108 bugs across four products, later shrinking to 4–5, plus examples like unencrypted passwords and integration failures; recommends standardized lower environments, code freezes and pre/post release signoffs.
AI-written summary · about
chapters (32)
- 0:00Product Owner in Test intro
- 1:04Testing vs checking
- 2:34From manufacturing to testing
- 3:14Waterfall testing legacy
- 4:19Agile testing challenges
- 5:47Why requirements fail
- 7:11Bugs love-hate
- 8:20Requirements cause bugs
- 10:08QA as scapegoat
- 11:53Broken processes ignored
- 13:00Non-tech QA roles fail
- 14:09Bugs to improvements
- 15:57QA struggles recap
- 16:40Security testing lessons
- 17:45Integration testing failures
- 18:25Know your product
- 19:06Need Product Owner in Test
- 20:10PO in Test qualifications
- 21:33PO in Test responsibilities
- 23:42Testing approach & docs
- 24:27Rename test cases
- 25:48Issues as improvements
- 26:52Product demo & collaboration
- 28:20Testing recommendations
- 29:03One PO per product
- 29:24Educate on data & standards
- 30:50Standardize lower envs
- 31:57Set release expectations
- 32:40Danger of MVP-first
- 33:46Technical requirements matter
- 34:26What PO in Test is not
- 35:29Why companies should care about this role
related talks
24mHello, assumption, my old friend! Or can a tester make a good product owner?
37mWe Are The Testers: You Will Be Assimilated
51mQuality Assurance vs. Testing
43mSoftware Developer in Test: Who Is That?
46mProject Culture and Team Responsibility for Quality
01h 08mTesting Is Your Brand: Sell It!
53mIs having a QA a symptom of a dysfunctional team?
36mWhy a Growing Company Needs a Growing QA Team