"I hope you found this useful". THAT WAS DEFINITELY MORE THAN JUST USEFUL You cleared the notion of Agile development to a NOOB like me

This was a great explanation. I've worked in tech for many years, but I'm not technical. This cleared up A LOT for me! Thanks!

Thanks for this! The company I've been hired at uses Agile development and this explained how development there works perfectly!

I have read so many articles on what agile is, but none made it more clearer than your video, thanks.

thanks a lot, I'm prepping for an interview and not worked in a specifically Agile way before, but this has helped me realise that actually a lot of my experience falls under the Agile banner. Thanks!

Waterfall vs Agile. A balance of quality vs quantity. Got it. Thanks for the video

Agile Programming means: We write the code, you find the bugs.

I was required to read up about agile software development and the information on their site was way over my head. I found your video and it really makes sense. thank you =D

i love the way you illustrate your subjects. great job.

I have been looking different videos and documents to explain Agile. This one is the best!!! thank you so much!

Thank you for the explanation. We are developing code under Agile and ACCURACY is more important than SPEED and we are experiencing the results of developing software the wrong way.

Been thru a couple of interviews and been asked if I have had experiences with Agile! Well, turn out I have been using it for awhile without even noticing it. Thank you.

Thanks for giving examples, those really help to identify which are Waterfall and which are Agile.

agile is a set of common sense facts, packed into religion-like rules, and practiced through a ritual called scrum!

but isn't sprint exclusive to scrum? i though you would explain agile without refering to any specific framework

Thank you for the concise and definite explanation of Agile environment.

Agile is great way for leadership to feel like they are doing the right thing and blame the work force when it goes wrong. If you use someone elses strategy you get their results.

Exactly what i was looking for...

This was very well explained.

Not sure I agree with 7:14 about waterfall is better for Quality. Agile is when you either don't have your full requirements or your requirements change. If you take for example a safety system up front they have rigid non changing requirements and this does not lend it self so well to agile. Agile can improve your quality exponentially over waterfall as you are constantly testing and changing and of you add a CI (continuous integration) to the system you get even better quality.

thanks for making such an informative video and making me understand AGILE in just 9:20 minutes

Great video! Thanks.

Great video! Any chance you could add subtitles or closed captions?

Thank you. Extremely helpful.

Thank you! This was a clean explanation.

Fantastic! Great overview. Thanks Pat! 👍🙂

Amazing videos. Great explanation for a newbie like me to understand

Excellent - thanks

Doesn’t Agile just mean being flexible not following a “Standard method”. It doesn’t mean that the product has to be buggy or doesn’t work. I’m not trying to be confrontational I’m just trying to learn.

So with this explanation, is there a difference between agile and prototyping?

This helped me understand agile much better, and I have been working in software for almost two years 🤣

good job man!

Can you please enable captions on this video? It is being used in a course.

This is amazing!

Excellent explanation 👌

Hi this was very useful! But can you please explain to me if the Scrum Master is the Project Manager or not? It feels like he fits that role best, but if that can also be someone else, how would that person fit into the scenario of doing a project for a company?

Is waterfall a method or a model? Pretty stuck in an assignment... I have deducted that agile is method with representative models such as scrum or XP. Am I wrong?

Thanks for a great video!

Thanks for this video. It gave me a really good idea what Agile development is. My question: How do you determine what a minimum viable product is? I have an application to manage international travel for staff. I need a page to manage staff (crud), a page to create objectives, a page to add a trip with all details and a few more. Would a minimum viable product have to include all pages? Would a MVP for example be to create an app which allows you to add users (but not manage) and to add a trip and type in objectives manually?

Turn the volume up.

Thanks for this video

agile also work on banking or healthcare system but the integration test phase will become critical

Thank you soooooooooo much.

Agile is basically changing you rigid software dev team that takes 1 year to get a product up and running into a home garage based single software engineer who chunks out apps in less than 4 weeks.

Hey can u add a downloadable pdf so that we can read over and also I don’t get your assent

very helpful!

thanks but the volume is too low

this is a description of scrum not on agile. eg sprints have nothing to do with agility.

Well-explained video! So clear, succinctly and with great examples!

Perfect!

How about object oriented method?

what is the actual method?

im just watching this video for my coursework but i think it helped idk

You could have shortened that considerably by saying it’s being flexible. In fact the dictionary tells you that. Agile = flexible.

pls add subtitle

i still dont get it...

Hello guys, it was constructive.

I don't understand anything.

I dont know if this was your intention but you make it seem like agile is inherently shittier. If you have good testing Agile can be just as reliable as waterfall. Other than the agile manifesto, the difference is simply the lifecycle of when planning, work, and testing is done. In waterfall the planning is all done up front and the work and testing trickle down from it. In agile you plan, execute, and test in increments. I don't understand how that makes it inherently more buggy. Maybe the PM just isn't good as his job.

is it just me or this dude looks like Seth Rogen?

na. yea.

lmao I thought Agile was a coding language smh, I have a lot to learn..

that sounds like word salad

Too complex and not understandable explanation. Sorry

This was very helpful. I appreciated the contrast that you made with 'waterfall' because it made your explanation ever better. I also appreciate that you showed the strengths and weaknesses of each. Well done.

Amazing, thanks

I got a quesiton... Can we say that generally for applications that require a lot of secure protocols like payments and fund transfers, The Water fall method should be adopted, whereas for applications unlike the ones that can afford any bug in functionality, Agile method is fine... is it?

Thanks you for the information! well explained!

Thanks for the video... it would be great if you would add a this lecture into an article, if you already do it please share the link.

Hi, thanks for the video! well explained! I really like the pattern of the video, what video editor are you using?

thanks for the short helpful video

Oh gosh, what is the name of that incredible font? 😮

Thank you very much!!! I subscribed already!

Positively badass since the first two of my experience with cat; this will be a habit - damn!

Is this a part of business logic?

hope this helps. suggest you do a lot more reading. there are a lot of good book on software development. Microsoft Secrets is a good starting point for understanding agile and how it helps. when it comes to bugs there are a lot of good books that explain how to reduce development time by reducing bugs. you seem to think that quality control increases development time but typically it reduces it by 30-50% anyway my point is this stuff is very old and good solutions are described in books if you do a bit more reading.

Great video, I hope you also have a video on devops.

always refuse a Agile&Waterfal PM position - because their lack of planning and organization will become your priority everyday of the week - because the usual lack of product ownership, will make you the PM AND the Product Owner too - because you have no authority over large groups responsible for Product development and testing as a PM - the lack of responsibility required by a true Agile organization will make you over responsible and utterly underpaid as a PM & product owner - last but no least: while your managers get paid, you don't and ... you will wear too many hats with too many responsibilities and complete lack of control/leverage - cherry on top: if you don't deliver and just lick waterfall artifacts - you are not Agile. if you deliver and you are Agile, you have not filled in your artifacts They want control but with delivery - this is a never ending quest for access while secure. Basically you are painted as a victim and played like a violin. Enjoy !