There are multiple views on Agility.
Highsmith in 2002 explained it as ability to handle the change in this dynamic environment where Business requirements change very frequently. If one is able to handle to change, agility is attained. He also added that it’s also an ability to make a trade off and balance the flexibility and stability. Requirements change can happen endlessly. There should be a point where a equilibrium is attained between flexibility towards adopting changes to stability of project/product. E.g. if the project is trying to optimize a system and working on some configuration items, there should be a balance between configurable parameters and level of optimization. Over-optimization may make system less flexible and over configurable items may make system too flexible to achieve stability.
Agile approach is always mistaken as a shortcut approach and less structure approach. However now it’s evident with lot many case studies and projects. Agility doesn’t imply that structure is not there rather it’s a balance game. Agile teams and projects are more focused and systematic due to which they achieve excellence as a team