!!! Overview[1]
[{$pagename}] are [Principals] to guide [Agile] Teams:
* Our highest priority is to satisfy the [customer] through early and [Continuous Delivery] of valuable [software|Applications].
* Welcome changing requirements, even late in [development|Programming]. [{$pagename}] 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.
* [{$pagename}] processes promote sustainable development. The [sponsors|Stakeholders], 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|Delivery Team].
* At regular intervals, the [Delivery Team] reflects on how to become more effective, then tunes and adjusts its behavior accordingly. ([Continuous Improvement])

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Principles behind the Agile Manifesto|http://agilemanifesto.org/principles.html|target='_blank'] - based on information obtained 2016-12-28-