Your estimates were hopelessly wrong. Check them, then have a colleague check them.
92
Manage Software Testing
b. Your beta tests didn??™t show the bugs they were supposed to. Read the bugs they did find; are
these bugs found by people playing with the system or using it in earnest?
c. You have a history of being overwhelmed by bugs. Check with Human Resources to find out
how many Support staff left after the last big release. Look at the test logs. Read the mails on
the user sites. If no big increase in 3rd-line Support calls
(real bugs which have to be checked
by the test group)
occurred after the last big release but a lot of Support staff left, they were
probably badly-prepared. If there were a lot of bugs and a lot of Support resignations/dismissals,
then maybe Support took the blame for poor testing.
8.
Do we have a sufficient contractual relationship with our suppliers of subsystems to be sure they will
respond in a manner which will not leave us exposed?
a. Check the contract: are there time limits and penalties? What happens if a customer finds a
severity-1 bug in their software tonight? In how much time must they get a patch to you? How
big is the risk to your company if they don??™t?
b. Check the history of your company??™s relations with that supplier. Have they ever provided a
severity-1 fix on time? Do they regularly provide fixes on time? What happened when they
failed the last time?
9.
Which of our tests was insufficient?
a.
Pages:
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248