#Nexus #Scrum #SAFe #Kanban
As a coach, people always ask about #scalingframeworks, which #framework should we go for; #SAFe or #LeSS or something else? Also, questions on team size like 'my team are big, we are 20 or even more, and we are part of a tribe (so, one team, but quite big); what should we do?', should we #re-org and split or become a separate #tribe...if we don't, then how we work as an #agile #team. Is there any framework around such a situation?

There are always questions like this. The truth is that all the frameworks are #useful and #powerful, but it's still #contextual; none can work well in all #contexts. To determine the #right #context, we need to think beyond size; it more about where the backlog ownership should lie.

To choose a framework, think both the size and the #backlog #ownership.
Let's look at the three possible scenarios to understand it better.

1. Single Scrum Team
2. Multiple scrum teams
3. Multi-team scrum - this is different from the multiple scrum teams scenario. There is only one backlog, one product owner, but the team size is quite big, say 15-20, or even more. In my experience, a framework like LeSS goes fantastically well. There is only one scrum, but you will be doing its ceremonies differently. You split your team into real or virtual sub-teams, all doing one-scrum together with one PO and one backlog. The planning meeting would break in planning 1 and 2; each subgroup may have separate dailies; you will have a joint review, again retrospection first at the sub-teams level, and then a common one, so on and so forth.