Risk Management is an approach that helps in managing and make best use of the available resources. A computer code project may be laid low with an out sized sort of risk so as to be ready to consistently establish the necessary risks which could have an effect on a computer code project. It is necessary to reason risks into completely different categories. The project manager will then examine the risks from every category square measure relevant to the project.
Principles of Risk Management:
There are 5 principles of Risk Management. They are:
- Global Perspective:
Larger system definitions, design and implementation is considered. The opportunity and the impact that the risk is going to have is looked. View software risks in the context of a system and the business problem planned to solve.
- Forward Looking View:
Looking at the possible uncertainties that might dragged. Possible solutions of the risks that might occur in the future are considered. Think about the risk which may occur in the future and create future plans for managing the future events.
- Open Communication:
This enables the free flow of the communication between the end users and the development team so that they can clarify the risks. Encourage all the stakeholders and users for suggesting risks at any time.
- Integrated Management:
Risk management is made an integral part of the project management during this phase. A consideration of risk should be integrated into the software process.
- Continuous Process:
Risks are tracked continuously throughout the risk management paradigm during this phase. Modify the identified risk than the more information is known and add new risks as better insight is achieved.
Risk Management Paradigm:
Risks are identified before major problem is created. If the risks are identified before they create a major problem then there might not be more difficulty in controlling the risks.
Deep analysis of nature, behavior and type of risk and collect information about it. It is required for the purpose of the determination of the knowledge about the risk.
Convert the plan into actions and implementation. This phase includes the actions and implementation of the planning that was done before. After the risk detection plans are made and executed.
Necessary actions are monitored. Necessary action means the required work for the removal and minimization of the risk detected.
Correct the deviation and make necessary changes. Put the right thing in the right place and the required field will changed according to the changes required.
Discussion about the current risks and the future risks and their management. Make a productive discussion between the developer and tester on the risks found in the software.
- Software Engineering | System configuration management
- Software Engineering | Software Project Management Complexities
- Software Engineering | Project Management Process
- Software Engineering | Seven Principles of software testing
- Integrating Risk Management in SDLC | Set 1
- Integrating Risk Management in SDLC | Set 2
- Integrating Risk Management in SDLC | Set 3
- Software Engineering | Software Project Management (SPM)
- Software Engineering | Risk Management
- Software Engineering | Software Project Management Plan (SPMP)
- Risk Assessment
- Agile Software Process and it's Principles
- Paradigm Software Testing
- Difference between Use Case and Test Case
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.