The Agile Manifesto

20 Feb

The Agile Manifesto was written in February 2001, at a summit of seventeen independent-minded practitioners of various programming methodologies.The Agile Manifesto,also known as the Manifesto for Agile Software Development, is a formal proclamation of four key values and 12  principles to guide an iterative and people-centric approach to software development. The Agile Manifesto was created as an alternative to document-driven, heavyweight software development processes such as the waterfall approach. It provides a philosophical foundation for effective software development.  Contrary to some of the criticisms you may have heard from the traditional community, the agile movement is based on some very solid concepts and the methodologies clearly reflect that.

The four core values of  agile software development as stated by the Agile Manifesto emphasize:

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

 Some of the key incentives behind the development of the Agile Manifesto are as follows (12 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.
 The agile manifesto is a great idea as instead of defining processes for people to handover work, integrate work etc. All members communicate by working togetgher as a team, resulting in colaborative thinking and swift problem solving.
-Instead of taking several months to release, this format results in a working prototype being created in just 1 month, ready to be used. 
The agile mnifesto can be found at http://agilemanifesto.org/ .
 
Links:
 http://c2.com/cgi/wiki?AgileManifesto
cathaldoyle.com
 

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: