What is it?
The Scaled Agile Framework (SAFe) supports companies to scale agile methods on an enterprise level. It was developed in 2011 by Dean Leffingwell.
Strengths (Top 3)
- Easy to sell
The closeness of this model of agile scaling to classic enterprise structures makes it easy to convince management to adopt it. There is also little resistance from role-holders of classic structures, as they can easily find a counterpart of their previous role in the depths of the SAFe model. Last but not least, the clear structure of roles and processes conveys security – especially to those who are not yet familiar with agile thinking. - Holism
SAFe focuses on the value stream in the company, taking into account all areas of the company. It therefore explicitly includes not only software development but also areas such as marketing (“business agility”). In this way, breaks in the coordination of the company divisions can be avoided. - Information availability
The wide spreading of this model makes it easy to find information or supporters (network effect) for the practical conversion of the model as well as the solution of arising problems.
Weaknesses (Top 3)
- High complexity
Many details and concrete requirements make the framework bureaucratic, prescriptive and confusing. Some companies reinforce this by choosing the next largest of the 4 size classes of the model (Essential, Large Solution, Portfolio, Full): After all, you plan to grow and don’t want to follow SAFe implementation directly with the next change. - Customer-distanced
Many intermediate layers and roles make it difficult for the agile team and especially product owners to get through to “their” customers. While this can be said about all frameworks of agile scaling, SAFe sets the hurdle especially high here. - Minimum Agile
The advantage of ease of adoption due to similarity to classic, non-agile, structures makes implementing agile models of thought and action much more difficult. In the worst case, one experiences agile theater, where the process is executed but not rudimentarily understood.
Feedback
If you have any comments, ideas, suggestions or other feedback about this article, feel free to send me an email at Feedback[at]scrummastersmind.com.
Sources:
- https://scaledagileframework.com/, downloaded on 18.03.23