There were days in the Java world when we were framework enthusiasts. Every single day new framework was deployed to sourceforge, googlecode, github, bitbucket or so on.
So it was turned out that being a Framework-Junkie led you to really poor architecture (see these articles: * Driven * do not change anything, Extremely Pragmatic Software Architecture, Measuring Software Architecture, Frame-of-our-work, What Exactly Are Patterns?).
Having this technological discussion out of our heads we started new one: what is the best agile framework. Yep, we are quite poor learners. How it possible that people who are trained to see repeatable patterns in the world don't see that we replay the old movie? - searching for the Silver Bullet.
Teams or whole organizations jump from one agile framework to another one - in the same way they jumped from Struts2 to JSF, from JSF to Spring MVC, etc. But they don't achieve desired effects.
If you wonder how to jump from SAFe to LeSS or another, or maybe you wonder which agile framework to use - I know the answer. Are you ready? - IT DOES NOT MATTER.
That's right - an agile framework doesn't do the job - PEOPLE DO. Don't try to bypass teams members skills by a new framework. This is a cognitive bias I described here.
Any framework was developed by highly-skilled professionals as a generalization of their daily routine. Having highly skilled people you will apply any framework, but a framework won't make your people better.
Again, frameworks are useful, but people and their skills are the key success factor.
