The key factors in this project are the limited budget ($82,000) and the aggressive timeline (one month). Both of these factors introduce risk into the project over and above the risks that might otherwise be associated with implementing a local area network.
Key risks associated with this project include:
Failure of hardware to arrive on time
Server failure during implementation
Workstation(s) failure during implementation
Software failure during implementation
Because of the tight timeline, failure of the hardware to arrive on time would cause a delay in the entire project. The most likely reason that this would occur is because of a delay at the factory, although it is remotely possible that such a delay could occur while the hardware is en route. This risk can be detected by monitoring the ship date and ensuring that the hardware manufacturer is aware of the criticality of the shipment being on time. Since JavaCom is a consulting firm·albeit a small one·it is likely to place additional orders with the manufacturer if it is satisfied with the delivery schedule; this can be leveraged to ensure that the delivery is on time. The remedy to this risk is to order hardware from a different vendor, which might carry some difference in price, particularly if the new order must be expedited.
The risk of a server failure is considered low because hardware is remarkably reliable. However, if such a failure occurs, it would severely hamper the prospects for the project to complete on-time. There is no way to tell until the hardware arrives and is installed whether the server will function properly, but detection is straightforward. The remedy to this risk is to order a replacement server, expedited, with the manufacturer bearing the shipping costs.
Workstation failure is more likely than server failure for the reason that there are considerably more workstations compared to a single server. The severity level o...