Why Enterprise Agile Teams Fail

... they have recently embarked on a journey to become “Agile.”... neither explicit support nor discouragement from senior executives... they are failing for the same list of reasons as every other team I have met with in the last 5 years. Here are those reasons:...
1. There is no clear vision for the product....The “idea” has been handed down by some senior executive based on an epiphany during a leadership retreat... this particular executive won the influence battle and got their pet project funded...
2. The business metrics are obfuscated...
3. You keep interfering..-. cut it out. You don’t get special privileges in the prioritization scheme just because you’re more important on the org chart....
4. Your teams are not dedicated... Most people on a project are assigned to multiple other projects... This. Doesn’t. Work....
5. Your teams are not colocated....
8. You are doing too many things at the same time....Immediately implement WIP limits. If you have a 10-person team, set the WIP limit to 5 items so that everyone is forced to pair up with someone else...
9. It takes too long to deploy new software....Solution: DevOps. Any engineer should be able to spin up new development and testing infrastructure at any time...
10. The rest of the enterprise is oblivious.... Your “experiment” in Agile... is completely off the radar to ... critical functions that you will need in order to get your work done.... three strategies for dealing with Agile to non-Agile translation... do all simultaneously