Personally, I think it is a problem of *marketing* methodologies to developers with *engineering* mindsets.

All these things are pushed as the holy grail to make everything work, but it is always vague, handwavy and reeks of BS. Engineers will consider the merits of an extra horsepower on their motor or a 10% reduction in friction on a guide, or two more cores in their CPU. There is at that point a known, hard benefit, and the engineer will look for all the hidden downsides before buying in. Methodologies on the other hand, lack numbers or hard facts; trying to sell it falls flat at the first step (except that management buys right in, to the derision of the engineers). It becomes just one more silly thing that management has latched onto and forced on everybody. Same as that one more useless collaboration app auto-installed that nobody asked for, that one more layer of lag-inducing security checks, or that shuffling of everybody to a new cubicle yet again.

The people pushing it claim that it will be a benefit but there are no numbers, no guarantees, and it has all been lies and empty promises before. Then it becomes a self-fulfilling prophecy of doom.