RISK MANAGEMENT PROCESS
Risk Analysis is the integral part of the software development and testing cycle.
Risks can be identified based on the categories of the risks. The risks can be broadly classified in two categories depending upon the nature of the same. These are –
1. Generic Risks:
Generic risks are a potential threat to all solution integration projects. Hence the nature is universal. The generic risks shall be described in the Organization Risk Database and if the Project Lead/Manager feels that no special treatment is required for this kind of risk they can mention the same from the Risk Database without performing any separate analysis for the same.
Some of the Generic risks are:
• Scope of work – risk associated with the overall scope of work of the project.
• Business impact – risks associated with constraints imposed by management or the market place.
• Customer characteristics – risks associated with the sophistication of the customer’s and the developer’s ability to communicate with the customer in a timely manner.
• Process definition – risks associated with the degree to which the process has been defined and is followed by the organization.
• Environment – risks associated with the complexity of the system to be built and the “newness” of the technology that is packaged by the system.
• Staff size and experience – risks associated with the overall technical and project experience of the project team who will do the work.
2. Project Specific Risks
These are associated with special characteristics of the project. Examples of such risk are:
• Type of the customer: Customer changes the requirements very often. This type of customer where volatility of requirements is high is not a common feature to every project.
• The onsite environment set up for testing is not matching with the offshore environment.
• There is no member from Customer side involved in this project, who can be consulted for any problem related to project.
Please let us know if you have queries or questions on above.