Uploaded byFrank Caron
QA + Product = Love
The document discusses the importance of alignment between QA and product management, illustrating this as a love story that leads to better project outcomes. It emphasizes that early collaboration results in improved acceptance criteria and successful product launches, ultimately benefiting both the team and customers. The author encourages QA at Points to consider capitalizing on this opportunity and outlines the steps needed to achieve effective collaboration.
QA + Product = Love
- 1. QA & Product ALove Story Frank Caron, Product Manager frank.caron@points.com
- 2. Once Upon ATime
- 3.
- 4.
- 5.
- 6.
- 7. The Moral OfThe Story ● Opportunity = pre-project alignment between QA & Product ● Early alignment = better acceptance criteria ● Better acceptance criteria = better launches ● Better launches = happier 4th floor (and customers!) ● Happy 4th floor = better products Ergo: We’ve the opportunity to build better products—together!
- 8. Epilogue ● Is thisopportunity something QA at Points wants to capitalize on? ● If so, how do we act on this given Points’ unique people, products, and processes? ● What are the next steps?
Editor's Notes
- #3 QA was a separate team QA received a finished product and 800 pages of specifications QA, and QA alone, was held accountable for quality QA operated in a black box Created a test plan for the entire product after it was built Filed bug reports that were closed during the final quarter of development Were hated by the dev and product teams; seen as pedantic and annoying Product and QA had a transactional relationship; “tell me it’s good or tell me it’s broken, and hurry up about it”
- #4 Agile brought product and QA together
- #5 Initially, we all thought cupid’s arrow in agile was going to be great, but… Specifications and documentation grew sparser, more out of date QA was brought in at the last second, mid-sprint, with unfinished product, and told to fix it QA struggled to match the new pace without documentation
- #6 We had big problems, but then.. One of the product managers decided to include QA in the definition phase to help define acceptance criteria QA was able to use their experience to predict problems and to ensure acceptance criteria pointed to or covered fringe cases A process was established QA would review acceptance criteria for each story QA would help to define certain acceptance criteria Acceptance criteria ownership was shared between QA and Product (but fought for by product)
- #7 With this new happy world... Acceptance Criteria, Sign off Able to reduce post-launch support requirements and warranty period bug cases by over 70%
- #8 Scenario No acceptance Criteria Second Scenario Acceptance Criteria, Sign off Able to reduce post-launch support requirements and warranty period bug cases by over 70%
- #9 Scenario No acceptance Criteria Second Scenario Acceptance Criteria, Sign off Able to reduce post-launch support requirements and warranty period bug cases by over 70%