Hi there, I hope that you're doing well! Thank you so much, this was so detailed and well-explained! Thank you for the effort that you put into this video! Have a wonderful day! :)
Hi there, do you have an email contact for business queries? I would like to enquire on rights to reproduce your video as an education resource. Thank you.
I know the comment is a year old, just wanted to give others the idea why Waterfall is not a very good model in a large organization. In Agile, if you see an issue and you know what to do about it you can easily make the change yourself and report your findings to the immediate manager. With waterfall, you will need approval before making the change; before making a report, and then submitting it to the management. This doesn't seem so bad until you realize that you can accomplish the task in like 15 mins in Agile but with Waterfall, sometimes it will take days just to get an approval. Testing and implementation considered, it is so much more cumbersome in a Waterfall model since all individuals that are involved are circling around a very inefficient model and frustrating bureaucracy. This is why when I apply for a job, I always ask what is the main methodology they use, since I get extremely frustrated with these approvals. Sometimes it gets bounced back to people who have no idea what they are doing and that adds more time to resolve, say, something that I could've done myself in like 30 mins.
@@rosshoyt2030 hey can i ask a question, if a system is already done and finished but the client wants to add two simple features to the system is waterfall model is suitable? sorry English is not my first language.
