Developing Product Review Practices (That Work)
summary
Product review practices that catch real risks: a requirements review checklist that asks show me the data, verifies business rules, and scores consistency and integration risk; heuristics that flag unrecoverable actions so teams add undo or confirmation; dogfooding reveals an auto-merge “auto magic” that erased contacts and an export flow hidden behind an ellipsis that takes four clicks and missing notifications, driving specific fixes and measurable reductions in support tickets.
AI-written summary · about
chapters (9)
- 0:00Start
- 10:29Requirements clarity.
- 10:55Data and use cases.
- 11:26Consistency*.
- 12:16Project and product risk assessment.
- 18:40Realistic and complex client use cases
- 19:21Layout and elements
- 20:07User experience
- 20:31Patterns familiarity
related talks
27mNo product to test yet? No problem.
11mTransforming Code Review into a Learning Tool for QA Teams
41mExits on the (QA) Highway to Hell
24mThe Testers’ Secret Weapon – Code Reviews
08mReviewing your test automation strategy"
09m"How to be a customer obsessed tester?"
37mBest Practices for Accelerating Delivery
34mGoldilocks And The Three Code Reviews