12 Principles behind the Agile Manifesto

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 maximizing the amount  of work not done–is essential.
11. The best architectures, requirements, and designs  emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Advertisement

Manifesto for Agile Software Development

source: http://agilemanifesto.org/

We are uncovering better ways of developing

software by doing it and helping others do it.
Through this work we have come to value:

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

That is, while there is value in the items on
the right, we value the items on the left more.

Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler

James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick

Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas

 

Agile Methodology Definition

Agile Methodology was a direct response to the dominant project management paradigm, waterfall, and borrows many principles from lean manufacturing. In 2001, as this new management paradigm began to pick up momentum, agile was formalized when 17 pioneers of the agile methodology met at the Snowbird Ski Resort in Utah and issued the Agile Manifesto. Their manifesto is now considered the foundational text for agile practices and principles. Most importantly, the manifesto spelled out the philosophy behind agile, which places a new emphasis on communication and collaboration; functioning software; and the flexibility to adapt to emerging business realities.

 

Related articles

• 8 questions you MUST contemplate and answer before going Agile (vineetkumarblog.com)
• Does Agile work? (stevecayzer.wordpress.com)
• Project Management Methodologies: Waterfall Agile & Scrum (business2community.com)