Also, the "forced" flavor of agile tends to be one that is disconnected from the trade offs that make agile work. I was in a shop that had a forced agile adopt

Also, the "forced" flavor of agile tends to be one that is disconnected from the trade offs that make agile work. I was in a shop that had a forced agile adoption. The development teams were all enthusiastic about it, went to training, etc. However, the very same managers that pushed it didn't understand it so we got: * hard delivery dates with fixed functionality (though we could drop small features at the margins) * lots of useless planning/status reporting ceremony (more than pre-agile) * pressure to "just start coding" instead of gathering requirements (since "we're agile now") * very litter tolerance for going back and fixing things that weren't done right (made more common by the above bullet) It didn't really work, and most of those managers are gone now.