Changes for page Agile Manifesto

Summary

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

Details

Page properties

Content

...	...	@@ -9,11 +9,11 @@
9	9	* **Ind**ividuals and interactions over processes and tools
10	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.
11	11	* **Wor**king software over comprehensive documentation
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.
	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 adds no value and is often quickly outdated.
13	13	* **Cu**stomer collaboration over contract negotiation
14	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.
15	15	* **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.
	16	+ * Comment: Agile teams should expect changes, such as in requirements or technical aspects, and design the source code to be flexible. They should be prepared to adapt it to customer needs, even if it means deviating from the original plan.
17	17
18	18	That is, while there is value in the items on the right, we value the items on the left more.
19	19