What is Agile?

Agile model considers each project must be handled differently, and existing methods must be adapted to best suit the project requirements. The agile tasks are divided into time box (small time frame) to deliver specific characteristics for the release.

An iterative approach is adopted and running software build software is delivered after each iteration. Each assembly more in terms of features; final assembly contains all the functions required to the customer.

Here is a graphic illustration of Agile Model:

Agile SDLC model
Agile thinking process started at the beginning of the software development and started to become popular over time because of its flexibility and adaptability.

The most popular agile methods include the Rational Unified Process (1994), the Scrum (1995), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and the method of dynamic systems (Dsdm) (1995). Now they are together referred to as agile methodologies, after the Agile Manifesto was published in 2001.

The principles Agile Manifesto

Individuals and interactions - in agile development, and self-motivation are important as well as the interaction as co-location and pair programming.

Software Development - Demo software working is considered the best means of communication with the customer to understand their requirements, not only in terms of documentation.

Co-operation with the customer - As the requirements can not be collected in full at the beginning of the project due to various factors, constant customer interaction is very important to get the appropriate product requirements.

Responding to change - Agile focuses on rapid response to change and continuous development.

Traditional Vs Agile SDLC model
Agile is based on adaptive methods of software development, where as traditional SDLC model as the waterfall model is based on a predictive approach.

Forward-looking team in the traditional SDLC models usually work with a detailed plan and have full forecast the exact tasks and functions, which will be delivered over the next few months or throughout the product lifecycle. Prognostic methods are totally dependent on the requirements analysis and planning done at the beginning of the cycle. Any changes that need to be included to pass through a rigorous change management controls and prioritization.

Agile uses adaptive approach, where there is no detailed plan, and there is clarity with regard to the future challenges only to what features should be developed. There is a function on the basis of the development team and adapt to the changing requirements of a dynamic product. The product was tested very often, through the release of iterations, minimizing the risk of any major failures in the future.

Interaction with customers is the basis of the methodology of Agile, and open communication with minimum documentation are typical features of Agile development environment. Agile teams work closely with each other and most often located in the same geographical location.

Agile Model Pros and Cons
Prompt methods currently widespread acceptance in the software world in recent years, however, this method may not always be suitable for all products. Here are some pros and cons of flexible model.

The following table lists the pros and cons of Agile Model:

Pros and cons
This is a very realistic approach to software development

It promotes teamwork and cross-training.

The functionality can be quickly developed and demonstrated.

The resource requirements are minimal.

Suitable for fixed or changing requirements

It provides early partial working solutions.

A good model for environments that change continuously.

Minimum rules documentation easily used.

It enables parallel development and delivery within the overall context of the plan.

Little or no planning is not needed

Easy to operate

It provides flexibility for developers

Not suitable for the machining of complex dependencies.

More risk stability, maintainability and extensibility.

The general plan, the leader of agile and flexible practices of PM is a must, without which it will not work.

Strict delivery management dictates the amount of functionality to deliver, as well as adjustments for the timing.

largely depends on the interaction with customers, so that if a client is not clear, the command may move in the wrong direction.

There is a very high dependence of the individual, as there is minimal documentation is generated.

Transfer of technology for the new members of the team can be quite a daunting task due to lack of documentation.