The thing that disrupted waterfall was not Agile per se. It was the fact that no one could figure out why waterfall was appropriate in some contexts but not in

The thing that disrupted waterfall was not Agile per se. It was the fact that no one could figure out why waterfall was appropriate in some contexts but not in others. This led to pervasive conflict between stakeholders who wanted correct answers and those who wanted immediate answers. The remedy, obviously, was: shiny process! -- including, but not limited to, Agile. Today, new shiny processes; but the question is still whether the answers should be right or fast. Pick one.