Home | About QAI | QAI Canada Home Page | Federated Chapters
Conference Home Page
Manager's Workshop
QUEST Magazine
Get Involved

Risk Management Workshop


Top Challenges to Addressing Risk

First: Properly Identify the Risk

Look at the risk and make sure it is not a:
    • Condition
    • Symptom
    • Event
    • Opinion
  • To determine if it is really a risk, ask if there is a $ impact if the risk occurs
    • Does it impact the schedule?
    • The quality
    • Or the mission you are trying to accomplish
    • What is the impact?

Second: Quantify the Risk Impact

  • Quantify as H,  M or L and assign a dollar value to that ranking if you can
  •  assigning a dollar value to a risk will always provide more value

Third: Effective Treatment

  • Identify a trigger point and put a timeframe on it

Risk Management Process

Establish the context
Identify the Risk
Quantify the risk
Treat/Mitigate the risk
Monitor the risk
Report the risk

Testing Risks Examples

Lack of test cases
Management cuts schedule
Changing requirements

Project Risk Example

Schedule delay due to regulatory changes to statute x

Risk Treatment and Mitigation

Review status of law change - (weekly) - Nov 1
Review draft change (x days after release 1)
Assess schedule impact (y days after release)
Enter risk
Proposed revised schedule
Re-baseline plan

Back to top

Testing Risk Group Exercise

Worked on as a group. These were all theoretical numbers we made up. This problem, however, was too broad; therefore it was hard to really define what the specific risk could be.

Problem - Changing Requirements


  • Schedule
  • Budget
  • Quality
  • Facilitator suggested that we should just focus on one risk, whatever has the highest impact or is most important


  • Schedule increased by 14 days
  • Budget will go up by 14 resources @ $500/day
  • Quality - defects will go up, rework involved in re-doing regression testing

If the impact of the changes to requirements is:
Low - Accept the risk/no rewrite (of test cases or scripts)
Medium - If the value outweighs the cost - re-test/expand schedule etc.
- If the value does not outweigh the cost - reject change or defer testing to another release

High - Make the changes and adjusts costs/schedule as required

Back to top

Post-Conference: Agile Panel Discussion | Better Test Planning Solutions Workshop | Risk Management Workshop
Building Effective Measurement Solutions Workshop
| Challenges of Test Automation Solutions Workshop


Quality Engineered Software & Testing (QUEST) Conference - Copyright © 2008