But it illustrates perfectly what happens when someone who should
know better gets a faulty paradigm into his
3
head. If you can get people to explain how they view
the system, you can probably clear away a lot of misconceptions.
17.
By the time the users have found that bug, we??™ll have released a patch.
Sorry, why does the release
need to be made anyway if you are going to release the patch so soon? Is it to fix a very embarrassing
bug? If so, can you imagine how happy users will be to find the patch contains another bug?
Because with that sort of inattention it will, and they??™ll find it as well. Probably immediately. This
too is the sort of excuse someone might dishonestly put to a (not very bright) board, not to testers.
18.
We don??™t have time to write the requirements specification
. If they say this to you at the interview,
and the project is allegedly ???close??? to making a critical release, then you have options:
??? Take the job (and enjoy being a scapegoat).
??? Fight your corner.
??? Don??™t take the job.
The requirements specification is of critical importance to the following stakeholders:
??? Testers who need a specification to test against.
??? Developers who need a specification to know what to develop.
??? Technical writers who need a specification to know what they have to write about.
??? Marketing which needs a specification to sell the product.
??? Project and test management need a requirements specification to get some idea of system sizing.
Pages:
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89