PNSQC 2014 - Alicia Cook
summary
Argues that pairing business analysts and quality analysts reduces delivery risk on highly integrated systems by keeping QA embedded early and BAs involved through development and testing; cites a Forrester report (two years earlier) recommending end-to-end training, pairing with designers/developers, and exposing teams to maintenance. Gives an agile case study called Team Awesome where joint BA/QA reviews uncover requirement gaps, drive prioritized testing by business value, and catch defects classified as requirements/configuration so teams can fix root causes and co-locate BA and QA for faster feedback.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:58Why
- 1:55Complexity
- 2:57The vicious cycle
- 3:44What can QA do
- 4:50How can QA help
- 7:56QA on agile teams
- 9:01QA and BA values
- 10:38Advantages
- 11:13Questions
- 12:10Where is the value
- 13:23My experience
- 14:46Best practices
- 16:01Ideal world
- 17:17Defects
- 18:26QA Lead
- 20:10QA vs BA
- 22:01Common Challenges
related talks
37mDavy Kenis: QA No More: Revolutionizing Software testing
07m“Importance of Quality Assurance to a delivery team”
40mReal Quality Assurance from an Agile and Lean Viewpoint
53mIs having a QA a symptom of a dysfunctional team?
39mQA Has a Voice
01h 21mPNSQC 2013 - Michael Mah
49mDeveloper + tester = quality++
46mDeveloper + Tester = Quality++