Risk-Based Testing (RBT) and Prioritisation

4.2 Risk-Based Testing (RBT) and Prioritisation

To make sure we focus our testing effort where it matters most, on the areas that have the highest impact on our customers, business, and systems.

• Identify high-risk areas early
• Look at features or components that:
  • Are critical to business operations or customer workflows
  • Handle sensitive or large amounts of data
  • Have complex integrations or dependencies
  • Have a history of bugs or instability
• Assess risk from two angles
• Business risk: Impact on customers, reputation, compliance, or revenue
• Technical risk: Complexity, new or changed code, integration points, or performance sensitivity
• Prioritise testing based on risk
• Test high-risk areas first and in more depth
• Medium-risk areas get balanced coverage
• Low-risk areas may have lighter testing if time/resources are limited
• Review and adjust regularly
• Update risk priorities when requirements, scope, or technical design changes
• Involve product owners, developers, and QA in risk discussions
  

Why this matters for DHI

By focusing on the riskiest areas first, we:

• Reduce the chance of serious bugs reaching customers
• Use time and resources more effectively
• Ensure quality where it has the biggest impact especially in complex solutions like MIKE and DHI Cloud platforms. Here is the sample risk assessment template that can be used to apply this guideline consistently and make adoption easier.