| || |
Can anyone help me to clear this doubts on Risk Analysis.
1)How will you do risk analysis for a project?
2)What are the risks in testing a project?
Re: Risk Analysis
1) Risks are any unwelcome events, which may occur during development or maintenance of the project, and make plans to avoid these events or, if they are inevitable, minimize their negative consequences.
RA is to identify potential risk events, their impact on project, sevearity (high, med, low) of event, No. of past occurences/probability of occurence (hi,med,low) , Indications of event if any, Alternate strategy and contengency plan.
Risks can be like : hw / network/power failure, team member on leave, team member leaving company etc.
2) As far as risks are concerned, testing project is almost like any s/w development project. Added risk is early release of new build before current build testing is satisfactorily completed.
Hope this helps you.
Re: Risk Analysis
There is not one way to do risk analysis. A number of techniques do exist. I suggest you do a search on google to find out more about it and then return with more specific questions.
Risks are different for each testing project. So providing you with 'the risks in testing a project' is not something that can be done like that.
There are 2 types of risks: risks related to the product (e.g. if functionality X is not availabl e the the company will loose Y), and risks related to the test project (e.g. if the developers do not deliver before that date, the test automater is not available for 2 months resulting in 4 months delay for the project).
Project risks can also be distinguished between internal to the test team (e.g. testers need training) and external to the test team (code is not delivered on time).