Ken Orr wrote ( in Cutter IT Journal Vol.3, No. 7 ):

Agile . since Jun 23 . Index . DOCs TOP TOC

THE AGILE MANIFESTO


The Agile Manifesto as put forward at Salt Lake City was a very simple and straightforward set of common principles (see Figure 2).

 

Figure 2

Figure 2 -- The Agile Manifesto.

Remember, if you want to start a religious or software war, issue an edict or manifesto. The issuing of the Agile Manifesto represented a watershed event for those involved with radical methodologies -- the Rubicon had been crossed; the gauntlet had been thrown down. It began the war with the establishment, or at least those supporting CMM.

As we will see, there are some fundamental differences between the agile movement and those who support CMM, but then again, their goals and objectives are also different. First, we will discuss the full set of process and concepts that advocates of agile development propose, and then we'll discuss the audience that agile development addresses.

 |

The Agile Development Approach

.    The Planning Game

.    Small Releases

.    Metaphor

.    Simple Design

.    Testing

.    Refactoring

.    Pair Programming

.    Collective Ownership

.    Continuous Integration

.    The 40-Hour Week

.    The On-Site Customer

.    Coding Standards

Comments on Committing to Agile Development

Comments on Minimalist Design and Refactoring

Comments on the Agile Manifesto

The Pluses of Agile Development

The Minuses of Agile Development

Some Keys to Success with Agile Development

Agile . since Jun 23 . Index . DOCs TOP TOC

The Agile Development Approach


If CMM is a set of loosely connected software management best practices, agile development is a set of highly integrated development and management practices.11 In his book, Extreme Programming Explained [1], Beck proposes 12 different ideas that are key to his form of agile development:12

        1.      The planning game

        2.      Small releases

        3.      Metaphor

        4.      Simple design

        5.      Testing

        6.      Refactoring

        7.      Pair programming

        8.      Collective ownership

        9.      Continuous integration

        10.  40-hour week

        11.  On-site customer

        12.  Coding standards

 |

The Planning Game

Small Releases

Metaphor

Simple Design

Testing

Refactoring

Pair Programming

Collective Ownership

Continuous Integration

The 40-Hour Week

The On-Site Customer

Coding Standards

Agile . Index . DOCs . TOC