Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 29 ยท Agile Basics

The Agile Manifesto and Principles

Understand the four values and twelve principles of the Agile Manifesto in plain words, the common misreadings, and how they show up in team habits.

In February 2001, seventeen software practitioners met at a ski resort in Utah. They used different methods and did not agree on everything, but they agreed that many projects were failing because of heavy process and too little contact with real users. They wrote a short statement called the Agile Manifesto, together with twelve supporting principles. Almost every Agile method you will meet in this tutorial, including Scrum, Kanban and XP, traces back to those few lines.

The manifesto is not a process, a certification or a checklist. It is a statement of priorities, and it is meant to be argued with in real situations. This lesson explains the four values and the twelve principles in plain words, clears up the most common misreadings, and shows what the values look like in a team's daily habits. For the problem the manifesto responds to, see What Is Agile?.

The four values

The manifesto is built around four pairs. In each pair, the authors say that the item on the left is valued more than the item on the right, while admitting the item on the right still has value.

Four values, left over right

People over process Individuals and interactions over processes and tools.
Software over documents Working software over comprehensive documentation.
Partners over contracts Customer collaboration over contract negotiation.
Change over plans Responding to change over following a plan.

The items on the right still matter. The left ones matter more.

1 / 2

Individuals and interactions over processes and tools

Software is made by people talking, deciding and sometimes disagreeing. A good process helps them, but a team that follows a perfect process while avoiding honest conversation will still build the wrong thing. Likewise, a tool does not create collaboration: a team with a sophisticated issue tracker and no trust will still fail. The value says: when the process and the people clash, fix the process.

Working software over comprehensive documentation

The only proof that a product works is that it works. Long specifications can drift out of date, and nobody can use a document to solve a customer's problem. Notice the word comprehensive: the value does not say "no documentation". It says that producing a complete document must not displace producing something that runs. Good Agile teams write the documentation that others genuinely need, such as an API reference, a setup guide or a short design note, and keep it current.

Customer collaboration over contract negotiation

A contract can say what was agreed last year, but it cannot tell you what the customer needs this week. Agile teams treat customers and users as partners who give regular feedback and help set priorities, instead of an opponent to be kept to the letter of an agreement. Contracts still exist, and can be structured to support this (for example, with payment tied to delivered slices, or to a fixed time budget with changing scope).

Responding to change over following a plan

A plan is a tool for thinking, not a promise from the future. When you learn something new, such as a competitor's move or a user who rejects your feature, the team should be able to change direction without a crisis. This does not mean making no plans: it means that a plan that no longer matches reality should be updated.

The twelve principles in plain words

The twelve principles turn the values into guidance. Here they are in the order the manifesto lists them, in our own words, grouped afterward by theme.

  1. Make customers happy by delivering useful software early and continually.
  2. Welcome new requirements, even late, because they can give the customer an advantage.
  3. Deliver working software often, every few weeks, favoring the shorter time scale.
  4. Business people and developers work together every day.
  5. Build around motivated individuals, give them what they need, and trust them.
  6. Face-to-face conversation is the most effective way to exchange information (for distributed teams this means live video or voice, not long email threads).
  7. Working software is the main measure of progress.
  8. Keep a sustainable pace that sponsors, developers and users could maintain indefinitely.
  9. Continuous attention to technical excellence and good design improves agility.
  10. Simplicity, the art of maximizing the amount of work not done, is essential.
  11. The best architectures, requirements and designs come from self-organizing teams.
  12. At regular intervals the team reflects on how to be more effective, then adjusts.

You can see four themes: customers and value (1, 2, 4), frequent delivery (3, 7, 12), people and teams (5, 6, 8, 11) and craft and simplicity (9, 10). The explorer below stores a short paraphrase of each principle and lets you filter by theme or search by word. It is a small data example, not part of any real tool.

JS Principles explorer

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The search for "work" returns many results because it also matches "working" and "works", which have different meanings in different principles. That is a reminder that keyword matching is crude; the themes are a better way to explore the principles.

Common misreadings

The manifesto is short, so people read their own preferences into it. Watch out for these:

  • "Agile means no documentation." The value contrasts working software with comprehensive documentation. It asks for the useful kind.
  • "Agile means no plan." Plans are made and updated all the time, in shorter horizons. The value is about not clinging to a plan after reality disagrees with it.
  • "The right-hand items are worthless." The manifesto says explicitly that there is value in them. A team that skips every process and every contract is not more Agile, only more chaotic.
  • "Agile means developers decide everything." Self-organization is about how the team does its work. Priorities still come from customer value and the business, and the team works with those people daily.
  • "Faster is more Agile." Principle 8 asks for a sustainable pace. Responding to change quickly is different from working overtime.
  • "Following Scrum correctly makes you Agile." Methods can be used mechanically. A team can hold every Scrum meeting and still ignore the values.

The values are phrased as trade-offs, which makes them good for decisions. When you are unsure what to do, ask: "Does this choice help people talk, deliver something that works, work with the customer, and adapt to what we learn?" If it does the opposite, you have probably found an anti-pattern.

How the values show up in daily habits

A value is only real when it changes what a team does on an ordinary Tuesday. Some examples:

  • People over process: when a question is unclear, someone walks over (or starts a short call) instead of writing a long ticket comment. The team can change its own working agreement when it is not working.
  • Working software over documentation: each iteration ends with a demo of something that runs. Design notes are short, live next to the code, and are updated with the code.
  • Customer collaboration: a real user or a person who speaks for users attends reviews and answers questions during the iteration, not only at the end.
  • Responding to change: the backlog is re-ordered regularly. A change request is discussed in terms of value and trade-offs, not blame.

The model below turns this into a simple self-check. Each practice is tagged with the value it relates to and whether it leans toward the left side (what the manifesto prefers) or the right side. It counts the habits for and against each value and names the weakest area. It is a conversation starter for a retrospective, not a measurement of "how Agile" a team is.

JS Check team habits against the values

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Try adding a practice from your own team and see which value moves. The stand-in only counts; a real discussion would ask why a habit exists and whether it still earns its place.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What does the Agile Manifesto say about the items on the right-hand side of each value, such as processes and documentation?

    The manifesto acknowledges that there is value in the right-hand items, yet it values the left-hand items more.
  2. 2. Which principle asks for a pace that teams could keep up for a long time?

    Sustainable pace means sponsors, developers and users should be able to maintain the rhythm indefinitely. Overtime is not a path to agility.
  3. 3. A manager says, 'We are Agile, so we do not need any plan or documentation.' What is the best reply?

    The values contrast working software with comprehensive documentation and responding to change with following a plan. They do not remove planning or documentation.
  4. 4. Which habit best reflects 'customer collaboration over contract negotiation'?

    Regular conversation with the people who use the product keeps the work aligned with real needs.
  5. 5. Which statement is a misreading of the manifesto?

    A team can follow Scrum's mechanics and still ignore the values. Agility is about the mindset and outcomes, not only the meetings.

Summary

  • The Agile Manifesto (2001) states four values: people and interactions, working software, customer collaboration and responding to change, each valued over a counterpart that still has worth.
  • Twelve principles turn the values into guidance on delivery, collaboration, trust, sustainable pace, quality and regular reflection.
  • Common misreadings include "no documentation", "no planning" and "developers decide everything".
  • The values show up in daily habits: short conversations, demos of working software, customers in reviews, and a backlog that is reordered as you learn.
  • Use the values as a decision aid and a retrospective topic, not as a score.

Next, see how the ideas become concrete working methods in Scrum, Kanban, XP and Lean Compared.