The Myth of the 'Waterfall' SDLC

a year ago

The article explores the misconceptions and historical context of the Waterfall model in software development.
It challenges the common 'Frozen Waterfall' interpretation, arguing that no original sources advocate for such a rigid process.
The author traces the origins of Waterfall to papers by Herbert D. Bennington (1956) and Winston W. Royce (1970), neither of whom used the term 'Waterfall'.
Royce's model is described as iterative and flexible, contrary to the rigid, linear process often attributed to Waterfall.
The U.S. Department of Defense's DOD Standard 2167 is often blamed for popularizing the 'Frozen Waterfall,' but the standard itself supports iterative development.
The article suggests that the 'Frozen Waterfall' myth may have been propagated by salespeople and Agile proponents to promote their methodologies.
Key characteristics of Royce's Waterfall include heavy documentation, iterative phases, and customer involvement throughout the process.
The author argues that no single development methodology is universally applicable and advocates for tailoring processes to specific project needs.
Alternative terms like 'Planned Development' are proposed to avoid the negative connotations associated with 'Waterfall.'
The article concludes with alternative visual representations of Waterfall to better reflect its iterative and flexible nature.

Hasty Briefsbeta