Why is the agile manifesto called a manifesto?
briley last edited by
Looking at the contents of the manifesto, I do not see if fulfilling the definition of a manifesto which is
The document details the principles but nowhere does it argument why those principles are valuable. For example "Individuals and interactions over processes and tools". Why? Why individuals and interactions over processes and tools?
Cambridge Dictionary defines a manifesto as a statement of "beliefs, aims and policies". The Agile Manifesto for Software Development does indeed set out some beliefs and aims, while the history page on the website explains some of their rationale.
In spite of its URL, agilemanifesto.org is not and has never been "the agile manifesto"; it is a manifesto specifically for agile software development and it makes no claim to be a proposal or statement about agility in general. Organisational agility and agile methods had existed for at least a couple of decades before the "software" manifesto came along. Since its authors were appealing to IT professionals who were late adopters of the agile idea, labelling it a "manifesto" presumably helped get people's attention and suggested that radical change was needed.