Skip to content


How the heck do I perform a Risk Analysis?

Huib Schoots

Being a tester is to know what to test and to be able to discuss this with your stakeholders and your team. Risk will help you to find out.

Are concerned that your team or your testing is not oriented on finding the bugs that really matter? We all know that risks are a central theme in software development and still we struggle to use them effectively in our work. Risks will help us to evaluate if the product is good enough, and at the same time, will help us evaluate if the testing we do is good enough.

Risk-based testing means organizing your test strategy around suspected product risks. This means performing risk analysis before, during, and after testing as a continuous process. Before tests to guide the test process, during tests to adjust the strategy, and after the product is released to learn about risks that were missed before going live. Risk-based testing is a powerful way to focus testing and to justify the time and energy it takes to test deeply. It also helps to identify parts where shallow testing or no testing at all can be justified.

In this workshop we will do a risk-analysis on real software. We will use risk heuristics and focus on assessment rather than measurement of risks, since software risks cannot be measured most of the time. In this interactive and hands on workshop your will learn the basic concept of how to construct risk assessments and how they can be done systematically.

This workshop is for everybody who wants to learn about how to analyse and identify risks using heuristics. You will also get an insight how these risks can help you get the coverage you need in a practical way to deliver the quality your customer wants.


  • Learn how to do practical risk analysis
  • How risks help you to do solid testing
  • Heuristics that will make risk analysis practical and easy