Agile is good for some problems (IE, where the requirements are poorly understood) and not others. That's the true answer. There's no one-size-fits-all soluti

Agile is good for some problems (IE, where the requirements are poorly understood) and not others. That's the true answer. There's no one-size-fits-all solution, but people think (and argue) in absolute terms, not situational nuance. People routinely mistake knowing the end-goal requirement ("Make a healthcare website") with knowing every sub-task requirement ("uh... we just spent $500 million with the goal of making a website and nothing actually works!"). We're in a fast society. Nobody wants to spend three years in pseudocode and dependency evaluation and documentation and procedures before laying down real code, so the best we can do these days is augment our decision making as our understanding of the problems and goals evolve then resolve all conflicts and confusions in as real-time as possible.