Agile Manifesto

A group of software experts wrote the Agile Manifesto in 2001. They wanted a better way to build software. The manifesto lists four values that guide every Agile team today.

The Four Values

Each value compares two things. Agile teams prefer the first item more, but they still respect the second item.

Value 1: Individuals and Interactions over Processes and Tools

People solve problems better through conversation than through rigid steps in a manual. A quick chat between two team members often fixes an issue faster than following a strict checklist.

Value 2: Working Software over Comprehensive Documentation

A product that actually works matters more than a perfect document describing it. Teams still write documents, but they keep them short and useful.

Value 3: Customer Collaboration over Contract Negotiation

Agile teams talk to customers throughout the project. They do not lock requirements into a fixed contract and ignore the customer until the end.

Value 4: Responding to Change over Following a Plan

Plans help teams start a project, but markets and customer needs shift over time. Agile teams adjust their plan instead of forcing the original plan to work.

Simple Diagram of the Values

People        > Process and Tools
Working item  > Heavy documentation
Collaboration > Contract terms
Change        > Fixed plan

Layman's Example

Think about planning a road trip. A rigid traveler follows the original map even when a road gets closed. An Agile traveler checks the road condition, talks to a local guide, and picks a new route. The destination stays the same, but the path adapts.

Key Takeaway

The Agile Manifesto does not reject planning or documentation. It simply asks teams to value people, working results, collaboration, and flexibility more highly.