How to manage customers requirements?

The Problems are

• Lack of information
• Ambiguity
• Wrong information

Projects that have alot of uncertainty as to what does the final product look like should Prototype. Prototyping allows project team members to explicitly define the product. "No assumptions No risk". If team members assume that they know what the customer wants, this is a risky strategy.

The first step is to Collect/Define requirements. second step is to perform a functional analysis. "Fit and Gap Analysis" compare between current status requirements. Analyze the Life Cycle Costs and perform the Cost and Resource Analysis. Third Step is to visualize the product of the project. Projects with uncertainty require prototyping to define the product and avoid ambiguity and requirements conflicts.