Changes for page Agile Manifesto

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -32,6 +32,20 @@
32	32
33	33	That is, while there is value in the items on the right, we value the items on the left more.
34	34
35		-### Mnemonic Bridge
	35	+Mnemonic Bridge: "**Ind**ustrious **wor**ms **cu**ltivate **res**ilience."
36	36
37		-"**Ind**ustrious **wor**ms **cu**ltivate **res**ilience."
	37	+### The 12 Principle
	38	+
	39	+Additionally, there are [twelve principles](https://agilemanifesto.org/principles.html) for further guidance:
	40	+
	41	+* Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
	42	+* Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
	43	+* Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
	44	+* Business people and developers must work together daily throughout the project.
	45	+* Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
	46	+* The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
	47	+* Working software is the primary measure of progress.
	48	+* Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
	49	+* Continuous attention to technical excellence and good design enhances agility. Simplicity, the art of maximizing the amount of work not done, is essential.
	50	+* The best architectures, requirements, and designs emerge from self-organizing teams.
	51	+* At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.