For the past year and a half my organization has been operating in a Scaled Agile environment. This has invigorated the firm noticeably and been adopted enthusiastically. But as with anything, there is a learning curve.
It is worth while being aware of some of the weaknesses of the framework so we can better understand the challenges that our partners in the business may be facing.
This isn’t meant as a criticism of the Scaled Agile Framework (aka “SAFe”), rather a reminder of aspects of it that we should keep in mind when implementing it in our own organizations. Much of this is based on what I have observed directly.
- SAFe introduces significant complexity, especially for smaller organizations or teams, which can make it difficult to implement effectively. “Small” is an objective term and open to debate, but overall, I think this point will resonate with many in smaller organizations SAFe is seen as overly bureaucratic, with numerous roles, ceremonies, and artifacts, leading to increased overhead and administrative burden.
- Many critics of SAFe feel that it places too much emphasis on processes and frameworks, potentially overshadowing the importance of individual interactions and self-organization. This can be overcome with a good level of self-organization and a culture of collaboration.
- There are perceived to be “dependency management challenges“. Managing dependencies between Agile Release Trains (ARTs) and coordinating cross-team activities can be challenging and may result in delays or inefficiencies.
- One of the most common criticisms of SAFe implementation is that requires a significant cultural shift, which can be difficult to achieve, especially in organizations with deeply entrenched ways of working.
- SAFe has a rigid structure that may not adapt well to certain project types or organizational cultures, leading to resistance and decreased agility. There’s an argument that it stifles creativity and innovation, particularly in environments that require rapid experimentation and adaptation. Different versions of SAFe can be implemented suited to an organization’s specific needs and culture. Unless one is in a firm that engages in rapid experimentation, this shouldn’t be a major issue.
It needs to be pointed out that these challenges are more likely to be encountered at the outset of using Scaled Agile when the organization is still learning the methodology. Given time and familiarity with the concepts, the organization will become more and more adept at Agile. That’s when the benefits will really accrue.
Tom Cremins 