For more
on risks see section 8.16, 8.17, and B5 in Appendix B.
TABLE 3.3
Simple risk
Risk name Prob.
Cost
(US$) Comments
Risk
(US$) Alerts Mitigation
It doesn??™t
work.
0.5 1,125,000
(cost of lost
sales)
It gets released
without major
features or with
major features not
functioning. The last
three releases did.
562,500 High levels of code
complexity,
turmoil, unit test
failures.
Create demonstrator
versions for all major
features and have
them performancetested
early.
It contains
serious bugs.
0.7 350,000
(the cost of
the next
bug-fixing
release)
The last three
releases did.
245,000 When actual bug
level exceeds
expected.
Ensure all critical
units are unit-tested.
Have all unit tests
reviewed, and some
code quality tools.
The release
will not be
made on time.
0.99 75,000
(average
cost of the
last three
overruns)
None of the last
eight releases did.
74,250 When any
workpackage is
late in delivery by
more than one
day.
Review the schedule
in the presence of
test and developer
staff. Identify weak
areas. Allow for
contingency of 25%.
The project
will suck in
resources from
the rest of the
company.
0.7 65,000
(cost of
resources)
+ 75,000
(cost of
delays to
other
projects)
Every one of the
last four releases
did.
98,000 Any request for
more staff by any
manager.
None. No other
project is more
important. Get staff
lists from the other
project and cherrypick
their best
people.
Pages:
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151