....................................449
xix
Preface
This book is written for:
??? Testers who want to become test managers and need to get a new perspective on all the things
they already know.
??? Test managers who want answers to some very pressing questions all in one place.
??? Project managers who want to know what they should expect from their test team, what they can
do with it, and what it will mean.
??? Quality assurance staff who want to know what to look for in a testing environment and how to
measure it when they find it.
??? Lecturers who realize that test management is another critical role which can mean the difference
between success and failure on a project, and which might form the basis of a new course.
??? Investment analysts who want to know what might go wrong with their investments, why, and
how to stop it.
??? Project office staff who want to know how to integrate the information they get from the test team.
??? Auditors fed up with being pilloried by the Public Company Accounting Oversight Board and
worried that something about Sarbanes??“Oxley might have escaped them.
It is intended to pull together a lot of issues to give a strategic, risk-based management view of testing
and how it relates to every stakeholder involved. In particular it is focused on lifting readers above the
testing battlefield, concerned with the
what
and
how
of bug finding but also looking at the
why
.
The book??™s structure is as follows:
??? The Introduction and Chapter 2 set out the
issues
.
Pages:
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75