The Agile Manifesto Values and Principles

Agile manifesto refers to the set of rules or values used in an agile project. It contains mainly 4 values:

1. Individual and Interactions
2. Working software
3. Customer collaboration
4. Responding to change

Over (in traditional project):

1. Processes and Tools
2. Comprehensive documentation
3. Contract negotiation
4. Following a plan

Let's discuss these four values in details:

Individual and Interactions: Agile development follows a whole team approach and is very people centered. Development team builds software through communication and interaction among different teams and people instead of depending on tools and processes. Individual team member offers a specific skill set and whole team involves in planning the development and testing strategies. 

Working software: It is always beneficial to see the working software instead of heavy documentation. It also helps developers in getting early feedback from the clients which in turn cuts down the cost of accommodating changes. It brings transparency to the project where everybody can see the progress and contribute to it. 

Customer collaboration: In agile, customers are involved in every stage which gives a clear idea about their expectations and what exactly they want to see in the product. Working with customers regularly helps in building the right product and helps in project success. 

Responding to changes: This is the real beauty of Agile development. Project plan should be flexible enough to embrace frequent changes. Both development and testing should be able to respond to the changes in the given time frame.

Here are 12 principles which capture above 4 values of agile manifesto:

1. Early and continuous software delivery
2. Accommodating changes even in later stages
3. Delivering working software at regular intervals
4. Whole team approach
5. Support team members and give them the motivational environment to work
6. Have face to face conversation whenever possible
7. Maintaining constant pace and sustainable development
8. Pay attention to technical excellence 
9. Simplicity (Art of maximizing the amount of work NOT done)
10. Self organizing team
11. Regular retrospective meetings
12. Progress is measured by working software

This data outline is taken from the ISTQB syllabus for Agile certification.