Agile software development methodology is an process for developing software (like other software development methodologies – Waterfall model, V-Model, Iterative model etc.) However, Agile methodology differs significantly from other methodologies. In English, Agile means ‘ability to move quickly and easily’ and responding swiftly to change – this is a key aspect of Agile software development as well.
- Brief overview of Agile Methodology
- Example of Agile Software Development
- Difference between Agile model and Non-Agile models
- When to use Agile and Non-Agile models
- Advantages of Agile Methodology
- Disadvantages of the Agile Methodology
- In traditional software development methodologies like Waterfall model, a project can take several months or years to complete and the customer may not get to see the end product until the completion of the project.
- At a high level, non-Agile projects allocate extensive periods of time for Requirements gathering, design, development, testing and User Acceptance Testing, before finally deploying the project.
- In contrast to this, Agile projects have Sprints or iterations which are shorter in duration (Sprints/iterations can vary from 2 weeks to 2 months) during which pre-determined features are developed and delivered.
- Agile projects can have one or more iterations and deliver the complete product at the end of the final iteration.
Example: Google is working on project to come up with a competing product for MS Word, that provides all the features provided by MS Word and any other features requested by the marketing team. The final product needs to be ready in 10 months of time. Let us see how this project is executed in traditional and Agile methodologies.
In traditional Waterfall model –
- At a high level, the project teams would spend 15% of their time on gathering requirements and analysis (1.5 months)
- 20% of their time on design (2 months)
- 40% on coding (4 months) and unit testing
- 20% on System and Integration testing (2 months).
- At the end of this cycle, the project may also have 2 weeks of User Acceptance testing by marketing teams.
- In this approach, the customer does not get to see the end product until the end of the project, when it becomes too late to make significant changes.
The image below shows how these activities align with the project schedule in traditional software development.
With Agile development methodology –
- In the Agile methodology, each project is broken up into several ‘Iterations’.
- All Iterations should be of the same time duration (between 2 to 8 weeks).
- At the end of each iteration, a working product should be delivered.
- In simple terms, in the Agile approach the project will be broken up into 10 releases (assuming each iteration is set to last 4 weeks).
- Rather than spending 1.5 months on requirements gathering, in Agile software development, the team will decide the basic core features that are required in the product and decide which of these features can be developed in the first iteration.
- Any remaining features that cannot be delivered in the first iteration will be taken up in the next iteration or subsequent iterations, based on priority.
- At the end of the first iterations, the team will deliver a working software with the features that were finalized for that iteration.
- There will be 10 iterations and at the end of each iteration the customer is delivered a working software that is incrementally enhanced and updated with the features that were shortlisted for that iteration.
The iteration cycle of an Agile project is shown in the image below.
This approach allows the customer to interact and work with functioning software at the end of each iteration and provide feedback on it. This approach allows teams to take up changes more easily and make course corrections if needed. In the Agile approach, software is developed and released incrementally in the iterations. An example of how software may evolve through iterations is shown in the image below.
Agile methodology gives more importance to collaboration within the team, collaboration with the customer, responding to change and delivering working software.
Agile development has become common place in IT industry. In a recent survey over 52% of respondents said that their company practiced Agile development in one form or another. Irrespective of your role in the organization, it has become essential to understand how Agile development works and how it differs from other forms of software development.
In traditional approach each job function does its job and hands over to the next job function. The previous job functions have to signoff before it is handed over the next job function authenticating that the job is full and complete in all aspects. For example, Requirement gathering is completed and handed over to design phase and it is subsequently handed over to development and later to testing and rework. Each job function is a phase by itself.
In Agile way of working, each feature is completed in terms of design, development, code, testing and rework, before the feature is called done. There are no separate phases and all the work is done in single phase only.
|Approach of this methodology||This methodology is very flexible and adjustable and can adapt to the project needs.||This methodology is not as flexible as Agile model and it’s tough to accommodate changes in the project.|
|Measurement of Success||The success of the project in Agile model is measured by the Business value delivered.||In this methodology the success of the project is measured by the Conformation to plan.|
|Size of the Project||The Project size is usually small in Agile model. However larger projects can also be handled using the Scaled Agile Framework (SAFe).||The project size is Large in non- Agile models.|
|Style of Management||The style of management in Agile model is not centralized. It is distributed among the team members.||The management style in the non-Agile models is dictatorial. Only one person is the decision maker and rest of the people follows him.|
|Ability to adapt to change||In Agile model the changes are accepted and adapted as per the project needs.||But in non-Agile models the changes are not accepted easily in the later stages of the development.|
|Documentation required||Less documentation is required in Agile.||More documentation is required in non-Agile models.|
|Importance of||In Agile model more emphasis is given to the people that means it’s People- Oriented.||In non-Agile models the more importance is given to the process hence it’s Process- Oreinted.|
|Cycles or iterations||Agile methodology has many cycles or iterations which is also known as Sprints.||But, in Non-Agile methodology the cycles are limited.|
|Planning in Advance||There is minimal upfront planning in Agile methodology.||In Non-Agile models the planning should be complete before the development starts.|
|Revenue||In Agile method the return on investment is early in the project cycle.||In non-Agile methods the return on investment is at the end of the project.|
|Size of the team||The size of the team in Agile methodology is usually small and creative.||But in Non-Agile models the team size is large.|
|Project Attributes||Agile Model||Non-Agile Model|
|Requirement of the Project||Requirements in Agile model can change as per the customer requirement. Sometimes requirements are not very clear.||In Non-Agile models the requirements are very clear before entering into the development phases. Any change in the requirement is not easily accepted during the development phases.|
|Size of the Project||The Project size is small in Agile model hence small team is required.||But in Non-Agile models the Project size is usually big hence big team is required.|
|Design of the Project||In Agile model the architecture is made as per the current requirements but is designed to be flexible.||In Non-Agile models the architecture is made as per the current requirements as well as for future requirements.|
|Planning and Control of the Project||In Agile model the planning of the project is Internalized and has qualitative control.||But in Non-Agile models the plans are documented properly and have quantitative control.|
|Type of Customers||Agile methodology is followed by the collaborated, dedicated collated and knowledgeable customers.||In Non-Agile models the customers are of Contract provisions.|
|Developers required||In Agile model the developers should be knowledgeable, analytically strong, collated and collaborative.||In Non-Agile models the developers should be more Plan Oriented.|
|Refactoring||In Agile model refactoring is not costly.||But in Non-Agile models the refactoring is very costly.|
|Risks involved||Usually in Agile models the chances of occurrence of unknown risks are more which can have major impact in the project.||In Non-Agile models the risks are understood clearly and the impact of the risk in the project is very less.|
- In Agile methodology the delivery of software is unremitting.
- The customers are satisfied because after every Sprint working feature of the software is delivered to them.
- Customers can have a look of the working feature which fulfilled their expectations.
- If the customers has any feedback or any change in the feature then it can be accommodated in the current release of the product.
- In Agile methodology the daily interactions are required between the business people and the developers.
- In this methodology attention is paid to the good design of the product.
- Changes in the requirements are accepted even in the later stages of the development.
- In Agile methodology the documentation is less.
- Sometimes in Agile methodology the requirement is not very clear hence it’s difficult to predict the expected result.
- In few of the projects at the starting of the software development life cycle it’s difficult to estimate the actual effort required.
- The projects following the Agile methodology may have to face some unknown risks which can affect the development of the project.