What does Agile mean?

Nice question!!! But where can I find this definition?? In PMBOK version 6???

Sorry for joining late to the party, but here I am (hehehehe). Agile was "formaly" born in 1990 inside the USA DoD NSF/Agility Forum which took place inside the Leihigh University trying to find an alternative to Lean (because of that Lean and Agile are not the same). It was moved by one seminal article published in middle 1980 in the USA named "Agile Manufacturing". Time after people that have methods to create software products and those methods were created taken Lean model they created the Manifesto (the word "software" is inside the name becasue a reason). The definitions created into the Forum are Agile:A way of thought and behave whose focus is the increase of value for the client and the quality", agility: "Be able respond to a wide variety of unexpected external surprises and create external surprises.Being agile will assist businesses who face unpredictable circumstances"
This is a short article published by the PMI:
"Perfectly Positioned", http://www.pmnetwork-digital.com/pmnetwork/april_2016?pg=73#pg73
"Perfectatmente Posicionado",http://www.pmnetwork-spanish.com/pmnetwork...016?pg=68#pg68.
Here some articles that I think could help to understand that Agile is not a synonim of software and in this case take the whole potential of Agile:
https://steveblank.com/2016/11/10/how-the-...vation-culture/
https://hbr.org/1986/01/the-new-new-product-development-game
https://hbr.org/2016/04/the-secret-history-of-agile-innovation
https://www.scruminc.com/wp-content/upload...-with-Agile.pdf

Very good description. I think we were missing you a bit.

So here is a question for you, what are the minimum criteria that must be met in order to be called Agile?

I would think at a minimum it must be iterative and incremental, which by default gives you the ability to make changes and work on quality.

I think as it has evolved, more things tend to be included on what constitutes Agile, but iterative and incremental was at least where it started. (I would add at least a couple more things to the list now as it has evolved some)

Take a look at Modern Agile - I prefer their four value statements, especially Make People Awesome!

I like the four values of the manifesto.

I like focusing on the product as a primary measure of success.
I like embracing change or being open to change and flexibility.
I like servant leadership and letting the team decide how best to do their work.
I like the focus on quality and continuous improvement.

I disagree with some of the other 12 principles of the manifesto, I don't think we need to be face to face to do an exceptional job, and who actually likes and works well in a collocated team (open office environment)?

The problem is: if you take the Manifesto then you will not take advantage of Agile. Agile is nothing to be with the Manifesto. The Manifresto is about software products not Agile. To be Agile and gain into agility the key focus is: 1-systemic thinking. 2-enterprise architecture. If you forget that then you will not being success with Agile. Other source (because I do not want to continue making references about I publish): https://agnosticagile.org

The problem is: if you take the Manifesto then you will not take advantage of Agile. Agile is nothing to be with the Manifesto. The Manifresto is about software products not Agile. To be Agile and gain into agility the key focus is: 1-systemic thinking. 2-enterprise architecture. If you forget that then you will not being success with Agile. Other source (because I do not want to continue making references about I publish): https://agnosticagile.org

But we can work with general points the manifesto raises. Replace software with "product" or "Work Output" or something else. I know the manifesto was for software, but we can apply it to larger things.