Risk Based Testing in Agile Teams
summary
Claim: using risk-based test meetings per user story yields earlier problem discovery and produces "much less bugs" on the stories where it’s applied. Practicals: collect risks (functional, nonfunctional, side effects) on a notepad risk table, invite a system tester or architect, score probability × damage prioritization plus test effectiveness (1–5), then focus test automation and manual effort on top risks. Outcomes: smaller stories see measurable defect reduction, some teams benefit from just the risk list; beware time cost and false security.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:25About me
- 3:25Scrum teams
- 4:37Why riskbased testing
- 7:20Riskbased testing process
- 12:44Riskbased testing meeting
- 20:00Risk prioritization
- 24:28Benefits
- 25:41Risks
- 27:29Summary
related talks
40mRisk Based Testing in Agile Teams
53mReady to Run the Risk? - Applying a Risk-Based Approach to Testing
46mInside Scoop on Risk-Based Testing
39mRisk-based testing in practice: how to work with it
49mThe Secret to Successful Testing
32mRisk-Based Test Effort Management
15mHow to NOT waste time
17mRisks with Ticket Driven Software Testing