Added by Geoff Sauer on Jul 11, 2004.
Average rating: 2.60/5.00 (n=5, std dev: 1.82)
 


Developing a new product or service is tricky. When everything goes well, the product can redefine a market or even create an entirely new one, to the benefit of its manufacturer and its consumers. When the product doesn't click with its audience, though, the costs—development, employee, manufacturing—can be staggering. How do you ensure that your new product doesn't flop? One effective method is to conduct a requirements definition phase before developing a new product.
 
  View all five works by Olshavsky, Ryan  
  View all 44 works published by Cooper Interaction Design  


Reviews
Ginger Shew-Stuckey Requirements Definition
I have participated in requirements gathering but I have never lead a project needing requirements. This article provided me with good, high-level information for a jumping off point.

Please share your rating/opinion of "Bridging the Gap with Requirements Definition".
 PoorExcellent 
click this box if you find the link above broken or out-of-date.

Copyright © 2001-17 by the EServer. All rights reserved.Add a Work | Discussion Forum | Habitués