Individual scaling: We look at what suits you best
Which is better, SAFe or LeSS? We at wibas think so: It's your organization. It depends on what you make of it. So we look at what suits you best. The good news: You can combine all agile frameworks. You can't really go wrong with the selection. The crux of the matter is implementation. And that's exactly where we start with you.
"We'll work with you to find a solution for agile scaling that fits your business."
SAFe and LeSS are collections of samples.
SAFe (Scaled Agile Framework) and LeSS (Large Scale Scrum) offer patterns for how to organize work across team boundaries in an agile way. They offer different solutions, but they can be combined with each other. For example, SAFe offers as one pattern the "Planning Interval" which holds a cadence superior to the Sprint. LeSS offers as a pattern a Product Owner for several teams, which the team members then support in their requirements management. Both are good ideas - it depends on what fits the specific situation and what fits the company. That's why you get a very pragmatic view from wibas: You can take good ideas from one framework and apply them to the other.
LeSS fits into SAFe. SAFe fits into LeSS. And then there was Kanban.
When it comes to more than one around one team, sooner or later you can't avoid frameworks like SAFe or LeSS, which provide patterns for agility across team levels. We're happy to look with you at which framework is right for your situation. And as pragmatic as we are, we take a LeSS configuration for an Agile release train without batting an eye. Likewise, we love the principles of LeSS: these two provide good guardrails for any SAFe Release Train Engineer. And then there is Kanban, which represents a third, alternative approach to the agile organization. This is what we are here for: to select the right tool for the specific situation with you and bring it to life in practice.
SAFe versus LeSS versus Kanban
SAFe addresses the whole agile organization, puts the main agile frameworks together, and provides a lot of detail. It's great because you can see how things mesh - and because you can outline the entire agile organization. It's dope because it's a really complicated picture.
LeSS primarily addresses product development, builds on Scrum, and focuses more on guardrails instead of details. This is great because LeSS is focused and easy to understand. It's silly when not everything is Scrum and you're still faced with the task of integrating other frameworks.
Kanban comes across as very casual: Here it is simply: "Start with what you are doing right now - and follow evolutionary changes". That's great because it always fits. It's dumb because it's also easy to lose orientation with such an open target picture.
It depends on what you make of it.
Actually, it's not that important what you choose. What is important is the understanding that it depends on you, on your organization and its understanding of agility. Frameworks give ideas on how different work situations can be designed in an agile way. However, they are not blueprints. You need to look specifically into the "idea box" for each team, each organizational unit, and each work situation, and select what fits situation-specifically, and then make something out of it for you. True to the saying: All frameworks are wrong, but some are useful.
Organization in a digital age
Our open-minded thinking and knowledge of how the patterns of the different frameworks fit together is described in the book "Organization in a digital age"is presented in detail. All those looking for a pragmatic approach to frameworks will find here the most important patterns prepared piece by piece - and a translation of the terms between the different frameworks.