Risk Identification is a systematic attempt to specify threats to the project plan estimates, schedule, resource loading, etc. After identification and predictable risks, we have taken following steps towards avoiding and controlling them.
It associated with the overall size of the software to be built or modified. Estimate size of product in number of programs, files, and transaction. Number of users of the product. Size of Database created.
Risks associated with constraints imposed by banking laws and management system.
Customer (Teacher) Characteristics
Risks associated with the sophistication of the customer (teacher) and developers ability to communicate. Have you work in the past with your teacher. Is the teacher willing to establish rapid communication links with the developer. Is the customer having the background technical knowledge.
Risks associated with the degree to which the software process has been defined and is followed by the development organization. Specific methods used for software analysis. Software tools used to support planning and tracking activities.
Risks associated with the availability and quality of the Oracle tools to be used to build the product.
Technology To Be Built
Risks associated with the complexity of the system to be built and the newest of the technology that is package by the system.
Members Size and Experience
Risks associated with the overall technical and project experience of the project members who will do the work.
Risk projection also called the risk estimation, attempts to rate each risk in two ways.
Risk Projection Activities
Establish a scale that reflects the perceived likelihood of a risk
The RMMM plan
(Risk Mitigation, Monitoring and Management Plan)
The RAMMM plan documents all work performed as part of risk analysis and is used by us as part of the overall Project Plan.
Outline for the RAMMM plan follows:
II . Project Risk Table
III. Risk Mitigation, Monitoring, Management
IV. RMMM Plan Iteration Schedule