Testing Risk Management

Software Testing Risk Management

As we know the Software Testing is the last phase of the SDLC, so it comes always under pressure and time constraint. For saving the time and money we have to prioritize out testing work, like which one have higher priority and one which have the less priority.

So here is the risk management and risk analyses are the main concerns of every project.

Definition: “Risk-based testing (RBT) is a type of software testing that prioritizes the tests of features and functions based on the risk of their failure”

Types of risk:

Schedule Risk:

Project schedule get slip when project task and schedule release risk are not addressed properly.

Schedules often slip due to following reasons:

1. Wrong time estimation.
2. Resources are not tracked properly. All resources like staff, systems, skill etc.
3. Failure to identify complex functionality and time required to develop that functionality.
4. Unexpected project scope expansion.

Budget Risk:

1. Wrong budget estimation.
2. Unexpected project scope expansion.

Operational Risk:

1. Failure to address priority conflicts.
2. Failure to resolve the priorities.
3. Insufficient resources.
4. No proper subject training
5. No resource planning
6. Lack of communication in team.

Technical Risk:

1. Continues changing in requirements.
2. Lack of advance technology.
3. Project is complex to implement.
4. Difficult to project module integration.

Risk Analysis: Risk analysis is the process of identifying the risk in applications and priorities then to test.