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.
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.
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.
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.
Principle 1
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Principle 2
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Principle 3
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Principle 4
Business people and developers must work together daily throughout the project.
Principle 5
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Principle 6
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Principle 7
Working software is the primary measure of progress.
Principle 8
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Principle 9
Continuous attention to technical excellence and good design enhances agility.
Principle 10
Simplicity – the art of maximizing the amount of work not done – is essential.
Principle 11
The best architectures, requirements, and designs emerge from self-organizing teams.
Principle 12
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.