Agile (adaptive) model

Purpose Riding the life cycle Agile (Adaptive) model

Abstract

Agile model is a new way to approach Project, Program and Portfolio Management. It is a combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery of working software product.

Although there are some adaptive methods that are from before 2000’s, it is possible to date the concept of agile in 2001 when it was signed the Agile Manifesto. The Agile Manifesto outlines 4 Core Values (individuals and interactions; working software; customer collaboration; and responding to change) and 12 Guiding Principles which are of key importance for any team aiming at using an agile methodology.

The agile model is an adaptive model that is divided in 5 phases: envision, speculate, explore, adapt and close, whereas the traditional models are based on a predictived approach (i.e., waterfall model). Both typologies of modelling have their pros and cons and the best approach to follow depends on the project/product.

Its goal is to assist companies provide value more frequently to their clients, react quicker to changes, and eventually improve the business. It is utilized when it is necessary to divide a large project into more reasonable tasks and complete them in short iterations throughout the project life cycle, defined as the set of phases from the start to the end of a project.

The model can be applied to almost any project, as it is not related to its size or complexity. However, it is not suitable for all cases, and it is fundamental to carefully define when to implement it. It is also important that the companies adopting the agile model make sure that their employees are aware of the rules and methodologies to successfully work with such a model.

Big Idea

History

Agile Manifesto

Description model

Explanation of how the model works

Application

Adaptive model

Adaptive vs predictive (agile vs waterfall)

Limitations

Pros and cons

When to use the agile method and when not. How could it be implemented.

References

1. SDLC - Agile Model

2. Manifesto for Agile Software Development

3. Agile Body of Knowledge

4. Life cycle,