The Agile Manifesto is a document that sets out the key values and principles behind the Agile philosophy and serves to help development teams work more efficiently and sustainably.
Known officially as ‘The Manifesto for Agile Software Development’, the manifesto detailing 4 Values and 12 Principles.
Acting as a proclamation, it is designed to improve software development methodologies, and directly responds to the inefficiency of traditional development processes. Namely, their reliance on weighty documentation and opportunity for oversight.
While the original document specifically set out to help software developers build business solutions in a faster and more efficient way, it has had a huge impact on the wider development industry and beyond.
Today, groups as diverse as PR and marketing departments, coders, restaurateurs, and even The Boy Scouts of America use the manifesto in one way or another, and its influence only continues to expand.
Learn how to prioritize by making it a simple process, to build products that stand out. Learn more about how to source insight, choose the right prioritization framework and much more.
So, what are the core values and principles of the Agile Manifesto?
Let’s break it down...
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
The highest priority is to satisfy the customer through early, and continuous, delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Clients and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The most efficient and effective method of conveying information to, and within a development team, is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development — the sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity — the art of maximizing the amount of work not done — is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Although various agile principles have been around since the 1970s, the manifesto itself — and the full definition of the agile philosophy — was created at the dawn of the new millennium.
In early 2001, a group of 17 developers held two meetings — the first in Oregon, the second in Snowbird, Utah — to discuss issues and solutions in software development, which is how the manifesto was firstborn.
Put simply, the manifesto was written as a response to major frustration with the traditional development processes of the 1990s.
The explosion of personal computing meant that product and software development had undergone significant changes, and developers at the meetings — and indeed, across the wider industry — felt that the status quo was no longer working.
The lag time between business needs and solutions being developed as an average of three years, and the standard processes at this point were unwieldy, unsatisfactory and overburdened with documentation and oversight.
The 17 developers who met in Oregon and Utah named themselves ‘The Agile Alliance’, and proposed a new way of working based around a set of values and principles that would “restore credibility to the word ‘methodology’”.
The manifesto was designed to empower developers, to speed up processes and to help encourage working practices that focus more directly on the user.
The values and principles allow teams to be adaptive, to respond quickly and effectively to change, and to be in a state of constant reimagination underpinned by frequent customer feedback.
Published in February 2001, the manifesto has since formed the basis of a vast array of frameworks, methodologies and different ways of working.
The original signatories to the Agile Manifesto were a group of 17 developers, scientists, programmers and authors who came together to find a solution to the perceived ills of the software development industry.
Agile philosophy pre-dated the Agile Manifesto, and the group included a number of inventors and creators of earlier agile frameworks. Kent Back of extreme programming, Jim Highsmith of adaptive software development, and Jeff Sutherland of scrum, to name a few.
The full list of signatories is:
Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, and Dave Thomas.
The beauty of the Agile Manifesto is that despite changes the industry has seen, despite the passage of time, and despite the fact that it has been applied to sectors and organizations far and beyond its original scope — the manifesto’s flexibility and adaptive nature mean that it continues to be relevant today.
Agile is a mentality — a philosophy — and the manifesto sets out principles and values, rather than prescribing certain processes. This means that plenty of developers work with an agile mindset without even realizing it. The manifesto merely formalizes how many successful teams have always worked.
The real problem with the manifesto today is not whether it is relevant, but how it is applied — or rather how it is applied incorrectly.
In part due to its flexibility, one of the biggest problems with agile is that some teams describe themselves as such without properly applying or understanding the underlying principles.
Plenty of ‘agile’ teams, for example, sometimes use the manifesto as an ‘excuse’ to abandon traditional development processes and to reject rigor, without ever really considering the fundamentals behind an agile mindset.
When used correctly, though, the manifesto remains as relevant today as it did when it was written, and can be a hugely valuable tool for developers, teams and even entire organizations.