Most people — Agile evangelists are no exception — tend to define Agility via a specific way of working (e.g. via SCRUM) or via the Agile Manifesto (which is a set of too easily – and by far too often – misunderstood principles totally ignoring the CIO as one of the most important stakeholders).
But to really understand what it means to become agile as a software developer (or a developer’s client) in some positive manner
- we have to understand Agility as a Necessity to survive in today’s fast changing environment,
- we have to adopt the right Agile Attitude,
- and we have to accept Agile as a Best Practice.
If you don’t believe me, there are others who also say:
- We are tired about reading misinformation about Agile,
- Agile is certainly not SCRUM (or some other specific process), and
- Agile is often used for an excuse not to work professionally enough.
ggreiter 
Comments
The problem really is that the Agile fathers did not create a very clear definition of Agile. They just created some guidelines, and then out of these guidelines everyone created his own Agile framework.
The Agile community needs something like the PMBoK.
This is getting a bit more subjective, however this is a great blog. Keep up the good work.