Agile Transformations Aren’t Even Close to “Done”

No, your DevOps/Agile transformation isn’t “done” because you got an award.

• No, your DevOps/Agile transformation isn’t “done” because you got an award.
• Or because you had your CEO hail it as concluded as they handed some expensive Big 4 some unGodly new contract for “transformation maintenance” (this, sadly, shockingly, is a real thing).
• Or because your people are no longer actively moaning about having to do Agile and attend all the ceremonies. (That you know of, at least.)
• Or because you see the enterprise ticking along and now there are retros and stand-ups so it must be “done”.

Or because you had your CEO hail it as concluded as they handed some expensive Big 4 some unGodly new contract for “transformation maintenance” (this, sadly, shockingly, is a real thing).

Or because your people are no longer actively moaning about having to do Agile and attend all the ceremonies. (That you know of, at least.)

Or because you see the enterprise ticking along and now there are retros and stand-ups so it must be “done”.

Or because you get away with not understanding the soul of the matter and still churn results that seem good enough. Because you can’t see far enough into the future to understand what will happen with the diminishing outcomes when they dry up because the foundation wasn’t there.