Iterative development history

Is iterative development a new process?

I have a dispute with my colleague. He thinks that iterative development has been available for decades. I am convinced he is wrong, as it is a reaction to the failing of the traditional waterfall model. It is not called "traditional" for nothing!

    Requires Free Membership to View

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I am sorry to tell you, but your colleague is right. The iterative process was developed in parallel with the waterfall model. This is perfectly pointed out by Craig Larman in a speech he gave two years ago. At the time the waterfall method came into official existence, there were also attempts at the DoD to promote iterative and incremental development. Even Dr. Royce ("inventor" of the waterfall method) knew at the time that there was more than one way to do development. When he first wrote about his process, he expressed that it was his personal view and that it was suited for some (but not all) situations. I guess Royce's process had a better "feel" for traditional management; it does provide a feeling of control and prediction.

Software development resources:

This was first published in February 2007