The project environment.
2. What the project is supposed to be doing.
3. What??™s happening, and the evidence.
4. What we need to do.
5. How we??™ll know if we??™re succeeding.
6. What will happen if we don??™t do what??™s needed.
Keep it short (no more than 4 pages, and preferably two), keep it conclusive. Say nothing you cannot
support with evidence.
1.6 Conventions
??? [Names] refer to a reference in the list at the back of the book.
??? |a| is the absolute value of a, e.g., (|-5|=5).
??? min(a, b) is the minimum of a or b, e.g., (min(10, 11) = 10).
??? is an estimate of N.
??? { sets | of | things } are held in curly brackets and separated with vertical strokes.
?†N
8
Manage Software Testing
1.7 Apologies
If this book seems so far to be a little diatribe against management, then please accept that:
1. I know and have worked for many intelligent managers who have been very tough over dates and
resources, but didn??™t want their name sullied by bug-filled releases. They are very good people to
work for.
2. There are the unhappy few for whom avoidance of responsibility has become a way of life.
More cautions:
1.
We have seen the enemy and it??™s us
. When we??™ve seen past the technology, we realize that most
of the problems we face are the ones we create for ourselves.
2.
Definitions of quality are a bit like quality of life
. If the subject is raised, then you know there
isn??™t much. If a product does what it says on the tin and someone will pay for it, that??™s quality.
Pages:
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96