#57 – An UnSAFe Protest

If implementing SAFe hasn’t made your company more agile (whatever that means), the blame is not with SAFe, but potentially with the people who implemented it without driving the needed change in company culture or behavior.

So, instead of complaining about how SAFe has skewed the purpose and dynamics of agile, let’s appreciate how the work of Dean Leffingwell, et. al., has actually helped companies to start working with integrated increments, feedback loops, business value, a common way of prioritizing, managing dependencies, etc.

And remember: SAFe is not the end state, but rather a means to start or continue an agile journey. You should always consider the trade-off between the overhead of SAFe and its benefits, and when it’s the right time to descale.