Agile Principles
What are Agile Principles?
The agile principles are twelve statements published alongside the Agile Manifesto in 2001 that turn its four values into practice, covering early delivery, welcoming change, daily collaboration, sustainable pace and reflection.
Updated November 2026 · 3 min read
The agile principles are the twelve statements published with the Agile Manifesto in 2001 that describe how agile teams work: deliver valuable results early and often, welcome change, collaborate daily with the business, trust motivated people, keep a sustainable pace, pay attention to technical quality, keep things simple and reflect regularly on how to improve. Where the manifesto's four values say what to prioritize, the principles say what that looks like in practice.
They were written for software teams, and the text refers to "working software" throughout. Most of them apply to any team that produces something usable in increments, which is why marketing, operations and HR teams have adapted them.
The twelve Agile principles, grouped by theme
| Theme | Principles (summarized) | What it means in practice |
|---|---|---|
| Customer value | 1. Satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late. | Release in small increments; treat new information as useful, not disruptive. |
| Frequent delivery | 3. Deliver working software frequently, from a couple of weeks to a couple of months, preferring shorter. 7. Working software is the primary measure of progress. | Judge progress by usable results, not documents or percent complete. |
| Collaboration | 4. Business people and developers work together daily. 6. Face-to-face conversation is the most efficient way to share information. | Keep the people who know the need close to the people doing the work. |
| People and pace | 5. Build projects around motivated individuals and trust them. 8. Promote sustainable development at a constant pace. | Give teams support and autonomy; avoid crunch as a planning tool. |
| Quality and simplicity | 9. Continuous attention to technical excellence and good design. 10. Simplicity, maximizing the amount of work not done, is essential. | Build quality in; do not build what is not needed. |
| Self-organization and improvement | 11. The best architectures, requirements and designs emerge from self-organizing teams. 12. At regular intervals the team reflects and adjusts. | Let teams shape their own approach; hold regular retrospectives. |
How the principles read today
- Delivery frequency has moved on. "A couple of weeks to a couple of months" was ambitious in 2001. Teams using continuous delivery now release many times a day, which is the principle taken further.
- Face-to-face has widened. Distributed teams interpret principle 6 as favoring rich, synchronous conversation, including video calls, over long written handoffs.
- "Done" includes outcomes. Many product teams now read principle 7 alongside outcome measures: working software that nobody uses is not much progress.
- Sustainable pace is a delivery issue. Teams that work overtime to meet every sprint commitment build up defects and turnover that slow them later.
Applying the principles outside software
Replace "working software" with the team's real output. For a recruiting team, it might be a filled role; for a finance team, a closed month or a usable forecast; for marketing, a live campaign with results. The questions stay the same: can we deliver a usable piece sooner, are the people we serve involved often, and do we regularly change how we work based on what we learn?
An example
Consider a hypothetical data team that has spent five months building a customer analytics dashboard with 40 charts. It is still not released, because two data sources are not yet integrated.
Reviewing the work against the principles, the team sees it has missed several: no early delivery (1, 3), no regular contact with the sales leaders who will use it (4) and a lot of work that may not be needed (10). It ships the 8 charts that rely only on finished data sources to sales leaders the following week and sets up a 30-minute review with them every two weeks. Usage data after a month shows that 5 of the 8 charts are viewed weekly and 3 almost never. The team removes those 3 and deprioritizes 12 similar charts in the backlog, cutting the remaining 32 charts of build work by more than a third.
Common pitfalls
- Cherry-picking. Teams often adopt "welcome changing requirements" and skip "technical excellence," which makes frequent change expensive.
- Reading principles as rules. They guide judgment. Some contexts, such as safety-critical systems, need more documentation and formal review than others.
- Ignoring principle 12. Without regular reflection and change, teams stop improving after the initial adoption.
- Applying them only to delivery teams. Principles about trust, simplicity and collaboration apply equally to how leaders plan and fund work.
The agile principles sit alongside the agile values and are put into practice through frameworks such as Scrum. The reflection in principle 12 is formalized in the sprint retrospective.
Frequently asked questions
What is the difference between agile values and agile principles?
The four agile values in the Agile Manifesto say what to prioritize, such as working software over comprehensive documentation. The twelve agile principles, published alongside them in 2001, describe what those priorities look like in practice: early and frequent delivery, welcoming change, daily collaboration, sustainable pace, technical excellence, simplicity and regular reflection.
Can the agile principles be applied outside software development?
Yes. Teams outside software replace working software with their own usable output, such as a filled role for recruiting, a closed month or forecast for finance or a live campaign for marketing. The questions stay the same: can a usable piece be delivered sooner, are the people being served involved often, and does the team change how it works based on what it learns?
Which agile principles do teams most often ignore?
Teams often cherry-pick, adopting welcoming changing requirements while skipping continuous attention to technical excellence, which makes frequent change expensive. Principle 12, regular reflection and adjustment, is also frequently dropped after the first adoption, so improvement stalls. Sustainable pace gets ignored when teams work overtime to meet every sprint commitment, building up defects and turnover that slow them later.
Related terms
Agile Manifesto
The 2001 founding statement of agile's four values and twelve principles.
Continuous Delivery (CD)
Keeping software always releasable so any change can ship on demand.
Agile Values
Four paired preferences at the heart of the Agile Manifesto.
Scrum
An agile framework of short Sprints, three roles and regular inspection.