(Check if there was a memo
authorizing the release: was the former test manager??™s signature on it? Ask the testers.)
??? The specifications were poor and very late. (Check the release dates and the dates on the specifications.
Read the specifications.)
??? The test manager failed to:
??“ Ensure testers had adequate baselines: ask the testers for copies of the baselines. (Check with
the project manager.)
??“ Support testers in their complaints about inadequate baselines. (Baselines have always got some
bugs. If the test manager hasn??™t complained about something??¦)
??“ Conduct a test readiness review (or if he did, he never left any record of it).
??“ Report on the status of the tests to the management and the testers.
??“ Define test start/stop criteria.
??“ Provide any metrics such that some sense of the success or failure of the testers or the project
could be unequivocally defined.
??“ Plan.
??“ Sack incompetent testers. (Look for big difference between the persons raising the greatest and
smallest number of bugs. Look for near-duplicate bugs which are not marked as such.)
??“ Check whether a bug had already been raised. (Look for a large number of bugs marked as
???duplicate.???)
??“ Clarify that testers and developers were on opposite sides of the fence. (Look for references to
???partnership??? in memoranda.)
??“ Protect testers from any unjustified criticism of them by the project manager. (???Testing only
raised x bugs, I could have raised more on my own.
Pages:
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187