There are some risks whose exposure can be considered
constant.
3.2 A Worked Example
Assume a project to build a release 7.0 of the QuanGO product. The product has four major features:
1. An Alerts Management System (AMS) (to tell staff when some stock is low)
2. An ODBC interface (to interface to the databases)
3. A Stock Management System (to manage the warehouse)
4. A web interface (so salesmen and major customers can see stock levels and order)
It is proposed to rewrite the Alerts Management System and add a voice input ordering system.
1.
What are the risks?
??? It doesn??™t work.
??? It contains serious bugs.
??? The release will not be made on time.
??? The project will suck in resources from the rest of the company which had been allocated to
other projects.
2.
What are the probabilities and costs?
From Table 3.3, it is a simple matter to calculate the total risk
the project faces (probability * cost). Note that
exposure
in this case is considered to be 100%.
3.
What are the sources?
Following is a list of possible sources. You will need this if you are to attack
the problem. Each of these can contribute to a single risk such as
it doesn??™t work
.
??? Developer expertise: the old AMS was, frankly, clunky. It was written in VB4, made no use of
.NET, and was a major source of bugs. It is proposed to rewrite it in C#. All the developers
are experienced in Java. None has any major C# experience.
Pages:
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148