Discussions like this arise mostly because developers today think less about whether a feature should be built and more about how it should be architected and t

Discussions like this arise mostly because developers today think less about whether a feature should be built and more about how it should be architected and tested. For decades, we've been conditioned to think that by the time a feature is written down on paper, someone else has crossed all the Ts and dotted all the Is to determine that the feature has value and should be built. It's far easier to focus on low value testing issues than attempt the harder work of convincing the customer/product owner that certain features should not be built.