An Agile project can...
* Accept feature requests in any order (the PlanningGame, DoSimpleThings, RefactorMercilessly)
* Release any integration (TestDrivenDevelopment, FrequentIntegration)
* Minimize the time between committing to a feature and letting end-users profit from it (SoftwareInProcess)

"Agile" is an umbrella term used to describe a variety of methods that encourage continual realignment of development goals with the needs and expectations of the customer. See http://AgileManifesto.org for a concise statement of beliefs held in common by the developers of these varied methods.

----
* A great overview of the state-of-the-art of agile methods can be found in JimHighsmith's book AgileSoftwareDevelopmentEcosystems.
* TheNewMethodology -- the best, and updated description I know concerning agile processes (Astrid Lumbye)
* http://www.inf.vtt.fi/pdf/publications/2002/P478.pdf -- survey of agile methods

* A new one called TgpMethodology an innovation of ArtwareSoft focus on integration of business professionals into the development process. It is based on a unique architecture. http://www.artwaresoft.com -- The TGP Methodology

-----
No M-word here... try AgileProcesses instead.

JeanPierreVickoff still uses the M-word in calling for "unification" (see PumaProposal)

----
See MethodologicalPluralism, AgileSoftwareDevelopment, AgileProcesses

-----
CategoryAgileMethodology