I wish TH-cam suggested me this channel 'Telusko' sooner. I'm not exaggerating but Reddygaru has always been breaking down information into comprehendable form for us to understand the contexts way better. Always kept it simple for us. Hats off!
You would not believe I was trying to understand Agile from my company's resources and was finding it difficult to understand and boring. I decided to learn it from Telusko and now I know what the whole damn thing is! Thanks Navin sir!
the main criteria to say who is an excellent TEACHER ?? that is "the listener should understand irrespective of his background " , u r THE BEST TEACHER i have never seen on youtube , ur videos will make someone to FALL IN LOVE WITH IT INDUSTRY . keep going bro. all the best and thanks a lot ...................................................................................................................!!! for ur reason behind a channel like this .
Thanks to you for making the video interesting. Most of the videos that has the topic from our syllabus went on so boring. You have just changed the game.
After watching few videos of yours I started liking IT and seems why I thought it's complex. Thanks for such beautiful examples which made understanding much more easy rather then just theory
You did a very good job of explaining agile. Probably the best i ever heard/watched. The Whatsapp example was a good scenario. Enjoyed watching this. Good work! Thanks.
Shanker, IT is very complex, do not let charlatans try to convince you otherwise, for if yuou get in it, you will have to lean so much, not only on the functional side (which IT only cares about the functional in a total of 45% the rest of the time is purely technical. A BA is a small, but crucial part of the IT domain, but if you cannot navigate in the technical side, then you cost twice as much as a BA that comes from the Technical side.... I strongly suggest, to enhance this with a very strong development of Analytical skills, but much more on logical skills, for it is in the logic (not just analysis), that will help you develop effective solutions, that will last long time (I can say that to this day, many of my old customers still use the core of what I recommended and developed (I come for the technical side and move up to the business side), so having both is the best and most successful way to differentiate yourself from the wannabes, which cost the company way too much money, because they develop haf ass, or non effective solutions.
Its very difficult to make me understand anything, and you did it in the first attempt 😂 thanks a lot! Having my Software Engineering paper tomorrow. Subscribed!
sir please make videos on software engineering. Because people like you are well experienced in this field and it help us to understand the whole process of software development. As you give examples of real life situation
Thanks a lot sir...You are really great...But one issue this time, the no. of ads are a hell lot of distraction. They were too much and break the whole flow of the video. There is no problem for ads to be in starting but I would suggest not to include them in between.... On the other hand You save lives!!!
In terms of software development, yes it is bad, but the model by itself is not bad by any means. It is still widely used in a lot of manufacturing and construction fields.
Really awesome explanation , anything that can't understood across web then i look for your video I think it's very easy to understand in your way of explanation I really love you methodology....♥️
thank you for explaining. i was afraid of agile and scrum before since they r new terms, but it turns out to be just what i have already done wrapped in new terms
Software developers need to respect the domain experts. Once the developers know the workflow, they start belittling the domain experts, this is true mostly of startups and smaller teams (of course not all programmers are like this) You cannot make a medical domain software without a doctor even if you know the entire workflow. Same for banking or geo science. You need a domain expert even when he has told you the entire workflow because when you get stuck, you will need domain knowledge.
I have a strong believe (not just by your age) that your exposure to Waterfall was extremely limited, for you state that requirement could not change, code could not change, that Sir is incorrect. Everything is subject to change, but, are you willing to pay for what the change will cost? Agile takes changes disregarding cost of change to the project, and disregard to delivery/completion of the project. Agile was the answer that Developers/Programmers had been looking for, since the fields of Business Analysts was inundated by "Analysts" posing as BAs. Analyst working as BAs did not underst that a BA is the "Bridge" between the Technical and the Functional side of the Business, and started focusing solely on the Functional but made a mess of the second half of the formula, for there was no technical influence that would give programmers/developer a clue as to what really was been asked of them to produce, but catching the blame that was pointed to them by the Analysts posing as BAs. First look at a fact, AGILE IS NOT A METHODOLOGY IS A PROCESS (at least in IT), for it to be a methodology all areas of the business needs to functioning in Agile environment/methodology, so comparing the two is like comparing apples to Oranges. Waterfall, a true methodology, not only allows for complete and detailed Requirement Gathering, and once completed, and approved by all parties involved, there was a possibility of three (3) possible changes, that would be considered, and only applied if a Full Change Management, Risk Assessment, Financial Study have been completed, and if the impact of the change would not change the on-time, on-budget delivery, then it would be added to the initial approved requirements, but up to three times. Anything over the third request for change would go in as a brand new add-on, or upgrade (versioning). The downfall, that many are seeing, is that changes continue to happen in an Agile environment, that prolong the finished product delivery, and budget. I am not saying that Agile process is not good, it is good, but not for everything. There are times when a Waterfall Methodology is applied, especially when gathering requirements, constructing User Cases (from which Test Scripts will come), QA, UAT, Pre-implementation testing (non live), live implementation in a secure site/server, and finally a full release of the new application to production servers. There are other times when dealing with upgrades, new small applications, versions, when Agile is the perfect tool., but for the most part, if BAs give themselves a brake and learn a bit more of the technical side of Requirement Gathering, Waterfall would still be the stronger tool, and Agile would be the most effective short term solution to smaller changes, or applications. There is only one organization that encourages Certifications, and one many that encourage them, specially for their own version of Agile Requirements/User Stories, but it is all for Money, so that's why Agile is the Defacto now, but is it really the most effective, yes! but for changes, upgrades, versioning and new smaller applications.
That’s the issue with the world, people start using & comparing the processes of 2 different industries. Waterfall is applicable for the industry where you need to have complete information about the final product & incomplete product cant be used either, like you can’t have a car with missing wheels or breaks or fuel tank etc, so you need to design the complete thing with all its components & one can’t say later to change any item in it as all the items are tightly coupled in the model. So waterfall is required here. Similarly one builds the house, it is not like today you will build one room & if needed you will build another room nearby. Or you will build 1-2 story building now, if needed you will add 1-2 stories later. No, as you have to lay the foundation accordingly & their one needs to be clear with the complete requirements. But software industry is ever changing & one can still use the incomplete software with minimum required features in it. So complete final design may not be required in the start but still many things are required in the start itself & that requires sufficient technical & business brainstorming to decide on the possible architecture. But nowadays architects/designers exploit Agile way to save their efforts. But still Agile methodology requires every phase present in Waterfall model. Only change is that you break the big set of requirements & unknowns into the current known set of requirements. Or what suggestion given in Agile, can be denied in Software waterfall. I have had arguments many times on the custom understanding senior people give & follow as per their comfort & that’s the wrong way to follow to build any product. So both these processes are just processes, its the issue with people mindsets while incorporating the process in their work. As I don’t remember if waterfall says documentation is more important than the working software or customer collaboration is not required or individuals are not important or no change can be made in between. Stopping here, as whole lecture can be given around these issues like people give on Agile & Waterfall.
sir Please also make lectures on retrofit Libraries like GET, POST, MULTIPART,PUT, etc for Android java or kotlin , I Like your videos very much you r perfect Guide to knowledge............ Thank you so much..
Sir you are very good teacher thanks for giving us such a good tutorial. I have one request for you. Can you please make tutorial on regex in java? Thank you
I wish TH-cam suggested me this channel 'Telusko' sooner. I'm not exaggerating but Reddygaru has always been breaking down information into comprehendable form for us to understand the contexts way better. Always kept it simple for us. Hats off!
Language and way of explaining is so nice that every person can understand.
You would not believe I was trying to understand Agile from my company's resources and was finding it difficult to understand and boring. I decided to learn it from Telusko and now I know what the whole damn thing is! Thanks Navin sir!
telusko is helping a lot to the community. I appreciate your hard work thanks for the video.
the main criteria to say who is an excellent TEACHER ?? that is "the listener should understand irrespective of his background " , u r THE BEST TEACHER i have never seen on youtube , ur videos will make someone to FALL IN LOVE WITH IT INDUSTRY . keep going bro. all the best and thanks a lot ...................................................................................................................!!! for ur reason behind a channel like this .
I am from non-IT background....but ur videos created interest for IT.
U explain in so simple language.
Thank you.
You are a good teacher, bcoz u make me understand the concept clearly with the good example. Nice work, and thanks for your videos
Thanks to you for making the video interesting.
Most of the videos that has the topic from our syllabus went on so boring.
You have just changed the game.
After watching few videos of yours I started liking IT and seems why I thought it's complex. Thanks for such beautiful examples which made understanding much more easy rather then just theory
I like your house of cards analogy, software and especially when developed with the waterfall method can feel like that.
Love this video, agile has been around for years but seems to be finally catching on
Very clear and to the point. I move through many videos but when i reach to your video, only then i understand any topic. 👍👍
Am still struggling to understand can you help understand it better 🙏🙏🙏
You did a very good job of explaining agile. Probably the best i ever heard/watched. The Whatsapp example was a good scenario. Enjoyed watching this. Good work! Thanks.
Shanker, IT is very complex, do not let charlatans try to convince you otherwise, for if yuou get in it, you will have to lean so much, not only on the functional side (which IT only cares about the functional in a total of 45% the rest of the time is purely technical. A BA is a small, but crucial part of the IT domain, but if you cannot navigate in the technical side, then you cost twice as much as a BA that comes from the Technical side.... I strongly suggest, to enhance this with a very strong development of Analytical skills, but much more on logical skills, for it is in the logic (not just analysis), that will help you develop effective solutions, that will last long time (I can say that to this day, many of my old customers still use the core of what I recommended and developed (I come for the technical side and move up to the business side), so having both is the best and most successful way to differentiate yourself from the wannabes, which cost the company way too much money, because they develop haf ass, or non effective solutions.
Its very difficult to make me understand anything, and you did it in the first attempt 😂 thanks a lot! Having my Software Engineering paper tomorrow. Subscribed!
This is foremost the best explanation of AGILE I have seen ..
Thanks man ...👍
Thanks
House of Cards is a good example of the process of Building Softwares
You have great teaching skills, you inspire and made a lot more easier who wants to learn from basic :)
Satya Nadella Lite!
Concept taught effectively! Nice video
sir please make videos on software engineering. Because people like you are well experienced in this field and it help us to understand the whole process of software development. As you give examples of real life situation
what an explanation Boss...! this is why I always Prefer to check TELUSUKO TH-cam.
Your lectures are so simple and clear..
I love the way you explained it. Thank you.
I could relate is with my current deliveries, Thanks Reddy Ji
Best short video for Agile 🙏 thanks
Point to point explanation in easy language.
You are so talented...amazing communication skills..a lay man can understand your video’s
bro you're going to heaven. you've saved me so many times
Starting explanation with the name of ur friend is very intersting.
Appreciate your efforts. Your are highly knowledgeable and have impressive explanation skills.
Best Explanation on Agile and examples are easy to understand .. Thank you
You are very good teacher, explain very clear and easy to understand, thank you
Your teaching makes me watch more videos of yours 👏👏👏
Great video. Very explanatory
No words to say...osam explanation....tq so much
We want best mechine learning tutorial from you with practical and explanation .I hope you to see this.
Agile is like waterfall put into each story!
you are the sole reason for the completion of my engineering sir, thank you a lot 😇😇
Thanks a lot sir...You are really great...But one issue this time, the no. of ads are a hell lot of distraction. They were too much and break the whole flow of the video. There is no problem for ads to be in starting but I would suggest not to include them in between....
On the other hand You save lives!!!
You are telugu peoples pride. Keep makin vids. Respect and love from east germany.
Excellent video...clear explanation..u got urself +1 in subscribers!
Thanks to simply explain Agile principles and values.
Thank you so much for this content-filled video. First time learning this, and I'm already feeling like a pro
Every Agile trainer's close friend is a rich man and start business. Same friend story for all trainers.
"That's a very big time" love this guy
Michael Homan marry with him
Thank you so much.
You are the best in this profession.
Really nice way of explanation 👌 👏 👍 Thank u so much.
Thank u for the clear explanation.
Nice explanation of waterfall and agile methods with good example. Thanks for sharing!
Crisp and Clear to the point!
Navin says "I'm not saying waterfall is bad!"
I'm screaming in my head "Yes it is bad sir!" :):)
LoL. Dear, he is stating that with reference to the context - Agile.
In terms of software development, yes it is bad, but the model by itself is not bad by any means. It is still widely used in a lot of manufacturing and construction fields.
I have understood this concept. Thanks for explaining so well ❤.
Thankyou for the upload 🙏
Hello sir...u explained very well...now my concepts are clear
Only video you need to understand Agile
Really awesome explanation , anything that can't understood across web then i look for your video I think it's very easy to understand in your way of explanation I really love you methodology....♥️
Understood agile and subscribed immediately
Thanks for your effort - helping tons of readers
Agile and scrum are not as simple as they are!!
bringing agile in the team itself takes some time.
Thank you! Super explanation
Great explanation ❤️
Great! well explained. Thanks!!
I am so happy why you are so good
Good explanation in a simpler way. thank you
thank you for explaining. i was afraid of agile and scrum before since they r new terms, but it turns out to be just what i have already done wrapped in new terms
Thank you brother …Crisp and clear
(telusko) .... telusukunnsm
You are so good in explaining. All the best:)
Gosh! Finally i understood it! Thanks
Verry clear explanation. Thank you!
Great Sir, well explained
I'm your new subscriber admin. Well explained.
thnku so much sir...your explanation is commendable....thanks a lot
Thanks for the wonderful explanation
Software developers need to respect the domain experts. Once the developers know the workflow, they start belittling the domain experts, this is true mostly of startups and smaller teams (of course not all programmers are like this)
You cannot make a medical domain software without a doctor even if you know the entire workflow. Same for banking or geo science. You need a domain expert even when he has told you the entire workflow because when you get stuck, you will need domain knowledge.
Thank you Navin.
Great explanation. Love the way you explained. Appreciated.
Thanks Sir... Once again reveal a new Technology.....
simple and very good explanation
it was a S/w Engineering concept...!
Great explaination as always
so clear and concise
Thank you! Very good and simple explanation!
indeed
I have a strong believe (not just by your age) that your exposure to Waterfall was extremely limited, for you state that requirement could not change, code could not change, that Sir is incorrect. Everything is subject to change, but, are you willing to pay for what the change will cost? Agile takes changes disregarding cost of change to the project, and disregard to delivery/completion of the project. Agile was the answer that Developers/Programmers had been looking for, since the fields of Business Analysts was inundated by "Analysts" posing as BAs. Analyst working as BAs did not underst that a BA is the "Bridge" between the Technical and the Functional side of the Business, and started focusing solely on the Functional but made a mess of the second half of the formula, for there was no technical influence that would give programmers/developer a clue as to what really was been asked of them to produce, but catching the blame that was pointed to them by the Analysts posing as BAs.
First look at a fact, AGILE IS NOT A METHODOLOGY IS A PROCESS (at least in IT), for it to be a methodology all areas of the business needs to functioning in Agile environment/methodology, so comparing the two is like comparing apples to Oranges. Waterfall, a true methodology, not only allows for complete and detailed Requirement Gathering, and once completed, and approved by all parties involved, there was a possibility of three (3) possible changes, that would be considered, and only applied if a Full Change Management, Risk Assessment, Financial Study have been completed, and if the impact of the change would not change the on-time, on-budget delivery, then it would be added to the initial approved requirements, but up to three times. Anything over the third request for change would go in as a brand new add-on, or upgrade (versioning). The downfall, that many are seeing, is that changes continue to happen in an Agile environment, that prolong the finished product delivery, and budget.
I am not saying that Agile process is not good, it is good, but not for everything. There are times when a Waterfall Methodology is applied, especially when gathering requirements, constructing User Cases (from which Test Scripts will come), QA, UAT, Pre-implementation testing (non live), live implementation in a secure site/server, and finally a full release of the new application to production servers. There are other times when dealing with upgrades, new small applications, versions, when Agile is the perfect tool., but for the most part, if BAs give themselves a brake and learn a bit more of the technical side of Requirement Gathering, Waterfall would still be the stronger tool, and Agile would be the most effective short term solution to smaller changes, or applications.
There is only one organization that encourages Certifications, and one many that encourage them, specially for their own version of Agile Requirements/User Stories, but it is all for Money, so that's why Agile is the Defacto now, but is it really the most effective, yes! but for changes, upgrades, versioning and new smaller applications.
U are wrong. Sir is right
@@rasikadeshpande4710 prove me worng, saying that I am wrong is lame, if you cannot back it up.
Just awesome ... Love it. Salute !!!
That’s the issue with the world, people start using & comparing the processes of 2 different industries.
Waterfall is applicable for the industry where you need to have complete information about the final product & incomplete product cant be used either, like you can’t have a car with missing wheels or breaks or fuel tank etc, so you need to design the complete thing with all its components & one can’t say later to change any item in it as all the items are tightly coupled in the model. So waterfall is required here. Similarly one builds the house, it is not like today you will build one room & if needed you will build another room nearby. Or you will build 1-2 story building now, if needed you will add 1-2 stories later. No, as you have to lay the foundation accordingly & their one needs to be clear with the complete requirements.
But software industry is ever changing & one can still use the incomplete software with minimum required features in it. So complete final design may not be required in the start but still many things are required in the start itself & that requires sufficient technical & business brainstorming to decide on the possible architecture. But nowadays architects/designers exploit Agile way to save their efforts.
But still Agile methodology requires every phase present in Waterfall model. Only change is that you break the big set of requirements & unknowns into the current known set of requirements. Or what suggestion given in Agile, can be denied in Software waterfall.
I have had arguments many times on the custom understanding senior people give & follow as per their comfort & that’s the wrong way to follow to build any product. So both these processes are just processes, its the issue with people mindsets while incorporating the process in their work. As I don’t remember if waterfall says documentation is more important than the working software or customer collaboration is not required or individuals are not important or no change can be made in between.
Stopping here, as whole lecture can be given around these issues like people give on Agile & Waterfall.
Nice explanation friend.
Great channel .
Thanks a lot, very informative video ❤
This was good...thanks !!!
Thanks a lot for explaining this so well.
I'm big fan of u r teaching
very good video on Agile. thank you!
sir Please also make lectures on retrofit Libraries like GET, POST, MULTIPART,PUT, etc for Android java or kotlin , I Like your videos very much you r perfect Guide to knowledge............
Thank you so much..
Super explanation sir
Who are watching this video in 2022 ..
We are late to know these things..
Very clear explanation Thanks a lot.
Agile is just like a Daily Serial......, and Water Fall is like Movie.....
Great explanation.Thanks Telusko! :)
Sir you are very good teacher thanks for giving us such a good tutorial. I have one request for you. Can you please make tutorial on regex in java?
Thank you
Thanks...except software where other applications of this Agile
thank you for making it easy to understand!! :)