ScALeD
ScALeD, or Scaled Agile Lean Development, is a set of guiding principles designed to help organizations effectively scale their agile practices. It emphasizes the importance of excited customers, happy and productive employees, global optimization, supportive leadership, and continuous improvement. The principles were formulated by Christoph Mathis, Markus Gärtner, Stefan Roock, Andreas Schliep, and Peter Beck.
How AME3 Implements the ScALeD Principles
AME3 was designed by two of the ScALeD co-authors — Andreas Schliep and Peter Beck — to put these principles into practice. The framework provides concrete leadership roles, organizational structures, and iterative rhythms that bring each ScALeD principle to life at enterprise scale.
Excited Customers. AME3 places customer value at the center through clear accountability. The Owner defines the Ambition — why an Arena exists and what success looks like — and selects Goals from the Enterprise Backlog to focus the work. Teams deliver small, working Improvements every Match, building a growing Arena Product that customers and stakeholders can inspect. Because Matches are timeboxed to one month or less, the organization gets fast feedback on whether it is building the right thing and can adjust direction before wasting effort.
Happy and Productive Employees. Each Arena contains self-managing, cross-functional Teams that decide how to accomplish their work. Teams pull Improvements from the Arena Backlog, coordinate with each other directly, and define their own completion standards. The Coach develops team capabilities and facilitates decision-making without directing. This combination of autonomy, growing mastery, and clear purpose — provided through a shared Goal — creates an environment where people can do their best work.
Global Optimization. AME3’s strategic doctrine Overall Optimization ensures that every improvement benefits the entire enterprise, not just the unit making the change. All Teams within an Arena share the same Goal, so their work aligns naturally without competing individual targets. The Arena Product and Enterprise Product are visible to everyone, and the Tournament provides regular enterprise-wide inspection by Accountable Representatives. Matches and Tournaments create synchronized rhythms where all parts of the organization coordinate and reflect together. Because organizational structure and product architecture are two sides of the same coin, AME3 treats them as one problem — slicing organizations along stable interfaces and reducing dependencies systematically.
Supportive Leadership. AME3 distributes leadership across three complementary functions: the Owner leads toward product success, the Coach leads toward effective work systems, and the Team leads toward customer satisfaction. None of these functions can override the others, which prevents top-down command-and-control. The Owner sets direction through Ambitions and Goals, not daily instructions. At the enterprise level, Accountable Representatives assess overall progress and advise the Enterprise Owner, while the Enterprise System Lead supports organizational evolution. Leadership’s job is to provide clarity, support, and the right environment — decisions are made by those doing the work.
Continuous Improvement. AME3 embeds inspection and adaptation at two levels. Within each Match, Teams assess the Arena Product and their own work process, then feed new Improvements into the Arena Backlog for the next cycle. At the Tournament level — typically quarterly — Accountable Representatives inspect the Enterprise Product and organizational design, and the Enterprise Owner adjusts Ambitions and the Enterprise Backlog accordingly. This dual-loop structure means that product quality, work processes, and organizational design all improve continuously based on evidence, not assumptions.