It has, because embracing agile as it was laid out in 12 principles put too much power in these "technical" people by giving them a stake at the table, to anyon

It has, because embracing agile as it was laid out in 12 principles put too much power in these "technical" people by giving them a stake at the table, to anyone who doesn't work in an ENG first / ENG focused company. If you look at how "Agile" is implemented in most organizations - even in technology companies! - there's alot of barrier process put up to sideline / minimize engineering input by focusing on stakeholders where stakeholder is defined by everyone telling engineering what to do as opposed to engineering being seen as a valid and reasonable stakeholder too. I think its because in part there is a linear pipeline that the non technical business side sees as how things go: you plan X, it gets designed by Y, and then "manufactured" by engineers, if you will. Engineers - good ones, in my estimation - want more stake in each step, both in planning and design, because often its engineers that work on the system the closest (you'd be shocked how many designers don't use their own products on a daily basis, same goes for alot of business oriented folks) and this is not "the way the world works". Thats my thesis anyway