SAFE (Scaled Agile Framework) is a popular methodology for implementing Agile at scale, yet it has recently come under criticism for its rigidity and lack of flexibility. It’s argued that SAFE’s prescriptive nature can stifle innovation and creativity, going against the very principles of Agile. Critics contend that SAFE’s focus on process over individuals and interactions can lead to a loss of the Agile mindset, which values individuals and interactions over processes and tools.
SAFE is also criticised for its complexity. The framework contains a multitude of roles, artefacts, and processes that can be overwhelming and difficult to implement. This complexity can lead to confusion and a lack of clarity, hindering the Agile transformation process.
In addition, SAFE’s emphasis on certification has been called into question. Critics argue that certification does not necessarily equate to competence or understanding, and that it can create a false sense of security. They suggest that the focus should be on building competence through experience and learning, rather than on obtaining certification.
Despite these criticisms, SAFE continues to be widely used, and many organisations have found success with it. It’s important to remember that no one-size-fits-all solution exists for implementing Agile, and what works for one organisation may not work for another.
Go to source article: https://www.agile-moose.com/blog/2019/4/7/safe-no-longer-my-final-farewell