6.1 Risk Mitigation, Monitoring and Management Plan

6.1.1 Risk: Unavailability of Skilled Staff

6.1.2 Risk: Late Delivery

6.1.3 Risk: Lack of Experience

6.1.4 Risk: Change in Requirements

6.1.5 Risk: Incorrect Size Estimation

6.0 Appendix

6.1 Risk Mitigation, Monitoring and Management Plan

Risk Mitigation, Monitoring and Management Plan are generally referred to as RMMM Plan. This plan deals with the three strategic issues, which are risk avoidance, risk monitoring and risk management. Its scope covers those potential risks that have major impact on the product, project and also the organization / business which have been identified previously. The goal of RMMM is to provide appropriate strategies to avoid and monitor the risks as the project progresses. This plan will also describe the actions to be taken in the event that mitigation steps have failed and the major risk has become a live problem.

Return to top

6.1.1 Risk: Unavailability of Skilled Staff

• Mitigation

In order to prevent this from happening, appropriate training or courses should be provided to the team members regarding their area of work before the project start and as the project progresses. In addition, the development team has to ensure proper quality control and maintenance of the software throughout the project development.

• Monitoring

The work progress of each team member should be monitor regularly in order to ensure her ability in performing the assigned task. Besides that, constant peer review among team members can be held during the project development

• Management

If a particular team member is having difficulties in performing her task or the quality of the work performed do not meet certain level of predefined standard, task re-assignment have to be done. If the problem still unsolved, recruitment of new staff with the required skills is another alternative that can be take into consideration.

6.1.2 Risk: Late Delivery

• Mitigation

The development team must have a regular review of the project plan, this can probably be done in the team's regular meeting. In addition, they must discuss the project plan during the early stages in order to ensure that all the deadlines are set realistically.

• Monitoring

The activities of the project will be monitoring in order to ensure that all the deadlines set in the project plan are met. A schedule can be established to monitor project status. This schedule will be followed closely during all the development phase of the project.

• Management

Below are some of the possible actions when the development team encounters a late delivery on the project:
- Modify the project schedule to account for any unforeseen delays.
- Identify the root cause of the delay and ensure that any problems are adequately dealt with.
- Increase the amount of available resources
- The re-allocation of available resources by streamlining other non-essential processes

6.1.3 Risk: Lack of Experience

• Mitigation

In order to prevent this from happening, all the involved team members will be required to learn techniques and skills necessary to develop this project. Each member will be assigned to the most appropriate area that matches with his/ her past experiences.
.
• Monitoring

The progress of each team members should be monitor regularly in order to check whether the team members is perform well on the assigned task. Attention should be pay on the team member who is weak in a particular area.

• Management

The more experience team members will provide help to other team members with their duties or the task can be re-assign to the most appropriate team member after review had been done on team member’s performance.

6.1.4 Risk: Change in Requirements

• Mitigation

In mitigating this risk, the development team must meet with the customer before the project begins, in order to obtain a detailed listing of all project requirements and to maintain a minimal number of required changes (if necessary) later in the project's life cycle. In addition, the development team must maintain an open line of communication with the customer in order to facilitate any changes that are required.

• Monitoring

In monitoring the activities of the project, the following issues will be monitored:
- Whether the customer have read the Software Requirements Specification document carefully.
- Whether any special instructions are given from the Customer after the Software Requirements Specification is signed by both the development team and the Customer.
- Ensure that the Customer is keep up to date with the team's progress

• Management

If there are changes in the project's requirements, the development team will arrange a meeting with the customer, to determine the nature of the changes. If it is reasonable, the Software Requirements Specification document will be modify to reflect all the changes.

6.1.5 Risk: Incorrect Size Estimation

• Mitigation

Prototyping approach can be used for this project and it should be start early in the project's life cycle so that any error in project size estimation can be discovered earlier.

• Monitoring

The development team should check the difference between the size of the prototype and the estimated size of the project during the project development.

• Management

If the estimated project size is lower then the exact figure, discuss with the client of the probability of cutting down requirements if the difference of the estimated size and the prototype is huge. Besides that, re-estimation on the project size based on the prototype done can be carry out.