We talk about characteristics of good requirements, including completeness, correctness, and ambiguity. But how do we assure that our requirements are complete, correct, and unambiguous? Simple, Captain, with logic.
Tag Archives: writing good requirements

Posted in Communication, Requirements, Writing
Tagged ambiguous requirements, complete requirements, correct requirements, documenting requirements, incomplete requirements, incorrect requirements, logical requirements, managing data, requirements writing, unambiguous requirements, writing good requirements, writing requirements
1 Comment

Posted in Requirements, Requirements gathering, Software development, Testing
Tagged managing data, quality and requirements, quality requirements, requirements and quality, requirements elicitation, requirements errors, requirements quality, writing good requirements, writing quality requirements
Leave a comment

Companies Will Waste $1B This Year on Software Tools
Gartner reported that companies spent $3.7 Billion USD on application development tools in 2004, with a 5% annual growth rate. The Standish Group has shown that 40% to 60% of project failures are due to requirements failures. At least 1/3 of the money spent on getting more efficient at coding is being wasted – it should be spent on writing the right software.

