Agile vs Waterfall: Choosing Your Methodology

hi in one of my previous videos I was talking about what is a child let's take a look now at the differences between a child and traditional way of working also called water for several years ago projects were managed in waterfall where tasks are executed in phases in a linear and sequential way probably's 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 what if all was organized in such a way that projects has to be finished within a certain budget fixed scope fixed time and the good quality which was almost never the case and the customer was always unhappy in fact even when the project respected the budget skull time and quality the customer was still unhappy but why as waterfall does not require a huge deal of customer involvement so by the time we deliver what we thought the customer needed it's not necessarily what he needs anymore and because of its linear approach and its rigidness towards changes in the development of the product and the process itself it makes it almost impossible for new ideas to be included which clearly impacts the customer satisfaction as well as the quality of the final product it's a child came to solve these issues with the four values and the 12 principles we create things differently in a child we build products incremental II and iteratively which helps teams deliver value to their customers faster and with fewer headaches instead of betting everything on a big bank launch an anti team delivers work in small but consumable increments we start with a small piece of work and we go through the design development testing and deployments the feedback from the customer and stakeholders is then collected and fit back into the cycle with our child changes are welcome the rapid delivery of the value in small increments allow teams to change their products based on customer feedback frequently and with lower costs this helped them to keep up to date with the users needs and the constantly evolving world let's take an example our customer needs a curve to be able to go to work if we decides to build this product in a wonderful way we will start by defining what the ideal car should look like after several weeks or months of thinking and once this phase is done we start building the car first the wheels then the engine the frame then we assemble everything and deliver it to the customer what happens here is that during the first phases the customer is not receiving anything for a long period of time if we are optimistic he is happy with the car you gave him but the customer might say that this is not the car he was expecting and he doesn't like this design in this case change in the design will be very expensive if we decide to build this car in an agile way we will involve the customer on a regular basis and we will ask him for input and feedback while building his car we can start with a Minimum Viable Product it's the least expensive product that can allow us to test our idea and for him to try it based on his feedback we can improve it and add new functionality at the end and after customer was involved all the time and his feedback was act on we know we are delivering exactly what he expects there is one important thing between these two ways of working in waterfall we cannot stop before we deliver the full products defined at the beginning in agile as we are delivering each iteration of functioning products the customer might say that he is happy with what you just presented and he doesn't need more so we don't have to spend more money to add additional features that the customer doesn't need as a summary one of the most notable differences between agile and waterfall is the level of flexibility involved a each one of them where a child prides itself as being an approach that is flexible and continuously evolving waterfall is known to be more rigid and stricter in terms of process structure thank you [Music]

Channel: OeLean

Views: 322,987

Keywords: Agile, Agile values, Agile principles, Agile vs waterfall, agile manifesto, agile manifesto principles, agile manifesto values, agile, agile vs waterfall, agile vs waterfall methodology, agile vs waterfall software development, waterfall vs agile, waterfall vs agile approach, waterfall vs agile project management, agile methodology, what is agile methodology, scrum, differences between agile and waterfall, Agile vs Waterfall, Agile vs Waterfall methodology, when to use agile

Id: 5RocT_OdQcA

Length: 5min 28sec (328 seconds)

Published: Sun Mar 08 2020