LeSS (Large-Scale Scrum)
LeSS collapses many teams into cross functional feature teams under one product backlog and one product owner, synchronizes them on a shared sprint, and runs an overall retrospective to fix systemic problems, covering Structure, Coordination, Flow, and Learning.
Craig Larman and Bas Vodde, 2008
The origin of the framework, as the directory records it. The mark grades the origin, not this page.
Umbrex, LeSS (Large-Scale Scrum)
The directory entry this score was read from. Umbrex is a consultancy network; its summary is the reference, not a primary source.
Scored against the twelve cells, it loads four: Structure, Coordination, Flow, and Learning. The other eight it leaves to you. None of Composition, Evidence, or Mastery is among them, which is the usual result in this directory: the questions an agent in the loop raises first are the ones the literature answers least.
This is not a summary of the framework. Umbrex has one; the link under Sources goes there.
What is the smallest unit that can own a customer outcome end to end?
What synchronizes the work when there is no room and half the team is not a person?
What limits throughput, and what is supposed to happen when the line stops?
How does tacit judgment become reusable, and who owns the loop that has to close?