What's Fundamentally Wrong? Improving our Approach Towards Capturing Value in Requirements Specification
by Tom Gilb and Lindsey Brodie
We know many of our IT projects fail and disappoint. The poor state of requirements methods and practice is frequently stated as a factor for IT project failure. In this paper, I discuss what I believe is the fundamental cause: we think like programmers, not engineers and managers. We do not concentrate on value delivery, but instead on functions, on use-cases and on code delivery. Further, management is not taking its responsibility to make things better. In this paper, ten practical key principles are proposed, which aim to improve the quality of requirements specification.
| Attachment | Size |
|---|---|
| Whats Fundamentally Wrong.pdf | 406.31 KB |
Article Sponsored By
So right, but obscure to a first time reader.
This short paper uses many unfamiliar notations for many readers, but reading the bibliographical reference material will constitute a substantial education and provide the opportunity to greatly enhance the value delivered by almost any project. This constitutes a very substantial challenge for anyone used to the typical practices in the industry.