Risk is a combination of the probability and consequences of unfavourable events.
The most probable causes of risks in Software Testing include
incorrect scheduling (wrong project assessment, distribution of tasks);
inaccurate customer requirements (requirements change during the work on the project);
violation of specifications (overload requirements/no exact requirements);
low productivity (inexperienced specialists).
Risk detection The risk detection process must be included at each stage of product development to think over the previously identified risks and find new ones.
The stages of risk detection include Brainstorm. At this stage, various techniques are used to define the main cause of the origin of the Risk. Script building It is the process of making a detailed scenario on how can this or that issue happen, by what steps, under which circumstances, etc. Root cause analysis During this stage, it is necessary to analyse the difficulties faced earlier and their reasons to prevent them in future work.
Software Testing Risk categorisation
Software Testing Risk Category1-Schedule
Schedule risk is the likelihood of failing to meet schedule plans and the effect of that failure. It exists in every schedule and is impossible to predict, with complete confidence, the length of time necessary to complete an activity, meet a milestone, or deliver a system.
Project schedules get slip when project tasks and schedule release risks are not addressed properly. Schedule risks mainly affect a project, which may lead to project failure.
Causes of Schedule risks include
Wrong time estimation
Resources are not tracked properly. All resources like staff, systems, skills of individuals, etc.
Failure to identify complex functionalities and time required to develop those functionalities.
Unexpected project scope expansions.
All schedules come with Risk, so learning to address some of the more common risks associated is an important step to their mitigation.
Avoid Schedule Risks by
Reduce the number of Critical Paths
Reduce Activity Dependencies
Schedule Risky Activities Earlier
Plan Regular Schedule Reviews
Summary Software test planning comes with schedule risk. And this schedule risk may be a significant factor in the failure of a project. Look to minimise the number of critical paths to help in avoiding schedule risk. Schedule path convergence is a major risk, so modifying the work so a respective activity has fewer predecessor dependencies. Do not delay complex efforts. It is very difficult to see beyond the horizon, so avoid scheduling errors by planning regular reviews of your long-duration testing project.
Software Testing Risk Category2-Budget
Budget risk is the potential for the estimates or assumptions built into a budget to turn out to be inaccurate. All budgets are based on future-looking forecasts that typically involve some degree of uncertainty.
Causes of Budget risks include
Wrong budget estimation.
Cost overruns
Project scope expansion
Avoid Budget Risks by
Review similar projects
Estimate accurately
Factor in tax
Plan your work
Manage scope
Continuously forecast
Reassign resources
Leverage technology
Summary Cost overrun, or any sort of expense that pushes a project past the agreed-upon budget, is something which a test manager must constantly be vigilant about. By utilising the avoidance techniques mentioned above, a test manager can prevent Cost overrun.
Software Testing Risk Category3-Operational
Operational Risk is defined as the Risk of loss resulting from inadequate or failed internal processes, people, controls, systems or from external events.
Causes of operational risks include
Failure to address priority conflicts
Failure to resolve the responsibilities
Insufficient resources
No proper subject training
No resource planning
No communication in the team.
Avoid Operational Risks by
Task segregation
Restraining complexities in business processes
Reinforcing organisational ethics
The right people for the right job
Monitoring and evaluations at regular intervals
Periodic risk assessment
Look back and learn
In summary, The critical task is how organisations can implement the seven steps for a successful operational risk management program. A corporate governance, Risk and compliance platform enabled by technology can effectively support the implementation of the 7-step approach to active risk management.
Software Testing Risk Category4-Technical
Technical Risk is the possible impact changes could have on a project, system, or entire infrastructure when an implementation does not work as anticipated. This will prevent issues without warning and drastically decrease the required efforts to alleviate sudden infrastructure or system problems.
Causes of Technical Risks include
Continuous changing requirements
No advanced technology is available, or the existing technology is in the initial stages.
The product is complex to implement.
Difficult project modules integration.
Avoid Technical Risks by
Identify key risks, measure probability, and impact
Analyse security threats
Analyse the Risk of hardware and software failure
Analyse outsourcing risks
Identify controlled technology
Measuring impact
Rank potential risks and specify desired outcomes
Summary As the data is collected and analysed, the organisation reaches a decision point. This decision cannot be made by considering technology risk alone. After all the risk factors have been analysed, an organisation must choose from the risk management options, including Risk avoidance, Risk transfer, Risk Reduction, and Risk retention. An organisation must prepare a strategy based on the risk management option they have chosen.
Thank you so much for putting in the time to come visit the all-things-testing blog.
Best regards
all-things-testing
PS: Please write back to me if you need assistance, so I can help you with more information on Risk identification, Risk Analysis, Risk Evaluation, Risk Mitigation, Risk Monitor and Review.
Comments