Estimate what it will cost if the software is late or fails. Then counter the question with ???
It costs
too much for what? The risk
the system represents to the company? The budget you agreed to last
week without me, or any relation to the cost to the company if the system fails?
???
Put the question another way: ???
Why not just build the software and release it? To hell with the
customers. They won??™t know. Think of the money and time you can save by sacking all the testers
.???
(Be prepared to make this argument because if ever anyone thinks you??™re too scared to argue for
your job ??” you??™re out. Persist.)
???
You don??™t want to test; fine, don??™t test
.??? (Then they??™ll accuse you of ???being silly.???)
???Fine, so we agree you do want to test.???
(Pause here. Let someone deny the obvious.)
???But you don??™t want to test a lot. At least not with as much rigor as I do. So how much do you
want? How much is enough????
This should trigger a counter-attack along the lines of
???testing is very costly in itself,??? ???testing is
costing us time to market,??? or ???there are still too many bugs being found in the field.???
To each of these, show your figures. When they fail to come up with their own figures, make
this bitingly clear.
???You??™re worried about the bottom line. Funny. So am I. But I??™m prepared to back
my arguments with figures and proof. You just hand-wave.???
(Yes, the gloves are off).
Pages:
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83