Just like our relationships, I suppose? First we fall in love with all the wonderful things that we’ve been longing for all along. And then, you start seeing the flaws…
As with any framework, it can only be as imperfect as the people using it. It doesn’t matter how perfect the theory sounds, if it doesn’t work in practice, it’s not very useful.
After all, it’s not the perfection of the theory of the framework that we’re after, but rather the underlying values that drive our interactions in a meaningful way.
Because of the importance of those values and principles, I struggle to convey the message of agile in it’s entirety.
This is not unique to SAFe, but I find that there is more clutter which obscures the new learners from the true character of agile, and what it stands for. People are fussing and panicking about not missing a step in the hugely choreographed “play”, and they forget to enjoy and smile. I know it’s not that simple, and that every implementation takes TIME, but I cannot help but question if SAFe is the right approach when starting with an agile transformation.
We forget about the agile manifesto, the values, the principles… The core where it all started. People start valuing their preparation & analysis over collaboration. Others cannot keep up, and instead of ensuring that problems get raised they value cloak & dagger over transparency.
Like I said before, this surely happens with every type of agile implementation, sometimes? I just found that these seem much more prominent in my experience during a SAFe implementation.