It's been awhile since I last posted as I have been debating what really should be reason number four project failure....well not really, I just have been failing to met my own expectations with everything I have going on.
In any case reason number four for project failure is adequately identifying, documenting and tracking requirements. Using documentation requirements does not eliminate the need for formal, well organized process for gathering requirements. Sometimes people believe that a one page email with a wish list features is good enough. Not so much! The good news is that most project owners/sponsors believe that requirements need to be documented. Nailing requirement documents must be done very early in a project, wait till later and it's to late. Ambiguity is good for no one thus you must clarify that ambiguity as quickly as possible.
There are various tools and techniques for defining requirements like codifying, progressive elaboration, interviewing, modeling and interviewing. You can use one or all these tools to help you to define your requirements.
