ฝัง
- เผยแพร่เมื่อ 5 ต.ค. 2024
- 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
📚 GET OUR FREE AGILE BOOKLET WORTH 39$
oelean.com/agile-booklet/
This video so far is the best video for agile and waterfall i found ....... I wish I found this before attending some boring class
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.
Hello Paulo and thank you for this comment.
When we talk about customer in the video we meant the end user, the person who will be using the product or service.
This being said, we definitely agree with your comment, Agile is not the answer for everything, Agile might be a good way of working in certain cases but Waterfall could also be the best project management method in some other cases and the type of projects you listed above (bridges, buildings, equipment construction…) are a great example of it, it really depends on the kind of problems you are trying to solve.
We have created a video explaining when to chose Agile or Waterfall, you can find it here : th-cam.com/video/Re_3fIymbK0/w-d-xo.html
Thank you again for your comment and have a wonderful evening
I thought the same thing too. Like there is interaction with the customer for waterfall methodology. It may not be during the implementation phase but prior to that, especially during the planning phases, they would need to agree on what it is that they want, how much it's gonna cost, what they want it to look like, what materials they'll use...all that and more. In this video, it's like a customer calls and says I want a car, and then the project manager just creates whatever car he wants and sends it to the customer.
-flawed.
Nice video
Well said!!!
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.
These are only myths, while in waterfall model i receive so many change requests and have to adhere to it as per the expectations.
Concise and straight to the point. Bravo!
Thank you so much. This is the best definition of agile I found so far. And I could say I understand now
Agile what? there are many adaptations of agility beyond its IT origins. For the best definition of agility read the 4 Values and 12 Principles of the Agile Manifesto then adapt ALL of them to the work you are doing.
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
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.
No but the client can come in with change of mind with the model, to me, Agile is the best, since it’s flexible and ready for change.
@@Mimi-jg6gk Client can come not after starting the project. He/She can during the initiation and planning period and not during the project execution. Agile is suited for various domain and not for construction where changes are always entertained.
@sumesh: Agile is Iterative and Incremental model.
Every sprint the Client is involved in and their feedback is listened to.
1. In waterfall the client is involved after the project delivered but not in between
2. Agile is adaptive planning
.
@@mpraveeen I don't agree with you. Client requirements are collected during the project initiation period right?
Moreover Change Management is accepted during the execution period too if it's worth it for the client and project. Agreed?
If so how can we say that the client is only entertained after the project completion.
I still believe both construction and fitout of a building should be done by waterfall methodology by infusing lean construction only.
Agile Alliance was formed by the software domain, for the software domain and of the software domain.
@@Mimi-jg6gk it's based on the domain that you work.
It is a really good example for differentiating agile vs waterfall and it made my doubts more clear.
Awesome diagrams and examples to make this understandable. Thank you!
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.😀
Best video explaining it I have found. Thanks!
The only video that helped me understand agile
Very clear and straightforwarded explanation. Thank you.
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.
This is situational, depending on
1) What type of project are you doing?
2) how big is the project?
3) who is your customer and what does the customer wants?
4) how easily you can break down a project in to smaller deliverable packages?
...
In simple words, Agile is just breaking a big project in to small packages and running waterfall on each of them :)
That was a great explanation of the difference between waterfall and agile.
Awesome work. Very clear explanation, thank you so much!
Best explanation so far.
Very clear explanation of the difference between waterfall and agile.
Thank you!
Thank you very much for using exemple, is more clear.
I'm appreciate for the knowledge. Fairly certain it made sense. Thank u🙏
very good and simple, no technical bombardment :), well done,
Need to learn more about Agile in the reality, I mean to apply it in some automotive projects and change management process.
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!!
absolutely agree
Completely agree, this is a very biased presentation
I agree - I‘ve been in the automotive industry for 10 years and we do always iterative loops an improve the product from each state to the next in parallel processes for several thousand parts and it’s still sth. like waterfall
I agree. These are two ways of delivering a project. Just like a tool, you have the right application. You don't expect to create an Agile team to deliver the same project as a waterfall team.
For instance: To build a bridge and to develop a game. Two worlds. You cannot, or shouldn’t, spend time delivering a bridge in phases. You can get environmental approvals, budget.. etc but not as a game where you can test an infinite number of times.
Unfortunately, Agile is a "new" thing (not new, but compared with other methods it is really new), therefore we still see discussion over which one is better.
There is no better. There is: which one is ideal for this case?
Still don't understand?
wich is better? A ferrari or a Land rover? well... Are you going to a race or are you going to a farm during winter?
Very well explained.. Thank u soo much!!!
Very good explanation and visual comparison 👏 thanks
thanks for this
Wow, that is really great content Mrs.
That's not how a car is built in waterfall. The different systems are developed simultaneously. Also, when would the customer be involved in feature requirements of the vehicle without letting competitors know what is being developed?
Thank you, I understand it now
Great Explanation, I never come across such kind of description.
very clear and concise...!!
Thanks for giving us such video
Short but sweet and very well explained..
Thanks for your explanation
The car build example is not correct.. in Agile they show a pre-assembled truck like symbol which grows into a car.. not sure how they go the pre-assembled truck like chassis doesnt that have to built... shows waterfall in poor light and agile as the miracle saviour...there maybe cases where u still need to use Waterfall for eg Infra build and Agile for your application rollout
Excellent! Thank you!
Very 'to the point' illustration. Well done
excellent video
What a great video!!!!
So helpful!
This makes agile look like waterfall but drawn in a circle.
This help me understand! Thank you!!
How do you decide or estimate the price/ budget of the project in agile methodology, because any project you do either by agile or waterfall approach, a cost is to be decided
Ty great video
thanks
This is a biased representation in favor of Agile and completely omits the role of change management in Waterfall methods as well as the role of the customer in requirements definition, schedule planning, and change control. Any changes to a product or solution can be similarly made during waterfall. Impact to schedule and cost are assessed and the customer may approve or reject the changes. If the changes are approved, the schedule is re-baselined and the work continues. In organizations for whom budget commitments are important, Waterfall may be a much better and safer alternative. The solution can be sized or phased based on fiscal constraints. Agile, on the other hand, has no idea where it's going until all is said and done. The most likely outcome is a solution which wildly exceeds financial and schedule commitments. It may meet the mark from a fit/function standpoint in an evolving world, however it ignores the time and budget commitments often imposed by boards and sponsors.
Wondering how requirement definition is impacted by agile approach?
For example in waterfall, you would expect that we get requirements for every part of the car and check they all fit together before building anything.
For agile, are requirements for all phases at least drafted and reviewed ahead of time? I can see issue for example if you only build the wheel base first phase, but but then in second phase customer wants an engine that does not fit...it could mean major re-design of already built product.
thank you! very informative and interactive with the videos!
Wow great explanation
This is great
Great explanation. 👌🏼
thank you so much there was a very clear explanation! :)
Thank you for sharing
Very well explained
The older I get the more I realize how much money can be made "reinventing" the wheel and repackaging it as something new, when it is still in essence a wheel. Each adopter of the new "wheel" always thinks their version of the wheel is better. But it is just different.
great explanation!
Brilliantly explained, well done
NICE VIDEO!!!!!!!!
super clear
thanks really understanding these methods may I use agile from our system development document.
thank you
please tell me....how software requirements can appear in different context of software development lifecycle such as waterfall, spiral and agile processes
great
But what's the point of the hand "drawing"?
great
great!!!
what did you create this video in ?
Thankssss... my exam is after exactly 1 hour😂
The customer would be happy but the product would be crappy!
Thank you for your comment, could you please share with us the challenges that might make the product not good?
@@OeLean bellow example When it comes to art related jobs, I expirienced this firsthand, As Artists we eather visualise the final output or push to get a brilient output while the work evolve, when the output is broken down to stages ( seing Halfwaydone/ workin progess work, the clent always gives feedback, amendments, new Ideas due to lack of his ability to previsualize, and start commenting, also every stage when the client is involved as mentioned above, new Ideas are added in ( new things, trends he sees or likes, he'd try to add ), so there wouldn't be a Style lockdown, Script lockdown, so the consistancy of the visual style breaks, frustration ontop of frustration gets build. Artists just become mouse clickers, where they'll give up their artistic freedom and input and will endup doing what client suggests. at the end the product will be lesser in quality, artists will be fedup and the client would be happy. ( Not all of the Clients but Many of the clients)
You just seem biased towards Agile. You gotta mention that choosing which methodology depends on the project itself, for instance developing a healthcare, banking, or military project, the Waterfall model would be the best candidate.
the link to the free booklet is not valid
Thanks for letting me know, I will check
Thumbs up for differences described. For school-theory purposes maybe. Added value for real life usage is almost none. Projects does not work that way. Maybe some IT product related..Apps and stuff.. Maybe and just in some. For others it is simply nonsense,
Disappointing that the video is little more than a sales pitch for agile - maximising the benefits of agile without identifying the downsides, and maximising the downsides of waterfall without highlighting the benefits. Each has a place and different projects will work better under each stucture depending on the nature of the project and the culture of the organisation.
Good Agile overview, Poor Project management basic knowledge understanding. Traditional Project management is much more than a GANTT chart. These kind of comparisons are useless..
Or, just develop software like it's always been done, which was perfectly fine before consultants started labeling things and pushing unnecessary services.
As a part of Uberization initiative of Razor Power plant, in-plant vehicle movement are
being restricted to minimize the use vehicle in the plant area. Here vehicles will be used
for movement of materials, usage of the logistics and to give a critical support in un-
planned shutdowns. In order to control the use of vehicle and to control the situation it
was decided to make an online booking of vehicles as a form of mobile app solution. A
mobile app will be created and data will be stored on cloud.
Technology used is J2ME and oracle and Google app used to know the location and shortest
path between source and destination. Uber kind of app will be prepared for users along
with vehicle booking, cancel booking and fixed payment for the first phase. Once the first
phase will be implemented successfully then in the 2nd phase booking in advance, critical
booking, bill generation, vehicle types, user rating, discount, promotion will be
implemented.
Plz tell me which method used for this case study?
❤️❤️❤️👍👍👍
U sound moroccan
Wow, that was an extremely limited view. I've used waterfall for years, and that's why stakeholder involvement in throughout the process is so important. Your video assumes that waterfall never involves the customer throughout the process. If that's how you managed waterfall, then you certainly did it incorrectly.
Ok so at the beginning of the video you basically lay out why using the waterfall method is a bad idea and then I'm sitting here in college paying to learn a out the waterfall method like I don't get it Jesus lol these people
This video appears to be confusing software development and project management. Project management has NEVER been defined by a life-cycle and projects can use ANY appropriate life-cycle. Its true they do Start, Do stuff then Finish, but thats hardly a life-cycle.
It also make NO sense to restrict a project management method to e.g. an iterative life-cycle as methods are supposed to be generic and adaptable. And here is the key point, project management agility has little to do with life-cycle but the adaptation of ALL of a PM method in a given project.
This is misleading.....at best!
The problem is that its wrong.
The facts don't match. Software, now more than ever, is of poor quality. More bugs, more glitches, more unfinished features - and software is slower and more bloated than ever. Agile is more than likely the #1 reason for this. The software industry is embarrassing.
English please!!!!
stop your background music
I will work on that for next videos, thanks for the feedback
Car is not perfect example....
lots of bla bla bla
Thank you
Thanks