Identified
Risk
|
Contingency
Plans
|
The data gets lost or damaged due to viruses |
·
Try to retrieve the file if it is still possible. ·
Clean the infected file using an anti-virus program. · Install a new copy of the database and re-encode data in the back up copy of the database. Data encoding will be part of the user training to be provided by the project team. |
The developers are not able to finish the database |
· Tasks will have to be re-assigned to cover for the 'unavailable' programmer or the lag in the work. |
The
encoder hired is does not perform well The person cannot meet the target amount of data needed to be inputted in the database each day |
·
The encoder would have to work overtime. ·
Some members of the project team will need to encode data
in order for the encoder to rest. · Extend the duration of the encoding task. |
The encoder quits working for the college guidance office |
·
Employ scholars to sign up for shifts during the encoding.
·
Members will share encoding tasks. · Consult the project sponsor as to hiring another encoder. |
The client is not satisfied with the modifications on the database |
· Always update with the requirements of the client. |
The client insists on adding an "important" feature in the database and presents the possibility of rejecting the project |
· Refuse the additional requests. Place them under recommendation. |
User resistance; The councilors refuse to utilize the improved database |
· Ask the sponsor to help in the implementation. |
The computers do not meet the required specifications for the new database |
·
Ask the sponsor to draft a request for additional computers.
· Suggest that they start encoding using another computer at school. |
The computer in the office breaks down |
·
Request for new hardware as soon as possible. · Install the database in another computer. |
The operating system of the computer crashes |
·
Re-install Windows in the computer. · Use the back up copy containing the database. |
The project sponsor fails to supply the table of scores for each test module |
· Start working on the other modules that already have tables. |
The
project sponsor/client, cannot provide feedback about the development
in the database |
· Email the sponsor. |
Copyright (c) 2002 by PJ Oliveria