Thursday, August 15, 2013

Performing Risk Managmant

As I already explained on previous articles, The Qa department is the bridge between the organization software and the clients.

Therefore, organizations should do major investments to make sure that they possess the best Qa teams that can supply the best protection for the organization and by achieving this goal the client receives a better product.
After explaining the importance of Qa for every organization we need to explain to the Qa limitations and principals when testing software.

Risk Management – this principle came from the timeline point of view. It's easy to understand that Qa takes the time that causes delays in the software release. Therefore Qa will never have unlimited time for testing. The solution is to perform a good "Risk Management" for version.
Risk Management will be dedicating to decide the tests priorities based on Risks that could be in some parts of the code.

For example:
If we have software that already tested in the previous version and the R&D added additional functionality that never tested we probably decide to perform more tests for the new functionality because the risk is higher then other parts in code that already covered before and therefore sanity or simple regression will be enough.
After this example we can understand that "Risk Management" cannot be determined "On the fly", therefore I suggest that every RM should be taken with the following Keys:

1.     Understand the software testing scale.

2.     Understand the time limitations of this project.

3.     Tests design should be written after we understand the change in code.

4.     Consult with R&D team to determine risks in specific parts in code.

5.     Make sure that everyone else understands the risk you take by reducing tests in other parts of the tested software.

6.     Understand the code parts that defects are really critical and may cause some major defects on other code parts.

7.     Document your reasons and conclusions regarding the risk you take.

8.     Understand that you cannot test everything.

9.     Understand the resource you have/or need to accomplish the risk analyses effort.

No comments:

Post a Comment

My Presentations