???
The development stage
includes requirements refining, design, code, and build. Its output is a
product ready for beta testing.
??“
Go to testing
is the moment when the testing budget and the marketing and operational plans
must be committed to. It is based on the continued existence of a market opportunity.
???
Testing
is system and acceptance testing at internal and friendly customer sites. It generates a
product fit for launch.
??“
Go to launch:
is the moment when marketing and training plans become operative.
???
Launch
the product.
It is easy to see a number of critical dangers in this approach:
??? Half the activities are oriented to the development of a business case. Since this is likely to occupy
between 5??“10% of the total manpower, more detail on the other 90??“95% of the manpower??™s
activities would be useful.
??? No allowance has been made for the (inevitable) requirements changes.
??? Testing is relegated to the penultimate activity. The possibility that the requirements are deeply
flawed will thus tend to be hidden. Similarly the testers will not learn how to use the product
until too late causing considerable delay. The tests they prepare may thus need much rewriting.
??? That a decision can be taken on the marketability of a product which has yet to enter beta testing
requires enormous faith in the ability of developers. The amount of iteration between the development
and testing groups is not shown, and the delays (which will also affect the go-to-market
decision) can be considerable.
Pages:
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166