Risk Based Testing in Agile Teams
summary
Adapts risk based testing to scrum teams by running short 10–15 minute risk meetings per user story, focusing on “what can go wrong” (risks, not cases), inviting testers and experts, and prioritizing with a 1–5 probability × damage score then factoring testability to produce a test priority and strategy. Applied on a large .NET industrial automation project, it uncovers surprising edge cases (rotated circle alignment), enables targeted automated tests, uses simple Excel tracking, and improves early defect detection and team motivation while warning of false security.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:21Who Taught You How To Ride a Bicycle
- 10:00Shift Left and Shift Right
- 20:46Tips for Collecting Risks
- 22:08Check Features in Combination
- 24:28Planning Meetings
- 25:22Test Strategy
- 30:40Dangers of this Risk Based Testing
- 33:38Benefits
- 35:28Questions
- 38:58How Do You Treat the Results of Taper Calculation
related talks
28mRisk Based Testing in Agile Teams
53mReady to Run the Risk? - Applying a Risk-Based Approach to Testing
39mRisk-based testing in practice: how to work with it
32mRisk-Based Test Effort Management
46mInside Scoop on Risk-Based Testing
33mAgile Software Testing
49mTest Strategy in a SCRUM Environment
44mFive Key Challenges for Agile Testers tomorrow