One of the responsibilities for an architect is to provide a space that is usable and enhances the possibilities for what you do. But mostly, museums are just the opposite; they're horrible spaces, anti-art, they can't be used. They can't function, they overwhelm it. So in a way, they become objects in themselves many times, almost sculptures, and they get a lot of aggrandizement out of it...In terms of Bilbao, the one difference there is that they did not really want a museum, they wanted a monument. They wanted a thing that would bring people to the Bilbao.
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.