??? It must be very tool-supported to work or it will either decay or become enmeshed in the
bureaucracy it was intended to minimize.
The implications of this for the system testing team are that:
??? The status of emerging requirements must be constantly reviewed.
??? The team is committed to validating both the requirements and the design.
??? Any use of prototype code in the production version will require much more rigorous unit testing
than is normal.
4.4.5 Prince II
Prince II is a stage-oriented project management approach which is promoted by the British government.
The words
test manager, test team, requirements, functional,
or
specification
do not appear in the glossary
or indeed anywhere else in the manual [Prince II]. Its approach to testing is naive and based entirely on
the requirements of ISO 9000. It is easy to see why the British government has suffered from so many
project failures. The British government, aware of the problem, has reviewed a number of IT projects
and issued a report [McCartney] which makes a number of useful recommendations concerning requirements
management and testing while stopping short of mentioning a test manager or team. None of
these has resulted in any change to Prince II. As a test manager you will need to ensure:
??? That you have a role at all to play despite Prince II and McCartney
??? That the requirements specification exists, is properly managed (if not under your control), and
all changes to it are controlled
??? That the project manager understands the need to institute reviews early
??? That the project manager understands the implications of [McCartney] and the need to change
the use the project makes of Prince II as a result
Prince II is intended to be used with SSADM.
Pages:
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169