SOFTWARE TESTING AND RISK MANAGEMENT

-

Software testing is an effective Risk Management technique in product development. 

When testing the product, right from requirements analysis (Shift-Left testing), the Test Manger helps in deciding on the Risk Management approaches.

These four approaches are guided by analysis of the LIKELIHOOD & IMPACT of the identified risk(s) which are;

1. Treat: Can the risk be reduced or eliminated completely? What should I do if my team/organisation cannot treat it?

2. Transfer: If my team cannot treat it? can someone treat it for me when it eventually crystallises? How much would it cost if I transfer to a third party?

3. Tolerate: What if I cannot transfer the treatment to a third party? Can the product survive the anticipated damage should the risk crystallises? What loss of reputation would this cost the company?

4. Terminate: What if we decide to remove the feature that has that risk? Is the feature necessary for our next release? How useful will the product be to our users if we remove the feature?

These are the tough questions (and more) that Risk Managers need to be asking and providing solutions to the product owners. They follow these stages of risk mitigation and suggest ways of improving the product.

Software Testers (or Risk Managers) are not just bearers of bad news. They also provide glad tidings by pointing out the best way to mitigate risks in products and processes. They assist in redesigning the products and identifying the most viable option at any given time.

Comments

Post a Comment

Popular posts from this blog

It's all About the Next Person Taking Over From You.

-
If there is one thing engineers and developers despise, is DOCUMENTATION! It takes away the joy and the pleasure we derive while building software. However, documenting your code is a Gift for Future Engineers and Developers. Writing clean code is essential, but even clean code can be puzzling without context. Documentation is not just for you; it is a lifeline for future engineers. It captures the why behind your work, making transitions and scalability smoother and preserving continuity in the long run. Clean code matters not just for good Code Quality, It goes beyond that. Even the best-structured code can leave future developers guessing about design choices and updates if there is no documentation to provide context. Imagine a new engineer taking over your project. They may find the code clean, yet the logic or the reason behind specific decisions may not be immediately clear. Having a backstory (Documentation) helps them understand not only what the code does, but why it w...
Read more

Why do I need a separate testing team if developers can test the product themselves?

-
Having a separate testing team is a beneficial way to ensure that the product is tested and validated from an unbiased point of view. Developers may be too close to the code of the product to provide an unbiased evaluation of it, and may not be completely objective about the quality of the product. A separate testing team, that is entirely independent from the development team, can provide a more accurate assessment of a product. This can result in a better and more reliable product that meets quality standards. While developers can and should test their code to ensure that it meets the expected functional and non-functional requirements, there are several reasons why having a separate testing team can be beneficial: Independent perspective and reduced bias: A software testing team can provide an independent perspective on the software being developed. Developers may be biased towards their own code and may not identify issues that are present. Therefore, having a separate team to...
Read more

There Is No “Manual vs Automated Testing” Conflict - Cassandra H. Leung

-
I’m a little bit frustrated. Since Twitter died and I decided to start engaging on   LinkedIn   more, I keep seeing posts that perpetuate this idea of “manual” vs automated testing; us vs them.   There is no versus. Your civil war is manufactured. There’s room for everyone and we all want the same thing: good quality.   I’m frustrated by posts which pit people against one another; which disparage human testing; which claim automated checks bring less or no value;  which distract us from actually improving quality .   Testers are specialists. Automation is a tool. Specialists use tools. Not every tool is right for every job. A specialist knows which tools to use and when. What’s the problem here?   I specialize in exploratory testing. I’ve written some automation before and I’m actively working to improve those skills, not because I want to replace my exploration, but because I want to contribute more to making more room for it.   Think of making t...
Read more