Prev | Current Page 126 | Next

Peter Farrell-Vinay

"Manage Software Testing"

The solicitors won their
case (the contract was according to the laws of England and surprise, surprise, they wrote it). Many
other problems became known over the years. The Italian computer manufacturer later sold mobile
(cell) phones, and has not fielded a computer system since its entire stock of (unsaleable) PCs was
destroyed in a mysterious fire.
T
1
Italian sparkling wine.
30
Manage Software Testing
3.1 How to Manage Risk
Here is a process for managing risk (see Figure 3.1). Risk should be tracked through the project plan,
but in the event that this has not been done, perform your own risk assessment. From such an analysis,
write a prioritized set of risks together with the risk reduction plan and a maximum which can reasonably
be spent to meet each risk. This can be fed into an equation of the type shown in section 7.9.2. From
this you can define some cost limits for the amount of testing you can afford to do, and these can be fed
back into the plan and used to justify the test team??™s work.
???
Plan how to manage the project??™s risks.
The Risk Management Plan documents how risks will
be managed. It is a subset of the project plan and is written before the project begins. See [IEEE
1540-2001] for a standard to follow. See also [Boehm 91].
???
Identify risks.
One simple approach is to get representatives of all the affected groups in a room
and have a workshop. Circulate a provisional list to excite attention.


Pages:
114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138