Javacom

Javacom LAN Project

There are some key factors for this project. The budget is limited ($82,000) and the timeline is a little aggressive (1 month). Because of these factors, there might occur some risk situations.

Key risks for this project are:

1-) Failure of hardware to arrive on time

2-) Setting the user priorities and authorizations

3-) System freezing

4-) Hardware malfunctioning

5-) Training

The hardware could delay its delivery for up to two business days delaying the entire project. This particular risk concerning the project is considered low, but it is possible. Setting the user priorities and authorizations could be a very intense process due to the involvement of a higher number of people. Corporate red tape always tends to stand in the way of efficiency and therefore the project team has determined a risk for delay of 1 day, considering this risk to be high. The in-house whole network testing could be affected by the system freezing, which could cause a medium risk for delay of at least a half-day. The client site test always has the low risk of the hardware malfunctioning, adding an additional half-day to the task. Finally, training is a very critical task in the project. The possibility for risk in this task is very high due to different learning curves within the organization in addition to questions that might arise. The team has determined the high risk to be at least a delay of three days.

In assessing the project risks the team must address the contingency plan to be implemented for each risk. The delivery of hardware could be delayed for up to 2 days. In order to prevent or avoid this risk the team will assign a team member to track the delivery of hardware from beginning to end. This will allow the team to know in advance the first sign of any flaws in the delivery logistics of the hardware. If an event of this nature would occur, the team would immediately arrange for the hardware to be delivered by another company. This action