Where the requirements are difficult to comprehend / elicit from customers, the rapid prototyping iterations prior to a full system build/release can be applied within the first build/release cycle of product development. How many times have you heard complaints from the engineering / development team that the users don‘t know what they want? This approach will help the users firm of their requirements after they see the product prototype by providing feedback in terms of what they really need.
Rapid prototyping by product managers / business analysts is also a great idea to resolve conflicts with engineering managers from old school, who require that requirements be frozen prior to analysis / design. This freeze mentality comes from the numb-nuts engineering managers who are grounded in waterfall methodology, and do not understand agile methods / spiral modeling.
Add this to del.icio.us »
Digg this »