Hello, assumption, my old friend! Or can a tester make a good product owner?
summary
Testing skills translate into specific, actionable practices and tradeoffs: tester-to-product-owner moves depend on decision table driven acceptance criteria, drawing state transition diagram flows, pairing on refinement and using screen recordings to show thought process. Concrete claims include learning to prioritize after reporting 5,000–6,000 bugs and treating high-severity low-priority issues as deferred tech debt. Remedies focus on building trust by showing hands on troubleshooting, measurable validation steps, and converting vague stories into testable, incremental experiments.
AI-written summary · about
chapters (15)
- 0:00Tester-PO relationship challenges
- 1:12Product owner complaints
- 2:39Distrust between roles
- 4:06Assumptions vs facts
- 6:57Progress vs perfection
- 9:07Testing skills for harmony
- 12:24Building trust through collaboration
- 14:55Empathy in tech teams
- 15:57Q&A
- 16:17Becoming a skilled PO
- 17:40PO skepticism toward testing
- 19:03PO availability challenges
- 19:45Prioritizing technical depth
- 21:12Returning bad tickets
- 22:40PO knowledge of SDLC
related talks
37mProduct Owner In Test
15mThe Tester I Was and the Tester I Could Be
01h 08mTesting Is Your Brand: Sell It!
48mOwning Our Narrative
41mExits on the (QA) Highway to Hell
42mHow a Tester Can Help Improve the Quality of Requirements
37mWe Are The Testers: You Will Be Assimilated
14mBecome the CEO of your testing