It is inherently risky in that it encourages shipping first and fixing stuff later. This is the opposite of what you do with something like someone's bank accou

It is inherently risky in that it encourages shipping first and fixing stuff later. This is the opposite of what you do with something like someone's bank account. (Yes, ETH Solidity developers, I'm talking to you.) I absolutely love the agile process and I'm a big believer in pair programming, which was part of the original doctrine but is hardly mentioned today. That being said, no one is smart as all of us and there are inevitably things in your code which you (two) as developers won't immediately discern. Waterfall, though protracted and boring, is crucial for identifying and fixing those problems before they ship.