- Shopping Bag ( 0 items )
Defining a process of requirements capture as the "front end" or"pre-development" of the product development process is imperative.The front end is a critical phase because once the concept has beendefined, then about 80% of subsequent costs will have beencommitted.
Without the requirements capture process, false assumptionsregarding customer, technical and other requirements may be made.Such false assumptions lead to errors in the product specificationwhich may only be uncovered later in the process. It does not takemuch to imagine the impact this has on time and money.
With the current focus on achieving quick response, managers worrythat more effort expended on requirements capture at the front endwill increase the time of product development. However, companieswith intensive front end activities spend 40% less time on productdevelopment than those that ignore this stage. In addition,companies with an effective requirements capture process gain moreprofits and revenue from new products than those that do not havean adequate requirements capture process.
The writing is on the wall.
New Product Development.
Requirements: Ideas, Research and Strategy.
Requirements: Market Research Tools and Techniques.
CAPTURING AND MANAGING REQUIREMENTS CAPTURE IN PRACTICE.
Introduction to the Case Studies.
Colossus Case Study.
Vantage Case Study.
Bandage Case Study.
Construct Case Study.
GUIDELINES TO REQUIREMENTS CAPTURE.
Requirements Capture Process.
Integrating Requirements Capture with Product Development.