,

Resources

Paper - When Good Requirements Go Bad

When Requirements Go Bad: Understanding the causes for Requirements errors can help prevent them. By Kurt Bittner

The notion that errors in requirements are a contributing cause to the failure of many projects is nothing new. It is easy to attribute the problem to lack of clarity in the requirements - that if only the ambiguities could be eliminated all would be well. Ambiguous, unclear or incomplete requirements are serious problems, to be sure, but they are not the sole source of requirements errors. Requirements errors have many sources, however, and ambiguous or unclear requirements are only part of the problem. In order to reduce requirements errors, it's worth exploring a number of common types of errors to find their source and strategies for dealing with them.

Filesize - 105 KB

To download your free copy sign in