Changes for page Agile Manifesto

Summary

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

Details

Page properties

Content

...	...	@@ -7,33 +7,20 @@
7	7	We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
8	8
9	9	* **Ind**ividuals and interactions over processes and tools
10		-
11		-{{info}}
12		-Ongoing human communication, teamwork, and collaboration are more important than strict adherence to processes such as workflows and guidelines, or software development and project management tools. Processes and tools should be flexible and enhance team productivity, not hinder it.
13		-{{/info}}
14		-
	10	+ * Comment: Ongoing human communication, teamwork, and collaboration are more important than strict adherence to processes such as workflows and guidelines, or software development and project management tools. Processes and tools should be flexible and enhance team productivity, not hinder it.
15	15	* **Wor**king software over comprehensive documentation
16		-
17		-{{info}}
18		-The primary goal is to deliver a working product. Developers should aim for enough documentation to understand and maintain the software, but avoid excessive detail that does not add value.
19		-{{/info}}
20		-
	12	+ * Comment: The primary goal is to deliver a working product. Developers should aim for enough documentation to understand and maintain the software, but avoid excessive detail that does not add value.
21	21	* **Cu**stomer collaboration over contract negotiation
22		-
23		-{{info}}
24		-Ongoing open communication with customers about the product is more important than relying strictly on the initial contract terms. Developers and customers should work together regularly to identify and address evolving requirements.
25		-{{/info}}
26		-
	14	+ * Comment: Ongoing open communication with customers about the product is more important than relying strictly on the initial contract terms. Developers and customers should work together regularly to identify and address evolving requirements.
27	27	* **Res**ponding to change over following a plan
	16	+ * Comment: Agile teams should expect changes, such as in requirements or technical aspects, and design the product to be flexible. They should be prepared to adapt it to customer needs, even if it means deviating from the original plan.
28	28
29		-{{info}}
30		-Agile teams should expect changes, such as in requirements or technical aspects, and design the product to be flexible. They should be prepared to adapt it to customer needs, even if it means deviating from the original plan.
31		-{{/info}}
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: "**Ind**ustrious **wor**ms **cu**ltivate **res**ilience."
	20	+### Mnemonic Bridge
36	36
	22	+**"Ind**ustrious **wor**ms **cu**ltivate **res**ilience."
	23	+
37	37	### The 12 Principle
38	38
39	39	Additionally, there are [twelve principles](https://agilemanifesto.org/principles.html) for further guidance.