Premium
7.4.2 What's fundamentally wrong? Improving our approach towards capturing value in requirements specification
Author(s) -
GILB TOM,
BRODIE LINDSEY
Publication year - 2012
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2012.tb01380.x
Subject(s) - computer science , value (mathematics) , quality (philosophy) , risk analysis (engineering) , focus (optics) , requirements management , software engineering , process management , requirements analysis , engineering , business , software , programming language , physics , optics , philosophy , epistemology , machine learning
We are all aware that many of our IT projects fail and disappoint: the poor state of requirements practice is frequently stated as a contributing factor. This article proposes a fundamental cause is that we think like programmers, not engineers and managers. We fail to concentrate on value delivery, and instead focus on functions, on use‐cases and on code delivery. Our requirements specification practices fail to adequately address capturing value‐related information. Compounding this problem, senior management is not taking its responsibility to make things better: managers are not effectively communicating about value and demanding value delivery. This article outlines some practical suggestions aimed at tackling these problems and improving the quality of requirements specification.