agile software development

(redirected from Agile Manifesto)
Also found in: Wikipedia.

agile software development

An umbrella term for a variety of best practices in creating applications and information systems. These methods have proven to be more effective in dealing with changing requirements during the development phase, which always seem to occur. Also called "lean programming," the agile methods emphasize teamwork, customer involvement and, most significantly, the creation of small or partial pieces of the total system that are tested in a user environment. For example, an application with 25 features might be prototyped with only five or six thoroughly completed before adding more, and so on.

The "Agile Manifesto" was created in 2001 by 17 people involved with Scrum, XP and other software development methods, and the Agile Alliance ( was founded to promote the agile philosophy. Contrast with waterfall development. See Scrum, XP, DSDM and iterative development.

The Agile Manifesto
Following is a summary of the philosophy behind the Manifesto (for details on all twelve of its principles, visit It states that although the items on the right have value, the items on the left (in bold) have more value.

Individuals and interactions over processes and tools.

Working software over comprehensive documentation.

Customer collaboration over contract negotiations.

Responding to change over following a plan.
Copyright © 1981-2019 by The Computer Language Company Inc. All Rights reserved. THIS DEFINITION IS FOR PERSONAL USE ONLY. All other reproduction is strictly prohibited without permission from the publisher.
References in periodicals archive ?
|default:svg width="23" height="23default:use xlink:efault:useefault:svdefault:svg width="22" height="22default:use xlink:efault:useefault:svThe first sentence of the Agile Manifesto states: "We are uncovering better ways of developing software by doing it and helping others do it." Is there a difference between Agile for IT and other types of organisations?
These ideas were put together in the Agile Manifesto (Martin, 1991).
The Agile Manifesto was written by software developers primarily to address information technology platforms using commonly available and standardized computer components and applications.
(28) Particularly since the publication of the Agile Manifesto, companies in all industries have begun to recognise the value of operational agility.
Lean, Agile Manifesto and SAFe principles will also be introduced to the participants.
As background, Agile DevOps is a particular methodology and should not be confused with the generic term Agile software development that initially was developed in 2001 by a group of 17 software engineers and describes a set of 12 software development principles that are known as the Agile Manifesto. These principles address items such as early and continuous delivery, of valuable software, welcoming new requirements, simplicity, customer satisfaction by delivering valuable software, and more.
Since the release of the Agile Manifesto in 2001, the popularity and use of Agile has continued to grow.
The Agile Manifesto, the impetus for Agile product development practices, calls for a development process that values collaboration, response to change, and a working product (Beck et al.
Planning is a casualty of today's interpretation of the Agile Manifesto, which can cause Agile teams to lose their way and their customers to lose visibility of what they are getting for their money, now and in the future.
The agile manifesto, Available from: (12, 2014).

Full browser ?