Fast and Steady Wins The Race
When I started software engineering, Waterfall was the typical process. A team would spend months building a large feature set, then deploy it. There were lots of reasons for it. Hardware acquisition looked nothing like it does today. Deployments took hours, not minutes. There were far fewer frameworks and almost no standardized automation. It was costly to do individual releases and thus batching was preferred. The batching had a time cost, though. User feedback was slower, patches took longer, and project management was more complex. ...