What Is Software Risk And Software Risk Management?

Risk is the possibility of a future loss or problem. It often arises from a lack of information, control or time. In software development, losses can include higher production costs, poor quality or late delivery. Risk exists because the future is uncertain and a plan cannot include every known and unknown factor. Internal risks are within the project manager’s control; external risks are outside it. Risk management aims to:

  1. Identify risks.
  2. Reduce their impact.
  3. Reduce their likelihood.
  4. Monitor risks.

Project managers deal with three kinds of uncertainty:

  1. Known knowns: Facts the team already understands. For example, too few developers can delay delivery. Record these risks in the project management plan.
  2. Known unknowns: Risks the team understands but does not know are present in the project. For example, poor client communication can lead to incomplete requirements. The team knows that risk exists, but may not know whether the client has communicated every detail.
  3. Unknown unknowns: Risks the organization does not yet recognize. They often involve unfamiliar technology or tools. For example, a client may suddenly ask the team to use technology it does not understand, exposing the project to previously unknown risks.

Quantifying software risk involves:

  1. Describe the risk event precisely.
  2. Define the probability that it will occur.
  3. Estimate the potential loss.
  4. Define its potential liability.

Risk management includes these processes:

  1. Software Risk Identification
  2. Software Risk Analysis
  3. Software Risk Planning
  4. Software Risk Monitoring
The following sections explain each process.

Software Risk Identification

To identify risks, study problems from earlier projects. Review the current plan for vulnerable areas. Converting it into a flowchart helps you examine the essential parts. Use brainstorming to identify known unknowns. Evaluate decisions involving technical, operational, political, legal, social, internal and external factors.

Software Risk IdentificationCurrentProjectReview the PastProject HistoryAssess the PracticesBeing Followed inthe Present ProjectCome Up withCreative Ideas forFuture Projects
Open Full-Size Diagram

Software Risk Identification

Define the processes used to identify risks. Record each risk’s unique ID, identification date, description and other relevant details.

Software Risk Analysis

Risk analysis identifies and categorizes risks, then examines their level, likelihood and impact. Express likelihood as a percentage after considering the technical conditions that could cause the risk, including:

  1. Complexity of the technology
  2. Technical knowledge possessed by the testing team
  3. Conflicts within the team
  4. Teams being distributed over a large geographical area
  5. Use of poor-quality testing tools

Impact means the consequences if a risk occurs. Understand how the customer, business and wider community could be affected:

  1. Loss to the customer
  2. Harm to the business
  3. Loss of reputation or harm to society
  4. Monetary losses
  5. Legal actions against the company
  6. Cancellation of business license

Assess the risk level using:

Qualitative Risk Analysis: Classify each risk as:

  • High
  • Low
  • Medium

Quantitative Risk Analysis

This approach uses numbers to estimate likelihood and impact. For example, a 10% chance of a 10,000 USD loss gives an expected loss of 1,000 USD. A probability alone does not tell you how serious the outcome would be.

Software Risk Planning

Risk planning involves:

  1. Define preventive measures that reduce likelihood.
  2. Define measures that reduce the impact if the risk occurs.
  3. Monitor processes continuously to identify risks early.

Software Risk PlanningInitial System RiskAcceptableUnacceptableWaivedAssumedUndiscoveredReducedEliminatedor AvoidedResidualSystem Risk
Open Full-Size Diagram

Software Risk Planning

Software Risk Monitoring

Integrate risk monitoring into project activities and check the highest risks regularly. Monitoring includes:

  • Track risk plans for major changes in plans, attributes or other conditions.
  • Prepare status reports for project management.
  • Review risks and close those whose impact or likelihood has reached the lowest possible level.
  • Look regularly for new risks.




We guarantee that your free online training will make you pass your Software Testing Certification Exam!

  1. 01

    Register Online

    Choose your Accredited certification and complete your registration.

  2. 02

    Receive Your Access Code

    Your personal exam access code is delivered instantly by email.

  3. 03

    Prepare & Take Your Exam

    Study your free training and answer your 50 multiple-choice questions online.

  4. 04

    Earn Your Lifetime Credential

    Receive your worldwide-valid certificate and verifiable digital badge.

Accredited Software Test Manager Certification™ sample
Register for Certification

YOUR FREE PREMIUM ONLINE TRAINING

Your Software Testing Revealed, Second Edition, Is Ready.

We created your training with a consortium of renowned business and people leaders, software testing coaches, mentors, experts and authorities from all major industries. Everyone visiting International Software Test Institute™ can access it. Find the materials through Your Free Software Testing Book and Your Free Premium Software Testing Training in the top menu.

These materials are the copyrighted intellectual property of International Software Test Institute™. We share them freely with everyone because sharing our expertise serves software testing professionals and helps the field develop.

Your certification examination uses multiple-choice questions. Read your online training to build the knowledge you need to pass your examination and earn your Software Testing Certification.

We guarantee that your free premium online training will make you pass your Software Testing Certification Exam!