SAFe is not agile! Here is why it might still be useful
Despite the contempt many of us agile folks have for SAFe, this “Scaled Agile Framework” might still have one useful purpose.
Note: this article is based on my experience and observations. You may disagree with my opinion. So I invite you to share your perspective with me.
Why many agile people hate SAFe
Just looking at the overview image of SAFe gives many agile folks (including me) goose bumps. This complex map of process hierarchies, roles and silos doesn’t look very agile to me. David Peirera wrote a great article about why so much about SAFe is not agile.
SAFe tries to take the agile Scrum framework (which was invented for 2-pizza teams of originally 10 or fewer people) and scale its use up to companies with thousands of employees. And to be honest, trying to scale agility to thousands of people will ALWAYS lose some agility — smaller teams simply can be more agile. So the goal of all agile scaling efforts (like LeSS, Nexus or the Spotify approach (not a framework!)) is to lose as little agility as possible along the way. And SAFe does a particularly bad job at that!
