With the stunning success of the pricing tool, we
declared agile methods to be the preferred development
method. It became the default mode for the subsequent
projects. Matching our own (initial) experiences with some
of the published literature on Agile Methods [2], we felt
reassured that “Agile = Good” and “Waterfall = Bad”.
We were unprepared for what happened next. Excited by
the prospect of working with a new process, we consulted
the literature that extolled the virtues of Agile Methods,
mostly as they apply to new projects [3], [4], [5]. We missed
the more balanced articles, like "Get Ready for Agile
Methods, with Care,” by Barry Boehm [6], which discussed
the more realistic side of Agile Development.