Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage

In 1994, the US Department of Defense issued a temporary military standard, MIL-STD-498, which explicitly supported the use of evolutionary project management (Evo). It also supported the related concept that projects do not initially have the final and correct user requirements specified. This standard has now been evolved into civil standards (such as IEEE standards) and is continuing to influence new standards. Such recognition for Evo is deserved as it has probably the best track record of any known project management method (Larman and Basili 2003).
Surprisingly, many project cultures have little formal knowledge of Evo, even though it has been in use since the 1960s. The first documented large-scale industrial use of Evo was from 1970 to 1980 and on, within IBM Federal Systems Division (IBM FSD, later owned by Loral and Lockheed Martin). Working within the military and space sector, they had complex high-tech projects requiring state-of-the-art performance with fixed financial budgets and fixed deadlines. These extreme requirements drove them into developing methods known as Cleanroom , which included using Evo. Harlan Mills reported on these early IBM FSD experiences as follows:
Ten years ago general management expected the worst from software projects cost overruns, late deliveries, unreliable and incomplete software. Today, management has learned to expect on-time, within budget deliveries of high-quality software. LAMPS a 4 year 200 person-years (project was delivered) in 45 incremental deliveries. Every one...