Agile Methodology

Term Definition
The term “Agile” refers to a software development methodology which promotes a project environment of adaptation, teamwork, self-organization, rapid delivery and client focus. The Agile method bears conceptual similarities to Six Sigma.

History
In part as a response to traditional project management methods which were seen as inflexible, slow, bureaucratic and unsuited to software development, the Agile method gained definition in the mid 1990’s. In 2001, the Agile Manifesto was published which documented the definition and principals of Agile development.

Overview
In contrast to more traditional and rigorous approaches to project management and development, the Agile Manifesto states:

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

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

That is, while there is value in the items on the right, we value the items on the left more.

Not to be mistaken as being unstructured or undisciplined, the Agile method is better considered to be “adaptive” (concerned with short-term tasks within a long-term mission framework) versus “predictive” (features and tasks planned through the length of the project).

While the Agile method is used successfully and championed by many prolific developers and firms, there exist warranted criticisms of the method, which include:

• Does not work well with junior-level developers
• Incorporates insufficient software design
• Bloated expense to customers due to frequent requirements meetings
• Can lead to more difficult contractual negotiations
• Can be very inefficient—if the requirements for one area of code change through various iterations, the same programming may need to be done several times over. Whereas if a plan were there to be followed, a single area of code is expected to be written once.
• Impossible to develop realistic estimates of work effort needed to provide a quote, because at the beginning of the project no one knows the entire scope/requirements
• Can increase the risk of scope creep due to the lack of detailed requirements documentation

Related Terms
Project Management
Six Sigma

External Links
The Agile Journal

Your Comments and Recommendations

Please help us improve the project management software glossary. Was this term well described? Any suggestions of how we can improve the description, what to add, remove or change? You can also use this form to suggest new project management terms we should add to the glossary.