The Agile Manifesto, Part 1: Introduction
In this series, I’ll be exploring the Agile ‘Software Development’ Manifesto created by the 17 members of the Agile Alliance during a conference in Snowbird, Utah from February 11-13, 2001.
(Screenshot taken from agilemanifesto.org with added annotations)
The Agile Manifesto has six sections:
-
Title: The choice of the word manifesto is an interesting one, implying a need for changes in how software was developed at that time. And the word agile suggests quickness, flexibility, and responsiveness to changing requirements.
-
Preamble: An introductory statement setting forth the goal of improving software development through a set of values.
-
Values: Describes four values for how software should be created by contrasting them with four other values. (In follow-up posts, I will be exploring each of the values contained in the Agile Manifesto.)
-
Clarification: Modifies the values section by stating the preference for certain values over the contrasting values but not fully negating the contrasting values.
- Authors: Provides a listing of the 17 members of the Agile Alliance, a Who’s Who of software development experts. Including representatives from various different (and, in some cases, competing) agile practicing groups:
- License: A permissive license for using the Agile Manifesto.
For more information on the Agile Manifesto, check here and here.