Agile vs Waterfall Methodologies

 

Video 1: Agile vs Waterfall

Agile Methodology

"Agile was developed as a flexible method that welcomes incorporating changes of direction even late in the process, as well as accounting for stakeholders’ feedback throughout the process" (Forbes.com).

Team works in phases in agile and deadlines are short. This is an incremental and iterative approach. Agile is done in sprints and allows requirements to change over time. This will help to incorporate feedback from the stakeholders. 

Benefits of Agile

• Flexible with the change
• Efficient communication and empower team to make decisions
• Customer focused approach
• Fast Software development life cycle

Waterfall Methodology

"Linear form of project management ideal for projects where the end result is clearly established from the beginning of the project. The expectations for the project and the deliverables of each stage are clear and are required in order to progress to the next phase" (Forbes.com). This method will provide you with clear plan from start to end. Each phase should have deliverable to start the next phase. 

Benefits of Waterfall

• Easy costing
• Progress can be measured clearly
• Team roles are defined well
• Scope of work is defined well

Comparison of Agile and Waterfall

Agile	Waterfall
Plan for sprints	Start to finish project plan
Teams of 3-9 people	Large teams
Change is accepted	Resist to change
Frequent customer involvement	Occasional customer involvement

These each method is different and can be utilised in different situations. If project outcomes are clear from the beginning, best fit would be waterfall methodology. whereas Agile is a suitable method for is project is conducted in fast changing circumstances and the final deliverable is not clear for the team. Currently agile methodology is widely used due its flexibility in many projects.  

References

https://www.forbes.com/advisor/business/agile-vs-waterfall-methodology/

https://project-management.com/agile-vs-waterfall/