If
this release is a feature too big, then remove that feature. Else keep testing.
13.
Nobody cares about these bugs.
Everyone cares about the bug that??™s stopping them from doing
something. This sort of reaction means either you haven??™t got them to agree on a way of classifying
bugs or they??™re arguing about the lesser bugs. What do these bugs mean? That some feature is
missing, or absent, and users don??™t care? If the latter, then remember that a system infected with
a thousand tiny bugs is possibly as unusable as one with a couple of big ones, and user dissatisfaction
may soon come to the boil. See section 17.2 for a little story.
14.
Testing isn??™t the answer.
This was said of a finance system which should have been tested and never
was, didn??™t work, and whose remaining users fled. The person who said that was later found
running another failing project. He had never quite worked out what the question was either.
15.
The developers do all the testing
and other sources of belly laughs. Developers develop. Ask them
to seriously system-test what they build and you??™ll be looking at a fascinating expanse of empty
chairs. This is probably what this person told the board or anyone else too dim to consider the
implications. The person who said that lost his job as CEO seven months later.
16.
Please don??™t damage the system
. OK, this was said 20 years ago and the person concerned will never
make the same mistake again.
Pages:
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88