I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome.
I always have a hard time wrapping my mind around some of the classic user questions: What is this thing for, is it for novices or professionals, etc? I do my best to avoid these questions, because the best thing you can possibly accomplish as the maker of a tool is to build something that gets used in ways you didn’t anticipate. If you’re building a tool that gets used in exactly the ways that you wrote out on paper, you shot very low. You did something literal and obvious.
In a natural landscape, each element is part of the greater whole, a sophisticated and intricate web of connections and energy flows. If we attempt to create landscapes using a strictly objective viewpoint, we will produce awkward and dysfunctional designs because all living systems are more than just a sum of their parts. Our culture has tried to define the landscape scientifically, by collecting extensive data about its parts.
These methods are much like the group of blind mullahs in the Sufi tale, who try to describe an elephant.