Agile at scale
Frameworks for running agile across hundreds of people: SAFe, LeSS, and their relatives.
Dean Leffingwell, Scaled Agile Framework
2011 onward
Scaled Agile, Inc. adoption and outcome claims
vendor material
Dean Leffingwell published the Scaled Agile Framework from 2011 onward. It layers portfolio, program, and team levels over agile teams, with a release train as the unit of coordination. Large-Scale Scrum and the Spotify model are the lighter relatives.
The canvas treats the family as a shape with a strong Flow story and a thin Authority story: it says who plans and who builds, and rarely who may halt or who answers for the outcome. Adoption claims from the framework's owner are marked as such.
What limits throughput, and what is supposed to happen when the line stops?
What synchronizes the work when there is no room and half the team is not a person?
What is the smallest unit that can own a customer outcome end to end?