What is Agile Manifesto?

Agile manifesto help to develop the softwares in better way and also educate the team members as well.

There are four pillars for Agile Manifesto:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Principals behind the Agile Manifesto

We follow these principles:

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a  couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development  team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximising the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organising teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.

Big Guns --- Authors of Agile Manifesto

1. Mike Beedle
2. Arie van Bennekum
3. Alistair Cockburn
4. Ward Cunningham
5. Martin Fowler
6. Jim Highsmith 
7. Andrew Hunt
8. Ron Jeffries
9. Jon Kern 
10. Brian Marick
11. Robert C. Martin
12. Ken Schwaber
13. Jeff Sutherland
14. Dave Thomas