Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
As Agile methodologies have matured, organizations of all sizes have sought ways to extend their benefits beyond individual teams. Enter the scaling frameworks designed to bring structure and coordination to Agile practices at the enterprise level. Yet, as companies implement these frameworks, a pressing question emerges: Do scaled Agile frameworks truly enhance organizational agility, or do they risk reintroducing the very bureaucratic waste that Lean principles aim to eradicate?
This blog post examines the intersection of scaling frameworks and Lean thinking, weighing their benefits and pitfalls, and considers whether agility is being enhanced or undermined in the pursuit of scale.
-Have you worked in organizations that adopted a scaled Agile framework?
-Did the scaled Agile framework enhanced Agility and value delivery, or did it create new layers of bureaucracy?
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Interesting reflection.
In my experience, scaled Agile frameworks can both enhance agility and create bureaucracy, depending on how they are applied.
One thought that comes to mind is that Lean does not oppose structure. Lean opposes waste.
As organizations grow, coordination costs naturally increase, and some mechanisms that appear bureaucratic may actually be necessary to manage complexity, align priorities, and manage dependencies across teams.
Perhaps the real challenge is not minimizing structure, but ensuring that every layer of coordination creates more value than friction.
The distinction between necessary coordination and bureaucratic waste may be more important than the distinction between frameworks and agility itself.
...
1 reply by Stelian ROMAN
Sep 13, 2026 9:47 PM
Stelian ROMAN
...
"Lean does not oppose structure. Lean opposes waste; neither does Agile. Any framework, including the simplest (Scrum) comes with a process, roles, and responsibilities. The Agile Manufacturing Enterprise was designed for organisations with tens of thousands of employees. The difference between a Lean organisation and an Agile one is that in Agile, 'waste' is a learning tool, and the impact is measured on the final product rather than on the development process.
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
he outcome depended largely on how they were implemented.
Scaling frameworks can improve alignment, coordination, and visibility across multiple teams. At the same time, they can introduce unnecessary complexity when ceremonies, roles, and governance are added without a clear purpose.
The most successful implementations I've seen focused on solving specific organizational challenges rather than trying to implement a framework exactly as described.
...
1 reply by Stelian ROMAN
Sep 13, 2026 10:02 PM
Stelian ROMAN
...
"The outcome depended largely on how they were implemented." It also depends on the framework itself. You can eat soup with chopsticks, but it's better if you use a spoon. Sometimes 'scaling' means relabeling existing processes and roles as Agile. That's where good leadership makes the difference. The difference between doing Agile and being Agile.
Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Jun 17, 2026 5:21 AM
Replying to Luis Branco
...
Interesting reflection.
In my experience, scaled Agile frameworks can both enhance agility and create bureaucracy, depending on how they are applied.
One thought that comes to mind is that Lean does not oppose structure. Lean opposes waste.
As organizations grow, coordination costs naturally increase, and some mechanisms that appear bureaucratic may actually be necessary to manage complexity, align priorities, and manage dependencies across teams.
Perhaps the real challenge is not minimizing structure, but ensuring that every layer of coordination creates more value than friction.
The distinction between necessary coordination and bureaucratic waste may be more important than the distinction between frameworks and agility itself.
"Lean does not oppose structure. Lean opposes waste; neither does Agile. Any framework, including the simplest (Scrum) comes with a process, roles, and responsibilities. The Agile Manufacturing Enterprise was designed for organisations with tens of thousands of employees. The difference between a Lean organisation and an Agile one is that in Agile, 'waste' is a learning tool, and the impact is measured on the final product rather than on the development process. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Jun 22, 2026 6:32 PM
Replying to Lissette Indhira Pimentel Sosa
...
he outcome depended largely on how they were implemented.
Scaling frameworks can improve alignment, coordination, and visibility across multiple teams. At the same time, they can introduce unnecessary complexity when ceremonies, roles, and governance are added without a clear purpose.
The most successful implementations I've seen focused on solving specific organizational challenges rather than trying to implement a framework exactly as described.
"The outcome depended largely on how they were implemented." It also depends on the framework itself. You can eat soup with chopsticks, but it's better if you use a spoon. Sometimes 'scaling' means relabeling existing processes and roles as Agile. That's where good leadership makes the difference. The difference between doing Agile and being Agile. Saving Changes...
Community Champion
