Many peoples of North Africa migrate within their buildings in both daily and seasonal patterns to take advantage of the various microclimates the buildings create.
The real world of technology denies the existence and the reality of nature. For instance, there is little sense of season as one walks through a North American or western European supermarket.
Just as there is a little sense of season, there is little sense of climate. Everything possible is done to equalize the ambiance – to construct and environment that is warm in the winter, cool in the summer.
I am fascinated by the Farmer’s Almanac, and the “Planting by the Moon” guide in particular, which has advice such as: “Root crops that can be planted now will yield well.” “Good days for killing weeds.” “Good days for transplanting.” “Barren days. Do no planting.”
I think it’d be funny to make up an almanac for writers and artists, one that emphasized the never-ending, repetitive work of the craft.
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.