> Agile is the opposite of Waterfall, which has been the old school way of crafting software until the ’90s. I'll probably die on this cross, but no, it wasn't

> Agile is the opposite of Waterfall, which has been the old school way of crafting software until the ’90s. I'll probably die on this cross, but no, it wasn't. VisiCalc was not developed with a waterfall model. Mac OS was not developed with a waterfall model. Infocom did not develop their games using a waterfall model. Neither did Sierra On-Line. The fine folks at Bell Labs did not use a waterfall model to develop Unix. Nor did Larry Wall when he developed Perl. Here's a challenge for you - think of 30 pieces of software developed before 1990. How many of them used a waterfall model? On the one hand, this is deliberately weighting the odds. Most corporate software has no popular awareness. Few outside of the travel industry know about SABRE. Even fewer know about 4ESS, except perhaps knowing it caused the long-distance phone system crash of 1990. On the other hand, the odds go the other way if you consider the many hobbyists writing software in the 1980s both for fun and, for example, to use D-Base II to computerize their records. (A Google Scholar search for "Using D-Base II" finds "Using D-Base II for Departmental Record Keeping and Reporting" (1985), "Tracking patient demographics and disease categories in a primary care residency" (1988), "Create Your Own Billing Program: Using d Base II, You Can Devise a Billing and Internal Accounting System in Just a Few Hours" (1984) and a few more. These people were not using waterfall.)