Differences

This shows you the differences between two versions of the page.

--- agile_values_and_principles [2017/01/20 11:58] – hpsamios
+++ agile_values_and_principles [2020/06/02 14:21] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 ====== Values ======
-Individuals and interactions over processes and tools
+The [[http://agilemanifesto.org|Values]] are:
-Working software over comprehensive documentation
-Customer collaboration over contract negotiation
+  * Individuals and interactions over processes and tools
-Responding to change over following a plan
+  * Working software over comprehensive documentation
+  * Customer collaboration over contract negotiation
+  * Responding to change over following a plan
 ====== Principles ======
-Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
+The [[http://agilemanifesto.org/principles.html|Principles]] are:
-Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
-Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
-Business people and developers must work together daily throughout the project.
-Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
-The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
-Working software is the primary measure of progress.
-Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
-Continuous attention to technical excellence and good design enhances agility.
-Simplicity--the art of maximizing the amount of work not done--is essential.
+  * Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
+  * Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
+  * Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
+  * Business people and developers must work together daily throughout the project.
+  * Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
+  * The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
+  * Working software is the primary measure of progress.
+  * Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
+  * Continuous attention to technical excellence and good design enhances agility.
+  * Simplicity--the art of maximizing the amount of work not done--is essential.
+  * The best architectures, requirements, and designs emerge from self-organizing teams.
+  * At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
-The best architectures, requirements, and designs emerge from self-organizing teams.
+====== Want to Know More? ======
-At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
+  * [[http://agilemanifesto.org|Agile Manifesto]]
+  * [[http://agilemanifesto.org/principles.html|Principles Behind the Manifesto]]
+  * [[http://agilemanifesto.org/authors.html|Authors of the Manifesto]]
+  * [[http://agilemanifesto.org/history.html|History of the Manifesto]]
+  * Book [[https://www.infoq.com/minibooks/agile-values-principles/|Understanding Agile Values & Principles. An Examination of the Agile Manifesto]] - By Scott Duncan
-{{tag>Learning Reference Basics FirstSprint Values Principles Agile}}
+{{tag>Learning Reference Basics Values Principles Agile}}
-~~LINKBACK~~
-~~DISCUSSION~~