Requirements Management |
Definition of Requirements Management |
"Requirements” are desired characteristics of a product (or service) being developed during a project. They are usually in the form of a formal statement of a function to be performed, or an attribute to be possessed by the product (or service).
"Requirements Management" refers to the collection of activities undertaken by an individual or a team in order to gather, store, track, prioritize and implement requirements. |
| |
Challenges in Requirements Management |
CIO Magazine |
Analysts report that as many as 71% of software projects that fail do so because of poor requirements management, making it the single biggest reason for project failure - bigger than bad technology, missed deadlines or change management fiascoes.
Christopher Lindquist, Fixing the Requirements Mess, CIO Magazine, November 15, 2005 |
Standish Report |
The Standish 2004 CHAOS Report, which surveyed 9,236 IT projects, found that the top three causes of project failure were lack of user input, incomplete requirements or changing requirements. |
Survey of European Software Organizations |
A recent survey of European software organizations identified that more than 40% perceived that they had major problems in managing customer requirements, and more than 50% perceived that they had major problems in the area of requirements specification.
El-Emam, K., Birk, A., Validating the ISO/IEC 15504 Measure of Software Requirements Analysis Process Capability |
| |
Why Use Requirements Management Tools? |
 |
 |
 |
| |
 |
|
"Requirements management can be simplified if initial requirements definitions are captured in a database-based tool to enable collaborative review, use-case and test-case creation, traceability and versioning/change control" |
Matt Light, Research Director, Gartner |
 |
|
 |
|
| |
|
 |
|
 |
|
| Quick Product Tour |
|
30-day FREE Trial |
|
