Skip to content
← All CTFL glossary terms

Risk analysis

Identifying risks and assessing their likelihood and impact to determine each risk's level and appropriate responses.

Syllabus chapters: 5

Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.

Related terms

Risk analysis in a practice question

Question 1

A product risk analysis rates the payment module's risk level as high and the help pages' risk level as low. What does this result support?

  1. Giving both areas the same coverage so that the residual risk is spread evenly
  2. Using more rigorous test techniques and higher coverage on the payment module
  3. Dropping the help pages from the test scope because their risk level is not high
  4. Deferring the payment module until late, so the risk analysis can be repeated first
Show answer
  • Giving both areas the same coverage so that the residual risk is spread evenlySpreading effort evenly is the opposite of focusing it to minimize residual product risk.
  • Correct answer: Using more rigorous test techniques and higher coverage on the payment moduleTechnique choice and coverage to be achieved are set from the risk analysis results.
  • Dropping the help pages from the test scope because their risk level is not highA low risk level is still a risk, and the analysis determines the scope rather than emptying it.
  • Deferring the payment module until late, so the risk analysis can be repeated firstThe results are used to find critical defects as early as possible, so deferral works against them.

The goal of product risk analysis from a testing perspective is to focus the test effort so that the residual level of product risk is minimized. Its results are used to determine the test scope, the test levels and test types, the test techniques to be employed and the coverage to be achieved, to estimate the effort per task, and to prioritize testing in order to find the critical defects as early as possible.

Syllabus section 5.2.3

Question 2

Which activity do testers perform when they take part in iteration planning?

  1. Breaking user stories down into tasks, particularly testing tasks
  2. Defining and re-defining the product backlog for the coming release
  3. Refining larger user stories into a set of smaller user stories
  4. Determining the test approach and planning the testing for the release
Show answer
  • Correct answer: Breaking user stories down into tasks, particularly testing tasksBreaking stories into tasks, particularly testing tasks, is iteration planning.
  • Defining and re-defining the product backlog for the coming releaseDefining and re-defining the product backlog belongs to release planning.
  • Refining larger user stories into a set of smaller user storiesRefining larger stories into smaller ones belongs to release planning.
  • Determining the test approach and planning the testing for the releaseDetermining the test approach for the release belongs to release planning.

Testers involved in iteration planning participate in the detailed risk analysis of user stories, determine the testability of user stories, break user stories down into tasks — particularly testing tasks — estimate test effort for all testing tasks, and identify and refine the functional and non-functional aspects of the test object. The other three options are all release planning activities.

Syllabus section 5.1.2

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.