Twelve Principles

Behind the
Agile Manifesto
The 12 Principles are based on the Agile Manifesto—a document published in
2001 by a bunch of engineers who were working with various lightweight software
methodologies. These guiding principles will help you implement and execute with
agility. Visit the Interaction Design Foundation to learn more.

01 02
Our highest priority is to satisfy the Welcome changing requirements, even late in
customer through early and continuous development. Agile processes harness change
delivery of valuable software. for the customer’s competitive advantage.

03 04
Deliver working software frequently, from Business people and developers must work
a couple of weeks to a couple of months, together daily throughout the project.
with a preference to the shorter timescale.

05 06
Build projects around motivated The most efficient and effective
individuals. Give them the environment method of conveying information to
and support they need, and trust them and within a development team is
to get the job done. face-to-face conversation.

07 08
Working software is the primary measure Agile processes promote sustainable
of progress. development. The sponsors, developers,
and users should be able to maintain a
constant pace indefinitely.

09 10
Continuous attention to technical excellence Simplicity—the art of maximizing the
and good design enhances agility. amount of work not done—is essential.

11 12
The best architectures, requirements, and At regular intervals, the team reflects on
designs emerge from self-organizing teams. how to become more effective, then tunes
and adjusts its behavior accordingly.

Start Learning Today:

interaction-design.org
Creative Commons BY-SA license: You are free to edit and redistribute this template, even for commercial use, as long as you give credit to the
Interaction Design Foundation. Also, if you remix, transform, or build upon this template, you must distribute it under the same CC BY-SA license.
Twelve Principles
Behind the
Agile Manifesto
The 12 Principles are based on the Agile Manifesto—a document published in
2001 by a bunch of engineers who were working with various lightweight software
methodologies. These guiding principles will help you implement and execute with
agility. Visit the Interaction Design Foundation to learn more.

01 02
Our highest priority is to satisfy the Welcome changing requirements, even late in
customer through early and continuous development. Agile processes harness change
delivery of valuable software. for the customer’s competitive advantage.

03 04
Deliver working software frequently, from Business people and developers must work
a couple of weeks to a couple of months, together daily throughout the project.
with a preference to the shorter timescale.

05 06
Build projects around motivated The most efficient and effective
individuals. Give them the environment method of conveying information to
and support they need, and trust them and within a development team is
to get the job done. face-to-face conversation.

07 08
Working software is the primary measure Agile processes promote sustainable
of progress. development. The sponsors, developers,
and users should be able to maintain a
constant pace indefinitely.

09 10
Continuous attention to technical excellence Simplicity—the art of maximizing the
and good design enhances agility. amount of work not done—is essential.

11 12
The best architectures, requirements, and At regular intervals, the team reflects on
designs emerge from self-organizing teams. how to become more effective, then tunes
and adjusts its behavior accordingly.

Start Learning Today:

interaction-design.org
Creative Commons BY-SA license: You are free to edit and redistribute this template, even for commercial use, as long as you give credit to the
Interaction Design Foundation. Also, if you remix, transform, or build upon this template, you must distribute it under the same CC BY-SA license.