great walktrough I am at a Itil4 course and they failed to explain what is it without talking over our heads with fancy words. This video has great examples and easy to understand
The main advantage that your video possesses is the example with which you started your explanation. It was easily to understand the process in reference to the example.
Excellent. Lucid and clear explanation of something that appears to have so many different meanings to engineers today. Suggest you also cover SRE alongside this one on DevOps
Thank you for this video, as for ideas about another video: Maybe some advice on the following: Often I have trouble convincing clients to go the agile route. If they come to me and say, I want you to build a car. And I say, we are going to build you a skateboard first, then a scooter, then a bike, etc etc - then they say "Ok I understand that, but I already know that a skateboard and a bike wont work, please don't waste time building and releasing software that meets some of my requirements, I want you to build something that meets all of my requirements". How do I sell this methodology? Personally, I agree that this method delivers features faster and will result in a better product, but I don't think it is cheaper for the customer, in fact I think it is just as expensive if not more expensive. expensive.
Hi Rowan, This is quite a small topic to make a video on, but here's a special note from Ahmad for your query: "While Agile methodology is "the way to go" for most software development teams today, it cannot be considered as a "silver bullet" (an answer for all development requirements). That being said, the Waterfall model is still being used where it fits. If any or all of the following conditions are true, the Waterfall model might be a better fit: If the requirements are clear from the beginning and they are not subject to any changes till the final product is built. If the technology used to build the product does not change frequently (compare a language like C or C++ to JavaScript frameworks and Node.js modules) If all the resources and expertise required to build the project start to finish are available. If the product is not dynamic in nature (does not require frequent updates and will not be installed in an environment that requires recurrent changes). So, to answer this client, it all depends on the nature of the product they are about to build. And while the skateboard or the scooter is not a car, it is still a "minimal viable product". It gives the client an idea about what the end product might look like. It's gonna have wheels, that's for certain. So, he can add his comments early enough before it becomes a car while he was thinking of a jet plane or a rocket! I hope this answers the question and, again, there is no right or wrong way of doing things. There is the "most suitable" for the situation at hand. And Rowan, i'm not sure how the Agile method is going to be more expensive than the Waterfall? in all cases you will write code and build a product. It's the stages that will go through, the rules that you will follow and the client engagement that differentiates one method from the other. Cost was never a difference." We hope this helps!
For the next lecture: How about we get a little run down or a walkthrough over the process behind DevOps using tools that you've mentioned here in this lecture. P.S: I 've leasrned a lot about DevOps in this lecture; Thankyou So much.
Hi Talha, I think to get what you're looking for, the best place would be our Kickstarter project: kck.st/2HekFLk But yes, we will try making short tutorials for it here as well. We're glad this video was helpful, subscribe for more!
great walktrough I am at a Itil4 course and they failed to explain what is it without talking over our heads with fancy words. This video has great examples and easy to understand
The main advantage that your video possesses is the example with which you started your explanation. It was easily to understand the process in reference to the example.
This was excellent. It's shocking how bad some content on here is. This stands out massively. Thank you!
Salut.
C'était une excellente vidéo sur le "nouveau" paradigme 'DevOps'...
Merci à l'intervenant et merci à EDUONIX.
Ciao ;)
Great video!
Good examples for agile life cycle, simple and clean Thanks man!!!
Hi Vignesh, we're glad the video was helpful. Subscribe for more!
Scooter and Bicycle don't meet the basic requirement of 4 wheels you mentioned in the first iteration.
Very nice video. Enjoyed it
Hi Simone, glad you liked the video! Subscribe for more!
Nice break down of DevOps, looking forward to more on DevOps
Thank you Gerso! Subscribe for more insightful tutorials!
Excellent. Lucid and clear explanation of something that appears to have so many different meanings to engineers today. Suggest you also cover SRE alongside this one on DevOps
Hi Draghuna, thank you! New suggestions are always welcomed! We shall look into it. Subscribe to stay updated.
Thank you!
You're welcome Paulo. Subscribe for more DevOps videos!
Thank you for this video, as for ideas about another video: Maybe some advice on the following: Often I have trouble convincing clients to go the agile route. If they come to me and say, I want you to build a car. And I say, we are going to build you a skateboard first, then a scooter, then a bike, etc etc - then they say "Ok I understand that, but I already know that a skateboard and a bike wont work, please don't waste time building and releasing software that meets some of my requirements, I want you to build something that meets all of my requirements". How do I sell this methodology?
Personally, I agree that this method delivers features faster and will result in a better product, but I don't think it is cheaper for the customer, in fact I think it is just as expensive if not more expensive. expensive.
Hi Rowan,
This is quite a small topic to make a video on, but here's a special note from Ahmad for your query:
"While Agile methodology is "the way to go" for most software development teams today, it cannot be considered as a "silver bullet" (an answer for all development requirements). That being said, the Waterfall model is still being used where it fits. If any or all of the following conditions are true, the Waterfall model might be a better fit:
If the requirements are clear from the beginning and they are not subject to any changes till the final product is built.
If the technology used to build the product does not change frequently (compare a language like C or C++ to JavaScript frameworks and Node.js modules)
If all the resources and expertise required to build the project start to finish are available.
If the product is not dynamic in nature (does not require frequent updates and will not be installed in an environment that requires recurrent changes).
So, to answer this client, it all depends on the nature of the product they are about to build. And while the skateboard or the scooter is not a car, it is still a "minimal viable product". It gives the client an idea about what the end product might look like. It's gonna have wheels, that's for certain. So, he can add his comments early enough before it becomes a car while he was thinking of a jet plane or a rocket!
I hope this answers the question and, again, there is no right or wrong way of doing things. There is the "most suitable" for the situation at hand.
And Rowan, i'm not sure how the Agile method is going to be more expensive than the Waterfall? in all cases you will write code and build a product. It's the stages that will go through, the rules that you will follow and the client engagement that differentiates one method from the other. Cost was never a difference."
We hope this helps!
Thanks very much, your response is very helpful!
You're welcome! Glad we could help.
For the next lecture: How about we get a little run down or a walkthrough over the process behind DevOps using tools that you've mentioned here in this lecture.
P.S: I 've leasrned a lot about DevOps in this lecture; Thankyou So much.
Hi Talha, I think to get what you're looking for, the best place would be our Kickstarter project: kck.st/2HekFLk But yes, we will try making short tutorials for it here as well. We're glad this video was helpful, subscribe for more!
Nice! Thanks!
You're welcome, subscribe for more!
Cool
I am first