I've tried similar things, but any time it's been communicated upwards the response has been (essentially) "That sounds scary. Where's the research that says th

I've tried similar things, but any time it's been communicated upwards the response has been (essentially) "That sounds scary. Where's the research that says that'll improve things over this awesome agile thing we've been doing and that all the marketing buzz says is awesome?" I totally am in agreement that you have to treat it as some new thing (rather than them just doing the old thing correctly, instead of incorrectly as they have been), but even assuming they were on board to consider it, it gets tricky. Do you just rebrand agile? Then they're going to screw it up the same way. Do you take a more prescriptive approach, that this new 'eliga' (agile spelled backwards) process means we do it -this- way? Because then you're not really doing agile, and teams that need to operate differently are not going to be as productive. Etc