The Twelve Principles

While the four values are philosophical, the twelve principles are more practical. They help answer "what should we do?" when you're unsure.

We'll group them into themes to make them easier to remember and apply.

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

Value delivered beats value planned. Ship something useful now, not something perfect in six months.

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

Shorter feedback loops mean faster learning. Two weeks is better than two months.

3. "Working software is the primary measure of progress."

Story points completed, documents signed off, meetings held—none of these are progress. Only working software counts.

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

Change isn't the enemy—it's information. A competitor launching a new feature is an opportunity to pivot, not a disaster.

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

Handoffs create delays and misunderstandings. Continuous collaboration beats handoff documents.

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

Micromanagement kills motivation. Hire good people and get out of their way.

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

Teams closest to the work make the best decisions about the work. Don't mandate solutions from above.

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

Continuous improvement isn't optional. Without reflection, you're just repeating the same mistakes.

9. "Continuous attention to technical excellence and good design enhances agility."

Speed without quality creates technical debt. Technical debt slows you down. Therefore, quality enables speed.

10. "Simplicity—the art of maximizing the amount of work not done—is essential."

Every feature has ongoing maintenance cost. Build only what's needed. YAGNI (You Ain't Gonna Need It) is a feature, not a bug.

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

Written communication loses nuance. When possible, talk. When distributed, video beats audio beats text.

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

Crunch is not a strategy. Sustainable pace produces better software over time than heroics followed by burnout.