Well said about the fuzzy nature of real world requirements. Given that there may be tons of cost savings if they could get Product Managers to get to define requirements in a more testable/quantitative way. There may be a push towards getting more out of the Product and Requirements side of things. Like making them define things vis-a-vis leetcode/topcoder style of problem statements. Probably likely in companies or divisions where the requirements can be quantified in such a fashion.