The Agile Manifesto Explained: 4 Values and 12 Principles in Practice

Every Agile framework, from Scrum to Kanban to SAFe, traces back to a short document written in February 2001 by seventeen software practitioners who met at a ski lodge in Utah. The Agile Manifesto is only 68 words long, yet people still argue about what it means. If you want to work as a Scrum Master, you need to understand it well enough to explain it to a sceptical manager and to apply it when the rules of a framework do not give you an answer.

This lesson walks through the four values and twelve principles, translates each into everyday team behaviour, and points out the most common ways teams misread them. If you are brand new to the topic, start with What Is Agile? A Simple Introduction for Beginners and come back here.

Why the Manifesto Was Written

In the 1990s most software projects followed heavyweight, plan-driven processes. Requirements were written up front, signed off, handed to designers, then developers, then testers. By the time customers saw working software, months or years had passed and their needs had changed. Projects failed not because people were lazy but because the process assumed that the future could be predicted in detail.

The authors came from different backgrounds (Scrum, Extreme Programming, DSDM, Crystal and others) but agreed on a few shared beliefs. They did not reject planning or documentation. They argued that, when forced to choose, some things matter more than others.

The Four Values

The Manifesto is written as four "over" statements. The authors added that while there is value in the items on the right, they value the items on the left more.

1. Individuals and interactions over processes and tools

Good teams with a simple process beat poor teams with a perfect process. In practice this means face-to-face (or video) conversation before long email chains, a team that sits together or has strong working agreements, and tools that serve the team rather than the other way round. A Jira workflow with fourteen statuses is a classic sign that the tool has started to drive behaviour.

2. Working software over comprehensive documentation

The real measure of progress is something users can run, not a document that describes something they might run one day. This does not mean "no documentation". It means documenting what is useful: an API reference, a runbook, an architecture decision record. A 200-page requirements specification that nobody reads is waste. A one-page decision log that new joiners rely on is value.

3. Customer collaboration over contract negotiation

Contracts matter, but a relationship in which customer and supplier work together on the problem produces better outcomes than one in which each side defends its paper position. In Scrum, this value shows up in the Sprint Review, where stakeholders inspect the Increment and discuss what to do next, and in the working relationship between the Product Owner and the Developers. See Sprint Review Explained for how that conversation should run.

4. Responding to change over following a plan

Plans are useful for thinking, but a plan that cannot change is a liability. Agile teams plan continuously and in short horizons, and they treat new information as an opportunity. If a competitor launches a feature or user research disproves an assumption, the team adjusts the Product Backlog rather than defending last quarter's roadmap.

Common misreading: "Agile means no documentation, no planning and no contracts." The Manifesto never says that. It says one side is valued more, not that the other side has zero value.

The Twelve Principles

The principles behind the Manifesto add detail. Rather than reciting them, it helps to group them into four themes.

Theme 1: Deliver value early and often

  • Satisfy the customer through early and continuous delivery. Ship small slices of value frequently so feedback arrives while it is still cheap to act on.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale. This is the origin of the Sprint.
  • Working software is the primary measure of progress. Percent-complete charts and status reports are secondary signals.

Theme 2: Welcome change and keep the pace sustainable

  • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  • Promote sustainable development. Sponsors, developers and users should be able to maintain a constant pace indefinitely. Chronic overtime is a signal that something upstream is broken.
  • Simplicity, the art of maximising the amount of work not done, is essential. The best feature is often the one you decide not to build.

Theme 3: People and collaboration

  • Business people and developers must work together daily. Weekly hand-offs are too slow.
  • 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 is face-to-face conversation. In a distributed team, read this as "rich, real-time communication".
  • The best architectures, requirements and designs emerge from self-organising teams. This is why Scrum has no project manager role inside the team.

Theme 4: Excellence and reflection

  • Continuous attention to technical excellence and good design enhances agility. Skipping tests and refactoring may feel fast today and slows every later Sprint.
  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour. This is the Sprint Retrospective, covered in Sprint Retrospective Explained.

How the Manifesto Maps to Scrum

Manifesto ideaWhere you see it in Scrum
Early and continuous deliveryEvery Sprint produces a usable Increment
Welcome changing requirementsThe Product Backlog is ordered and refined continuously
Self-organising teamsDevelopers decide how to turn Product Backlog items into an Increment
Reflect and adjustSprint Retrospective at the end of every Sprint
Customer collaborationSprint Review and ongoing Product Owner involvement
Technical excellenceThe Definition of Done as a quality commitment

Three Ways Teams Misuse the Manifesto

  1. Using it as an excuse. "We are Agile, so we do not need to estimate, plan or write anything down." That is not Agile; that is chaos with stand-ups.
  2. Treating it as a rulebook. The Manifesto is a statement of values, not a process. Frameworks such as Scrum give you the process; the Manifesto helps you decide what to do when the framework is silent.
  3. Doing the ceremonies without the mindset. A team can hold every Scrum event and still behave like a waterfall team with shorter phases. If people never change the plan, never talk to users and never improve their process, the values are missing.

How a Scrum Master Uses the Manifesto

When a team argues about a process question (for example, "should we write a detailed spec before building?"), the Manifesto offers a useful tie-breaker: what would help us deliver working software and collaborate better right now? As a Scrum Master you will use it in three ways:

  • Coaching: asking questions such as "which of the four values is this practice supporting?"
  • Stakeholder conversations: explaining why a fixed scope and date commitment made months in advance is risky, using the language of the values.
  • Self-checks: noticing when your own behaviour (for example, assigning tasks or demanding status reports) cuts against the principles.

Frequently Asked Questions

Is the Agile Manifesto the same as Scrum?

No. The Manifesto is a set of values and principles; Scrum is a specific framework that is consistent with them. Kanban, Extreme Programming and other approaches are also consistent with the Manifesto. See Agile Methodologies Compared.

Is the Manifesto outdated?

The wording reflects its time, with its focus on software, but the underlying ideas about feedback, people and adaptation are still widely used well beyond IT. Teams in marketing, HR and operations adapt the same ideas, as discussed in Scrum Beyond Software.

Do I need to memorise the twelve principles for an exam?

For Scrum certifications, you need to understand the intent more than the exact wording. For interviews, being able to explain the four values with a real example from your own experience is far more convincing than reciting the list.

Key takeaways
  • The Manifesto has four values and twelve principles; it is a mindset, not a method.
  • Both sides of each "over" statement have value, but the left side is valued more.
  • Scrum is one way to apply the values; the values help when the framework runs out of answers.
  • Ceremonies without the mindset do not make a team Agile.

Related Lessons