The Agile Manifesto

I gave a brief introduction on the history of the agile methodology in my previous post and I would like to continue the discuss and talk about the Agile Manifesto.

Once a decision was made on the need to create a new approach for unpredictable projects, leaders in the software industry published the Manifesto for Agile Software development in 2001.

This is the Agile Manifesto :

The Agile Manifesto

The agile manifesto led to the creation of twelve principles which explain the agile manifesto and these principles are :

Principles behind the Agile Manifesto

Though the agile methodology was originally created to be used for software development, it is now being used in numerous industries.

There are two general strategies that satisfy the agile values and principles and they are :

  1. Formal agile approach : in this approach the agile team learns and understands the agile approaches and then adapts them to suite their purpose.
  2. Adhoc agile approach : in this approach changes are made to the project based on the context. These changes include creating timeboxes to implement solution features and using specific techniques to clarify features.

Agile projects are usually more successful when the following are done:

a. A larger project is broken down into smaller sub-projects so that they are easier to implement.

b. Implement the quick wins first as long as they are not dependent on other requirements.

c. Prioritize changes that would help the organization to achieve its objectives.