Risk Management (RMM plan)
|
Risks |
Category |
Impact |
RMMM |
|
Change of Requirements |
Project Risk |
Critical |
The system must be designed using an Object Oriented approach so that it is modifiable with less effort; in the sense that new objects and/or ADTs may be added and/or removed to suit the new requirements of the system. |
|
Staff turnover |
Project risk |
Catastrophic |
Make sure the knowledge/details of the activities done by a staff is spread to others also so that others may continue if one leaves. Work must be well documented to make the transfer of control easy. Every possible effort like counseling must be done to stop staff turnover. |
|
End users resist the system that has been designed |
Business risk |
Critical |
The system has to be designed after taking into considering both the functional and non functional requirements into consideration. The System has to be designed to be as user friendly as possible so that the system that's being designed is easily acceptable to the user. |
|
Funding |
Project Risk |
None |
This system is not being designed with support in the form of funding. So lack of funding does not affect the system. |
|
Deadline of the project may be tightened |
Business Risk |
Critical |
If dead line is tightened make the best possible effort to make the deliverable by making employees work overtime. Adding new employees may not help to speedup the project.. |
|
Larger number of users than planned |
Product risk |
Marginal |
Make sure that the design is enhance able to the meet the growing needs. |
|
Available Technology does not meet expectations |
Technical Risk |
Catastrophic |
Look out for the one supporting the maximum necessary functionalities and try to simulate the other requirements using the available functionality. By selecting a functionally superior language like JAVA we can make sure that most of the required functionalities are met with. |