We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2
RMMM Plan :
A risk management technique is usually seen in the software Project
plan. This can be divided into Risk Mitigation, Monitoring, and Management Plan (RMMM). In this plan, all works are done as part of risk analysis. As part of the overall project plan project manager generally uses this RMMM plan. Risk Mitigation : It is an activity used to avoid problems (Risk Avoidance). Steps for mitigating the risks as follows.
Finding out the risk.
Removing causes that are the reason for risk creation. Controlling the corresponding documents from time to time. Conducting timely reviews to speed up the work. Risk Monitoring : It is an activity used for project tracking. It has the following primary objectives as follows.
To check if predicted risks occur or not.
To ensure proper application of risk aversion steps defined for risk. To collect data for future risk analysis. To allocate what problems are caused by which risks throughout the project. Risk Management and planning : It assumes that the mitigation activity failed and the risk is a reality. This task is done by Project manager when risk becomes reality and causes severe problems. If the project manager effectively uses project mitigation to remove risks successfully then it is easier to manage the risks. This shows that the response that will be taken for each risk by a manager. The main objective of the risk management plan is the risk register. This risk register describes and focuses on the predicted threats to a software project. Drawbacks of RMMM:
It incurs additional project costs.
It takes additional time. For larger projects, implementing an RMMM may itself turn out to be another tedious project. RMMM does not guarantee a risk-free project, infact, risks may also come up after the project is delivered.