I’d say that that huh is the foundational block of curiosity. To get good at the huh is to get good at both paying attention and nurturing compassion; if you don’t notice, you can’t give a shit. But the huh is only half the equation. You gotta go huh, alright — the “alright,” the follow-up, the openness to what comes next is where the cascade lives. It’s the sometimes-sardonic, sometimes-optimistic engine driving the next huh and so on and so forth.
Form comes from wonder. Wonder stems from our 'in touchness' with how we were made. One senses that nature records the process of what it makes, so that in what it makes there is also the records of how it was made. In touch with this record we are in wonder. This wonder gives rise to knowledge. But knowledge is related to other knowledge and this relation gives a sense of order, a sense of how they inter-relate in a harmony that makes all things exist. From knowledge to sense of order we then wink at wonder and say How am I doing, wonder?
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.
Features don’t work, in the sense that they can be easily gamed. A brittle and perfunctory implementation, done quickly, is going to score more intramural brownie points over a robust and complete one. If the question is "does product A have feature X?" then the answer is yes either way.
We use the term feature factory as a pejorative to designate companies addicted to adding features, while accumulating incalculable so-called technical debt. This situation is driven by management for the convenience of marketing, and I am skeptical that a more faithful application of Agile principles will correct it. Indeed, I suspect Agile processes are constitutionally vulnerable to this kind of compromise.
The presence of a feature can only indicate to a user if a goal is possible, behavior will determine how painful it will be to achieve it.