Agile Values

What are Agile Values?

The agile values are the four preferences in the Agile Manifesto: individuals and interactions, working software, customer collaboration and responding to change, each favored over processes and tools, documentation, contracts and plans.

Updated November 2026 · 3 min read


The agile values are the four statements at the center of the Agile Manifesto, written in 2001: 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 one states a preference between two good things. The manifesto is explicit that the items on the right still have value; the items on the left are valued more when the two conflict.

The values are deliberately short and do not prescribe practices. They are a test for practices: a ceremony, tool or policy that pushes a team toward the right-hand side of every pair is working against agility, whatever it is called.

The four Agile values in practice

ValueWhat it looks likeWhat it does not mean
Individuals and interactions over processes and toolsTalking through a problem instead of filing tickets back and forth; choosing tools that fit how people workNo process or no tools
Working software over comprehensive documentationProgress shown through usable increments; documentation kept to what people will useNo documentation
Customer collaboration over contract negotiationCustomers involved in reviews and trade-offs throughoutNo contracts or agreed terms
Responding to change over following a planPlans revised regularly from evidenceNo planning

Individuals and interactions over processes and tools

Software is built by people solving problems together, and most delays come from misunderstandings and waiting, not from missing tools. Processes and tools should serve the team's collaboration. A useful check: when a process step exists mainly to protect someone from blame, it is probably on the wrong side of this value.

Working software over comprehensive documentation

Documents describe intent; working software shows whether the intent was right. Agile teams prefer to show progress through something people can use. They still write documentation, but choose it for its audience: API references, operational runbooks and decision records tend to be worth keeping, while long specifications written months before building often are not.

Customer collaboration over contract negotiation

A contract defines a relationship; collaboration makes it work. Instead of treating every change as a dispute over scope, agile teams involve customers in regular reviews and make trade-offs together. Contracts can support this, for example by fixing budget and time while leaving detailed scope to be agreed each iteration.

Responding to change over following a plan

Plans are made with the least information a team will ever have. Agile teams plan continuously, at several levels, and expect to change those plans as they learn. A plan is still valuable as a statement of current intent and as a way to see the impact of a change.

An example

Consider a hypothetical internal IT team building an expense tool for a finance department. The original plan requires a 60-page specification, sign-off and a single release after six months. Applying the agile values, the team instead meets with three finance staff for an hour each week (customer collaboration), releases a minimal version that handles the most common claim type in week four (working software) and replaces the sign-off gate with a short shared page of business rules that developers and finance staff update together after each conversation (individuals and interactions, and lighter documentation).

In week six, finance learns of a new tax rule affecting mileage claims. Under the original plan this would have been a formal change request. Here, the product owner moves the mileage rule to the top of the backlog and it ships two weeks later (responding to change). The plan still exists; it is just updated every two weeks instead of defended for six months.

Common misreadings

  • Treating the values as either/or. The right-hand items remain useful. The values guide which way to lean.
  • Using the values to avoid accountability. "We respond to change" is not a reason to miss every commitment.
  • Applying them only in delivery teams. Budgeting, governance and vendor management can follow the same values.
  • Confusing values with practices. Sprints, standups and boards are ways of acting on the values, not the values themselves.

The agile values are expanded in the twelve agile principles, underpin the agile mindset and are applied day to day through frameworks such as Scrum.

Frequently asked questions

Do the agile values mean teams should not plan or write contracts?

No. Each agile value states a preference between two useful things, and the manifesto says the items on the right, such as plans, documentation, contracts and tools, still have value. Agile teams plan continuously, sign contracts and write documentation people will use. The values guide which way to lean when the two sides conflict, not which side to abandon.

How can teams apply the agile values in daily work?

Talk problems through instead of passing tickets back and forth, show progress with usable increments, involve customers in regular reviews and trade-offs, and revise plans from evidence every few weeks. The values also work as a test for practices: a process step that mainly exists to protect someone from blame is probably working against them.

Can the agile values apply outside software delivery teams?

Yes. Although written for software, the agile values can guide budgeting, governance and vendor management as well as delivery. A contract can fix budget and time while leaving detailed scope to be agreed each iteration, and governance can rely on frequent reviews of real results instead of large sign-off gates. The values describe priorities, not software practices.