T. Johansen and T. Gilb, “From Waterfall to Evolutionary Development (Evo): How we Created Faster, More User-Friendly, More Productive Software Products for a Multi-National Market,” Proceedings of INCOSE, Rochester, 2005. http://www.gilb.com/tiki-download_file.php? fileId=32

has been cited by the following article:

• TITLE: What’s Wrong with Requirements Specification? An Analysis of the Fundamental Failings of Conventional Thinking about Software Requirements, and Some Suggestions for Getting it Right

  AUTHORS: Tom Gilb

  KEYWORDS: Requirements, Value Delivery, Requirements Definition, Requirements Methods

  JOURNAL NAME: Journal of Software Engineering and Applications, Vol.3 No.9, September 30, 2010

  ABSTRACT: 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.