Value 1

Individuals and Interactions
Over Processes and Tools

The right set of people in a team and their interactions are the keys to success.

The best techniques available are of no value in the wrong hands.

Vector graphic of individuals talking and interacting.

Value 2

Working Software
Over Comprehensive Documentation

Don't spend hours making documentation before you write a single line of code.

Documentation is important, but prioritize the delivery of working software to your customers.

Vector graphic of two gears and hyper text markup language code.

Value 3

Customer Collaboration
Over Contract Negotiation

Customers and the development team are not adversaries.

Collaborate to chart the best way forward together. Establish a feedback loop for your customers to ensure that your product works for them.

Vector graphic of a client and customer talking and collaborating.

Value 4

Responding to Change
Over Following a Plan

A fixed environment and static road maps do not exist.

Needs and demands will vary, and goals continually change. Adapt and pivot if necessary.

Vector graphic of change, represented by geometric shapes, gears, and arrow paths pointing upwards.

Principle 1

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Vector graphic of the number 1 and icons representing a customer, code, and a heart.

Principle 2

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Vector graphic of the number 2 and change, represented by geometric shapes, gears, and a check mark.

Principle 3

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Vector graphic of the number 3 and icons representing code and a spinning gear containing a circular arrow.

Principle 4

Business people and developers must work together daily throughout the project.

Vector graphic of the number 4 and icons representing business people and software developers.

Principle 5

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Vector graphic of the number 5 and icons representing a rocket, projects, and motivated individuals.

Principle 6

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Vector graphic of the number 6 and icons representing face to face conversation between two individuals.

Principle 7

Working software is the primary measure of progress.

Vector graphic of the number 7 and icons representing code, software, and hardware with a working spinning gear.

Principle 8

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Vector graphic of the number 8 and icons representing development, a light bulb, communication, code, and repair.

Principle 9

Continuous attention to technical excellence and good design enhances agility.

Vector graphic of the number 9 and icons representing attention, a magnifying glass, and code.

Principle 10

Simplicity – the art of maximizing the amount of work not done – is essential.

Vector graphic of the number 10 and a check list on a clipboard.

Principle 11

The best architectures, requirements, and designs emerge from self-organizing teams.

Vector graphic of the number 11 and icons representing code and teams.

Principle 12

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Vector graphic of the number 12 and a team of 3 individuals communicating with each other.