Managing the Development of Large Software Systems

The paper usually cited as the birth of waterfall, and almost always misread. Royce diagrams the linear sequence — requirements, design, code, test, deploy — and immediately writes that this approach is "risky and invites failure." The rest of the paper argues for iteration, feedback, and doing each step twice. It is one of the most consequential misreadings in the history of software: the industry built careers on a straw man of a paper that was warning against the straw man. Worth reading in the original to understand how ideas travel, and how often they arrive at their destination inverted.