Agile vs Waterfall: Choosing Your Methodology

This short video explains the differences between Agile and Waterfall, and gives an example for both of them.

Several years ago, projects were managed in waterfall project where we Tasks are executed in phases in a linear and sequential way and progress flows downwards in one direction like a waterfall. Each of these phases represents a distinct stage and each stage generally finishes before the next one can begin.
Waterfall was organized in such a way that projects had to be finished within a certain budget, fixed scope, fixed time and a good quality, which was almost never the case and the customer was always unhappy.

Agile came to solve these issues, with the 4 values and the 12 principles we create things differently. In agile we build products incrementally and iteratively which that helps teams deliver value to their customers faster and with fewer headaches.

Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments.We start with a small piece of work and we go through the design, develop, test and deploy, the feedback from the customer and stakeholders is then collected and fed back into the cycle.

#agile #businessagility #agility

[OeLean]

📚 GET OUR FREE AGILE BOOKLET WORTH 39$

[iuumkl]

This video so far is the best video for agile and waterfall i found I wish I found this before attending some boring class

[paulomarciohaack]

The level of interaction between the Sponsor (Customer) and a waterfall project team is at the discretion of the Project Manager. So, the idea suggested by this video that every Waterfall project will keep its Sponsor out of the loop it is flawed. For instance, in a waterfall project, the Sponsor might be required to approve milestones so that they will be involved during the entire project. Certainly, Agile methodology offers an extra level of flexibility and is great for projects where the requirements are expected to change; software development is a good example where Agile has been successfully used. But in projects where the requirements and constraints are clear and must be respected (bridges, buildings, equipment construction…), Waterfall is the methodology you will want to use.

[sasca]

Ah, if only it were this smooth and simple in practice. The fact is, there's really only a semantic difference between waterfall and agile. There's no reason, for example, why the customer would need to be excluded in every step of the car-creating process in your waterfall example, and in agile it's entirely possible (or even probable) that what the customer _thought_ they wanted still isn't what they actually wanted-- and that's at _every_ iteration, which leads to _lots_ of overhead. And let's not trivialize how difficult it can be at times to even get to that MVP stage.

[napi]

Concise and straight to the point. Bravo!

[ellakou]

Thank you so much. This is the best definition of agile I found so far. And I could say I understand now

[jayasrimohanrajan]

hi.. wht I cant understand in 3 hours you explained me, made me understand in 10 minutes.. the car exmple is just amazing.. Thank you so much

[sumeshsivsankar]

I strongly believe that Waterfall Methodology is best suited in construction domain. Think of a high rise building. Would the client comes up daily or weekly with a change he/she wants? Step by step process is the best suited concept here.

[skpalakiko]

Awesome diagrams and examples to make this understandable. Thank you!

[navjotsandhuria]

It is a really good example for differentiating agile vs waterfall and it made my doubts more clear.

[vijnathamondreti]

Loved the presentation and explanation too...Had gone through multiple videos prior to this but this one was so clear and to the point...Thank you.😀

[txpatriot]

So with Agile you build a cheap car and let the customer drive it then make changes...I'd like to see the cost-benefit on that. This makes me think of the Simpsons Episode when Homer helps his brother build a car for the average guy.

My experience with Agile is not good. It seems to be the latest hip thing in business; like the fad diet...someone is selling a book. The problem this does work on some things but it is no silver bullet (not car building). Yet, people try to apply it everywhere. You should have a waterfall approach with milestones and maybe some of the milestones or tasks as Agile. IMO


In all good video and good explanation.

[PaddyDAngelo]

Best video explaining it I have found. Thanks!

[baoton]

The only video that helped me understand agile

[NancyAngelArtemis]

Very clear and straightforwarded explanation. Thank you.

[rodneyrobinson]

That was a great explanation of the difference between waterfall and agile.

[albertoramos]

Awesome work. Very clear explanation, thank you so much!

[srinivaskunapareddy]

This tutorial shows waterfall method in poor light and as inferior compared to agile method. It is not the case. The two methods are applicable in two different scenarios and hence are not comparable.
In waterfall method also, the customer is continuously involved in the project. Customer needs to give various approvals, process monthly/milestone payments, supply their scope of work etc etc.
You said that the projects in waterfall method are almost never completed within the triple constraints and quality. It's not true. Thousands of projects were completed within the constraints!!

[lomari]

very good and simple, no technical bombardment :), well done,

[markfaulkner]

Very clear explanation of the difference between waterfall and agile.