Five common errors in requirements analysis (and how to avoid them)

In the traditional waterfall model of software development, the first phase of requirements analysis is also the most important one. This is the phase which involves gathering information about the customer's needs and defining, in the clearest possible terms, the problem that the product is expected to solve. Well, at least that's the way it's supposed to work theoretically. In reality, there are a number of problems with this theoretical model, and these can cause delays and knock-on errors in the rest of the process. This download discusses some of the more common problems that project managers experience during this phase, and suggests possible solutions.

This download is also available as a TechRepublic article.