Comment Re:doesn't work (Score 1) 597
Hey, it's Mr. Strawman. I haven't seen you in days!
First off- waterfall doesn't exist. It never has. It was made up as an example of what people thought development was like, and then immediately used to contrast with how software really was made. Really- check out the history up front.
Secondly, nowhere did I say waterfall was the preferred method. THere are more than 2 options here. Shocking, I know.
Agile is absolutely not about providing information to make decisions early. By the point that you get enough functionality into an Agile project to make any non-trivial decisions on projects of non-trivial scale, you're already many months in and have an architecture that changes will force you to throw away. You're going from possibly needing to throw away work due to changes to assuring it. The costs are no less, and actually tend to be higher than other forms of iterative design.