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.
WE NEED YOUR SUPPORT so we can continue sharing our Knowledge. Any donation, big or small, will help to fulfil Oelean's mission to support and promote the Agile Mindset.
By becoming a paying member of OeLean, you'll get access to a wide range of knowledge- and community-based benefits, by supporting us we will be able to supply our wonderful followers with some extra content, tutorial videos and podcasts in addition to our regular youtube videos.
? JOIN MY PATREON FOR MORE CONTENT
https://www.patreon.com/oelean
FOLLOW OUR TRAININGS
Agile Fundamentals , Scrum and Kanban
?? French Course : https://tinyurl.com/y4auyrtj
?? English Course : https://tinyurl.com/y6o84dna
Scrum Product Owner
?? French Course : https://tinyurl.com/y5ev5z69
?? English Course : https://tinyurl.com/yxz224dt
FOLLOW ME
?️ Youtube: https://www.youtube.com/oelean
❤️ Facebook: https://www.facebook.com/oelean
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.
Concise and straight to the point. Bravo!
❤️❤️❤️???
Brilliantly explained, well done
Thank you!
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.
thank you