Risk Assessment
Risk
1
2
3
4
Risk Description
Problems integrating our
GUI, DB and the COTS
graphics engine
Customers are unwilling to
change their current
process
Customer avoids use of the
software due to unfriendly
user interface
Data loss caused by power
outage
Likelihood/Consequence
Risk Value
Mitigation Plan
Type of Risk
4/5
20
Employ expert developers
Technology
4/4
16
Market the product as a short term time
and money saver
Customer
3/5
15
Keep the GUI simple and easy to use,
collect beta test feedback on ease of
use
Customer
3/4
12
Employ UPS
Technology
5
Insufficient Funding
2/5
10
6
Customer unable to grasp
the technology
2/4
8
1/3
3
1/1
1
7
8
Database Server Hard
Drive Failure
Development Schedule
Delay
Follow a strict budget with weekly
budget reviews
The software shall come with easy to
use/understand manuals and
documentation. Offer training to the
customer
Employ RAID storage for the central
database
Hire more staff as needed
Problems Integrating our GUI, DB, and the COTS Graphics Engine
The integration of our software with the 3D rendering, database, graphical user
interface, and the COTS might slow down the development of our project. We are going
to license the 3D rendering software to integrate with our software as well as we are
going to create a database that is pretty big in its size. To mitigate this risk, we will have
to hire experts who are already familiar with the 3D rendering and database creation.
Customers are Unwilling to Change their Current Process
Many architectural firms are reluctant to change. The managers and owners feel
that their convoluted system is the best way. To avoid such common reluctance our
marketing strategy focuses on our goals of saving the clients time and money. The
strategy targets our clients showing them that our software will be of overall benefit to
their business. It the market does not embrace our idea, our solution might fail.
Customer Avoids Use of the Software due to Unfriendly User Interface
Our software will be very sophisticated as complex and efficient algorithms must
be created in order to deal with the graphical rendering and database. We have to answer
questions before we start building our product. What can we do to make our product easy
to use for non-computer science people? What we are planning to do is to keep our
graphical user interface simple and easy to use. We will also collect beta test feedback on
ease of use.
Financial
Customer
Technology
Technology
Data Loss Caused by Power Outage
If a power outage occurs, the PC will not be able to operate properly. However, the
database items will be saved and sent to the appropriate places as soon as the power
returns. We will have to employ UPS, with its addition a power outage will not stop our
solution. During the power outage, a UPS will provide the database server with a few
minutes to a few hours of battery power to complete all the transactions and properly
shutdown the system.
Insufficient Funding
Our primary driver for the successful development of the project is our finances.
In order to avoid development delays from poor financial analysis, we will have weekly
budget reviews. The purpose of these reviews is mostly to make sure that we are on
schedule and within our budget constraints. We have done a lot of research upon our
financial needs, so the probability of it is low. The impact is high as if we do not have
enough money to complete the project, it will stop the whole developing process.
Customer Unable to Grasp the Technology
Another technology risk that may occur is the ability for the customer to function
comfortably with technology. To mitigate this risk we are going to offer special training
and online help. Also, with the efforts of our programmers, the software graphical user
interface will be relatively simplistic, and it will lead the user on the correct path to
functioning with our system. We will develop a very in-depth trouble shooting wizard
that will help the user with any potential problems they encounter as well as have a
technical support staff only a phone call away.
Database Server Hard Drive Failure
If there are any sensor problems, the software will scan and properly alert the
user. Also, to mitigate this risk, we will employ RAID storage for the central database.
Development Schedule Delay
The delay in our project developing is possible, but not likely, as well as the
consequences are very small. The only possible way to mitigate this risk is to hire more
help that fits our budget.