Agile Manifesto and Principles behind Agile Manifesto

In February 2001, 17 software developers met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development to define the approach now known as agile software development. Some of the manifesto’s authors formed the Agile Alliance, a nonprofit organization that promotes software development according to the manifesto’s principles.

Manifesto for Agile Software Development

Agile Manifesto Individuals and interactions

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.

Principles behind the Agile Manifesto

We follow these principles:

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers must work
together daily throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity–the art of maximizing the amount
of work not done–is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

Reference :
http://agilemanifesto.org/history.html
http://www.agilemanifesto.org/principles.html
http://en.wikipedia.org/wiki/Agile_software_development#Agile_Manifesto

What is Agile Software Development

Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizingcross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle. The Agile Manifesto[1]introduced the term in 2001.

Agile development is a common umbrella term used for today’s highly iterative and incremental approaches to software development.  The term was first used in 2001 when the Agile Manifesto was published as a unifying charter by many of the leading visionaries in the software field at the time who were fed up with traditional approaches to software development.  Unlike traditional software development practices, agile development methodologies such as Scrum, Extreme Programming, Dynamic System Development Method (DSDM), Lean Development, Feature-Driven Development (FDD), Crystal, Adaptive Software Development (ASD), and others incorporate close, cross-functional collaboration and frequent planning and feedback as fundamental tenets inherent to the evolution of a software system.

The overarching focus of agile development projects is the frequent delivery of high-quality, working software in the form of business-valued functionality.  Each of these methods emphasizes ongoing alignment between technology and the business.  They are all considered lightweight in nature in that they strive to impose a minimum of bureaucracy and overhead within the development lifecycle.  They are adaptive in that they embrace and manage changing requirements and business priorities throughout the development process.  With any agile development project, there is also considerable emphasis on empowering teams and collaborative decision-making.