Risks
We started of by distinguishing between risks for the product, project, people or business. We then zoomed into risks for the product, and its variables, i.e. properties and purpose of the thing we’re testing and the risks associated with those, using Dan Ashby’s Risk Model:
We looked at the “impact x likelihood” formula as a way to prioritise risk - which also can be a good way to drive test focus. If we don’t know yet how likely a scenario would be, but we know that it would have a catastrophic impact, can we run an experiment to find out?
And we introduced some techniques and Heuristics to uncover risks:
- Ask “What could go wrong?”, “What’s the worst that could happen?”
- “Negative Internal Press Release” exercise (1, 2)
- Mike Talks: Oblique Testing
- TestSphere, especially used for RiskStorming
And had a quick go iterating through risks of a chair!
Resources at a Glance:
- Mike Talks: Oblique Testing
- Marcel Gehlen: RiskStorming - Mapping Risks with TestSphere
- Negative Internal Press Release: div, esp. Ian McAllister: What is Amazon’s approach to product development and product management? / Sandy Mamoli: Agile Project Inception with a Press Release
… and some more:
- Cem Kaner: Risk Based Testing
- James Bach: Heuristic Risk-Based Testing
- James Bach: Reinventing Testing: What is Integration Testing? (part 2)
- Jenny Bramble: Risk Based Testing Because You Can’t Do EVERYTHING
- Andy Glover: Risk Based Testing
- OWASP Risk Rating Methodology: