Prev | Current Page 347 | Next

Peter Farrell-Vinay

"Manage Software Testing"

Also, they had learned to look at the bug detection chart, and not release
until it was nearly flat. So eventually a preliminary demonstration release was made and many
ag?©d fingers were crossed, as just a few customer staff used it in earnest. And three weeks later
some interesting bugs were exposed and analyzed, and the testers revised their tests.
Finally the first release was made, and it went up. And it stayed up. And the four key programmers
who were warned to be on hand to create emergency fixes found that they had nothing to do and
could get on with version 2. And version 2 was built and tested in record time, and was as solid
as version 1, so even the accountants started to smile.
T
172
Manage Software Testing
9.1.1 The Test Manager
The test manager needs a number of qualities. He:
???
Is able to judge people
to distinguish the:
??“ Determined from the hangers-on
??“ Beginners from the finishers
??“ Intellectually-curious from the merely technology-obsessed
??? Is able to
distinguish between the true and the useful
.
??? Is
methodical
: this is so obvious a prerequisite that it??™s often overlooked.
???
Listens well
to what is being said. Why? What is
not
being said? Who is telling you? What is their
advantage in ensuring you know? He notices what
isn??™t
being said (and ought to be).
??? Is largely
unconcerned for popularity
: he won??™t be popular at many moments in his career, and
he needs to be able to withstand that pressure.


Pages:
335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359