Definition: The Agile Manifesto is a 2001 statement of values for building software in short, feedback-driven cycles instead of one long upfront plan. Written by 17 practitioners, it favors people, working results, customer collaboration, and adapting to change. Its 4 values and 12 principles now guide Scrum, Kanban, and project work far beyond code.
You are probably already doing a version of this. If you ship something small, show it to the people who will use it, listen, and adjust, you are working the way the manifesto describes. The document named that instinct and gave teams a shared language for it.
TL;DR: The Agile Manifesto (2001, 17 authors) sets 4 values and 12 principles that put working results and fast feedback ahead of rigid plans. It seeded Scrum and Kanban. Turn it into practice on a board view where work moves left to right. Build an agile board free.
What is the Agile Manifesto?
The Agile Manifesto is a short statement, signed in February 2001 by 17 software practitioners, that names 4 values and 12 principles for delivering software in small, frequent increments. It prizes individuals over process, working results over documents, collaboration over contracts, and responsiveness over rigid plans. The full text runs under 500 words.
The point of each value is balance, not rejection. The manifesto keeps process, documents, contracts, and plans. It says that when the two sides pull against each other, the left side wins. The right side still has value.
The manifesto seeded the methods most teams use today. Scrum added fixed sprints and roles, Kanban added a flow board with work limits, and Lean software development added waste-cutting ideas from manufacturing. Each interprets the same values differently.
The 4 values, in plain terms
The 4 values describe what to favor when you face a trade-off. Favor real conversations over handoffs through tools. Favor something that runs over a binder that describes it. Favor working alongside the customer over locking scope in a contract. Favor adjusting course over honoring a plan that reality has outgrown.
| Value (favored side) | Over | What it means in practice |
|---|---|---|
| Individuals and interactions | Processes and tools | Talk it out. A two-minute conversation beats a five-email thread. |
| Working software | Comprehensive documentation | Ship a thin slice users can try, then document what survives. |
| Customer collaboration | Contract negotiation | Bring the customer in early and often, not only at sign-off. |
| Responding to change | Following a plan | Re-plan when you learn something. The plan serves the goal. |
The 12 principles mapped to practice
The 12 principles expand the 4 values into working habits: deliver often, welcome change, keep a sustainable pace, reflect and adjust. They are the "how" behind the "what." Most map cleanly onto a recurring sprint and a board where work moves from idea to done.
| # | Principle (paraphrased) | What it looks like on a real team |
|---|---|---|
| 1 | Satisfy the customer with early, continuous delivery | Ship a usable slice in week one, not month six |
| 2 | Welcome changing requirements, even late | Re-order the backlog when priorities shift |
| 3 | Deliver working results frequently | Release every iteration, not once a quarter |
| 4 | Business and developers work together daily | Customer or owner is reachable, not a distant gatekeeper |
| 5 | Build around motivated people and trust them | Give the team the goal, not a step-by-step script |
| 6 | Favor face-to-face conversation | A quick daily check-in over status reports |
| 7 | Working software is the measure of progress | "Done" means usable, per the definition of done |
| 8 | Sustainable pace, indefinitely | Plan to capacity using story points, not heroics |
| 9 | Technical excellence and good design | Pair continuous integration with code review |
| 10 | Simplicity, the art of maximizing work not done | Cut the feature nobody asked for |
| 11 | Self-organizing teams produce the best work | The team pulls work; no one assigns every task |
| 12 | Reflect regularly and tune behavior | Run a retrospective and act on one fix per cycle |
A board is where these principles become visible. Work enters on the left, moves through stages, and exits on the right as something usable. The picture below shows a small slice mid-iteration.
BACKLOG IN PROGRESS REVIEW DONE
--------- ----------- ---------- ----------
Login page Search bar Profile edit Sign-up form
Export CSV [WIP limit: 2] Dark mode Email alerts
Team invites
Billing
| | | |
welcome sustainable working result measure of
change pace is the goal progress
Is the Agile Manifesto still relevant?
Yes. The manifesto stays relevant because its core idea, short cycles with real feedback, fits any field where requirements change faster than a yearly plan can keep up. Software teams still cite it, and marketing, operations, education, and event teams now borrow the same values to stay responsive to their customers.
The specifics of how teams apply it keep evolving. New agile metrics, tooling, and ceremonies come and go. The underlying philosophy, favor people, working results, collaboration, and adaptation, has held steady for more than two decades and continues to guide continuous improvement.
Related terms and concepts
- Scrum: An agile framework that organizes work into fixed sprints with defined roles and ceremonies.
- Kanban: A visual flow method that limits work in progress so tasks finish before new ones start.
- User stories: Short, plain-language descriptions of a feature written from the end user's point of view.
- Sprint backlog: The set of items a team commits to delivering in the current cycle.
- Continuous integration and continuous delivery: Practices that test and release code changes automatically and often.
Do it in Taskade: run an agile board
You don't need a process binder to work agile. You need one place where work moves from idea to shipped, and where everyone sees the same picture. In Taskade, describe the team and the work in plain English, and Taskade Genesis turns it into a live project you can run.
Use a board view as your agile pipeline. Each card is a work item. Columns are your stages, for example Backlog, In Progress, Review, and Done. The team drags a card right as it moves toward shipped, so progress is visible at a glance instead of buried in a status report. Switch the same data to a list view for planning or a calendar for deadlines without re-entering anything.
What runs on its own: an AI agent can sort new requests into the right column and draft a first description, and a reliable automation can move a card to Review when it is checked off, then ping the owner. Your stakeholders see the board update in real time. You see the work flow without chasing anyone.
That is the manifesto made concrete. Working results over documents, change welcomed by reordering cards, progress measured by what reaches Done. Open a board and start your first sprint free.
Frequently asked questions about the Agile Manifesto
What are the 4 values of the Agile Manifesto?
The 4 values are: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. Each favors the left side without discarding the right side, which still holds value.
How many principles does the Agile Manifesto have?
The Agile Manifesto has 12 principles. They expand the 4 values into working habits: deliver early and often, welcome changing requirements, keep a sustainable pace, favor face-to-face conversation, and reflect regularly to tune how the team works.
Who wrote the Agile Manifesto and when?
Seventeen software practitioners wrote the Agile Manifesto in February 2001 at a gathering in Snowbird, Utah. They came from different lightweight methods of the time and agreed on a shared set of values, which they published as a short public statement under 500 words.
What is the difference between Agile and Scrum?
Agile is a set of values and principles for delivering work in short, feedback-driven cycles. Scrum is one specific framework that implements those values with fixed sprints, defined roles, and ceremonies. Agile is the philosophy; Scrum is one way to practice it.
How can an organization adopt the Agile Manifesto?
Start small. Pick one team, run work in short iterations, and put every item on a shared board view so progress is visible. Hold a short daily check-in and a retrospective each cycle, then act on one improvement. Expand once the rhythm holds.
Can the Agile Manifesto be applied outside software?
Yes. Marketing, operations, education, and event teams use the same values wherever requirements change and fast feedback helps. The vocabulary stays the same: small increments, frequent delivery, close collaboration, and adapting the plan as you learn.