Agile Manifesto - Four Values

We are uncovering better ways of developing software by doing it and helping others do it.

1. Individuals and Interactions over Processes and Tools

Projects are about people, not just tools or processes.

Example: Instead of relying solely on project management tools like Microsoft Project, teams should encourage direct communication between developers and stakeholders.

2. Working Software over Comprehensive Documentation

The primary objective is to deliver functional software rather than spending excessive time on documentation.

Example: A user-friendly application that is intuitive and requires minimal documentation is preferred over a complex system with an extensive user manual.

3. Customer Collaboration over Contract Negotiation

Engage with customers regularly and be open to changes instead of strictly following a contract.

Example: A client requests a new feature mid-project. Instead of rejecting it due to contract limitations, Agile teams welcome discussions and adjustments to improve the final product.

4. Responding to Change over Following a Plan

Be adaptable and willing to change plans based on new insights.

Example: If user feedback suggests a better way to implement a feature, an Agile team will adjust the development approach rather than rigidly sticking to the original plan.

Conclusion

While the items on the right (Processes and Tools, Comprehensive Documentation, Contract Negotiation, Following a Plan) are important, Agile values the items on the left more.