Why do agile transformations fail?


27 Aug
27Aug
  1. “Agile” is too broad in scope and interpretation to be useful as a direction for transformation

  2. There is generally no effort made to find where there is alignment on specific principles in management/leadership, or what practically needs to change (e.g. do they all understand and agree that limiting WIP is necessary for improving throughput and quality, and are taking practical steps to do that? Uncontroversial slogans like “Put the customer first!” are easy to agree with and useless for transformation)

  3. There is generally a focus on teams and individual “workers” needing to change, not management; it is believed management should set the agenda for the transformation (and report on it) rather than lead the way in terms of changing their own behaviour and making immediate practical improvements

  4. Because of the scope of “Agile”, and because it is generally slow-moving corporations who feel they need it in order to “speed up”, they hire hundreds or even thousands of “Agile Coaches” and consultants. I promise you — even if the level of competence and experience in most of those coaches is high for these kinds of situations (which it isn’t), you are left again with the problem of lack of alignment on principles and approach.

Thanks for reading! If you are looking for help with your software or product delivery, I provide agile coaching, public training (both theory and practical) up to executive management level, and more. As well as public events, I can also run training internally in your organisation for a massively reduced cost, so please ✍ get in touch.
Comments
* The email will not be published on the website.