As a complete software/code illiterate, these videos have been hugely helpful for me to learn basic definitions and keywords as well as the context to connect them to real-life situations. Thanks!
I love how you explained everything! You put it right down on laymans term, and made me realize that I've been doing Agile methodology all along, I just don't know it because it doesn't match the extremely technical descriptions of it from other sites and videos. Huge thanks to you, mister! \m/
This is solid stuff, thanks so much. I was struggling so much trying to read about Agile. 2 mins into the first video and I could tell I was saved. Thanks a lot, really!
+Georgy Louis There is a lot of discussion about documentation in Agile, and there is no clear recommendation on what documents should be used. This is primarily because agile isn't a strict methodology that dictates a set process. That said, the main idea seems to be to use documentation sparingly and only as needed, but certainly not to shun documentation completely. This is consistent with the agile manifesto, which urges agile practitioners to favor collaboration over documentation. In many small projects, a single specification or vision document is enough, but in larger projects it's foolish to think that communication and collaboration can take the place of documentation, so pragmatic decisions need to be made. What I see succeed a lot is for development to start with a high level vision document that explains the business case and overall use model of the application. This allows stakeholders to understand what they are building. From there, it's usually a good idea to document actual requirements, and depending on the scope this can be a document as well. On a very simple application, we'll sometimes load requirements right into the tracker as stories with details loaded right into the tracker. However, if a complex process requires flowcharts and data dictionaries, etc. it's not useful to squeeze it into a text area on some online system - a document is very convenient. Things like support and maintenance documents haven't changed much in the agile world, but the key talking about about documentation in agile seems to still be the golden rule: Try to use as little documentation as possible, but always use documents when necessary.
It's really great the way you explained Agile methodology ,but I wish you may explain more about it ,and how the flow of project changes by changing to different methodologies
What's the best place for we small business owners to post projects in the hopes of finding a talented developer to create a couple of websites for and not get ripped off?
Great post! Thanks for sharing. Here is my question. In agile development, do we still use the series of documentation : requirement analysis, specification, software architecture, Implementation, Testing, Documentation, training and support, maintenance. My assumption these documents are being produced in agile development, but they are being changed in each iteration. am I right?
Thank you Dave, My question is I am a dot net developer , should I learn Agile Methodology ? If it is mandatory to learn which module should I learn? could you please guide me.
+vamsi krishna Everyone interprets agile differently, and enterprise/larger companies tend to use a mishmash of agile and waterfall practices together - it's always different. Since most .Net gigs are still with larger companies, you might want to lean enough about agile to be conversant in the topic, but I wouldn't go further than that.
I liked it except for the point, "Agile Development Is a Methodology." I do so based on the article by Jeff Sutherland, co-creator of Scrum, who states in a 2013 MSDN article, "Agile development is not a methodology in itself. It is an umbrella term that describes several agile methodologies." (See, msdn.microsoft.com/en-us/library/dd997578(v=vs.120).aspx). I think it's more accurate to state that Agile Development is a practice that adheres to the values and principles of Agile ideology using one of the currently available methodologies. That's probably not as simple as you want, but it's accurate and will likely reduce or eliminate questions down the road.
Fair enough - but I don't want to understate the amount of people who mostly want a real-world, non-esoteric, simple explanation of what agile is about. Once the higher level methodologies, philosophies, or manifestos are introduced we've already lost that audience. So, this is just a simple way to get a simple idea of what agile development is about - in simple terms. If people want to learn more, there are plenty of resources who will provide long discourses about philosophy and ideology :)
I loved your video. It's short and precise. Would love to watch more videos like it. If you could show me a way to join developer teams, it really would really be great :D
I was developing an E-commerce web application using .Net framework for a school project. I have developed each module of these web app like the sign in , signup , homepage etc and tested it before moving to the next module. Is this considered as a practice for Agile methodology?
+Adarsh Jayakumar It would be. In a slightly more formal method you would assign a "bigness" points to each item you mentioned. Then you decide on a number of points to do in a given sprint. At the end of each Sprint you decide whether or not your project is ready to be deployed.
thanks for the explanation, I am kind of worried to spend a lot of time getting agail with no benefits for my career. I work as a recruitment specialist, but I really got into agail and I am very interested in getting to master this methodology do you recommend it ?
Suppose that an organization did not use processes that were designed and built to be agile, particularly when it comes to IS/IT technologies. Predict the impact of environmental changes on an organization financially, socially, and in terms of survivability.
I like the way you described it. It's the first time someone said it is time-boxed but you are totally right with that. I never thought about it before. My colleague at Zenkit wrote an article on our blog about that topic and I would love to here your thoughts about it: zenkit.com/en/blog/agile-methodology-an-overview/
Your point is well taken, but please consider the fact that many people have a tough time getting their heads around what agile really means and a concrete example can be helpful for them. Manifestos and philosophies are important, but not everyone understands what they really mean in practice. There are also agile experts giving mixed messages about what agile is, not to mention a lot of dogmatic practitioners with rigid interpretations of agile. There are plenty of videos that discuss the manifesto and philosophy of agile, yet we hear from people all the time who still struggle with the simple question, “what, exactly is agile development?” This video is for them!
As a complete software/code illiterate, these videos have been hugely helpful for me to learn basic definitions and keywords as well as the context to connect them to real-life situations. Thanks!
I love how you explained everything! You put it right down on laymans term, and made me realize that I've been doing Agile methodology all along, I just don't know it because it doesn't match the extremely technical descriptions of it from other sites and videos. Huge thanks to you, mister! \m/
THANKYOU for a clear explanation. Literally spent months trying to get a straight answer out of various people I know.
This is the second time today you've had a video that explained precisely what I was looking for. Thanks a lot for that!
Very clear and straight explanation. Thanks Dave.
+Javed Khatri Thanks Javed!
Great little video giving a clear underlying definition :)
Thanks Keelan, be sure to let us know if there is a topic you want us to cover.
This is solid stuff, thanks so much. I was struggling so much trying to read about Agile. 2 mins into the first video and I could tell I was saved. Thanks a lot, really!
Simple and clear explanation of 'Agile' terminology !
Great clear basic introduction to Agile.
A really clear and straightforward explanation! thanks, Dave!
+Diana Kulish Thank you!!
Great video. Like what you said at 02:08 about Agile being streamlined.
really nice, unlike other channels who often confuse
Thank you!
Nice Explanation
Now I clear of word "Agile"
This simplifies things a lot. Thanks.
Excellent Overview, brief, directive and very informative. A+++ Thanks for sharing.
Great presentation very clear information
Thanks .
Mohammed Abulsoud Thanks Mohommed. Let me know if you have any questions.
+Georgy Louis There is a lot of discussion about documentation in Agile, and there is no clear recommendation on what documents should be used. This is primarily because agile isn't a strict methodology that dictates a set process. That said, the main idea seems to be to use documentation sparingly and only as needed, but certainly not to shun documentation completely.
This is consistent with the agile manifesto, which urges agile practitioners to favor collaboration over documentation. In many small projects, a single specification or vision document is enough, but in larger projects it's foolish to think that communication and collaboration can take the place of documentation, so pragmatic decisions need to be made.
What I see succeed a lot is for development to start with a high level vision document that explains the business case and overall use model of the application. This allows stakeholders to understand what they are building. From there, it's usually a good idea to document actual requirements, and depending on the scope this can be a document as well. On a very simple application, we'll sometimes load requirements right into the tracker as stories with details loaded right into the tracker. However, if a complex process requires flowcharts and data dictionaries, etc. it's not useful to squeeze it into a text area on some online system - a document is very convenient.
Things like support and maintenance documents haven't changed much in the agile world, but the key talking about about documentation in agile seems to still be the golden rule: Try to use as little documentation as possible, but always use documents when necessary.
This is so well put together, thanks a lot!
Thank you!
Great video, now I know what to write in my dissertation, thanks!
Good luck with it, and let me know if you have any questions.
Sure will do, cheers
Very clear Explanation. Thank you Dave.
good
Great video with a clear explanation.
Great Explanation Sir..Thanks
Hi Dave. You did a good job on this video - thanks!
very good explanation
It's really great the way you explained Agile methodology ,but I wish you may explain more about it ,and how the flow of project changes by changing to different methodologies
Really great video, please keep up the good work :)
GIve this man an Oscar!
Thanks for vid, nicely explained!
At Last, I found it. Thanks This is a great video!
Great video Dave! Keep it up!
Thanks Emanuel!
Very informative and great explanation - thanks Sir!
Amazing explanation.
Very clear.
thanks, it was great help to understand the concept.
Well done!
that is a good video, it is clear and easy understand.
Thank your sharing :D
Such a great tutorial. This was really helpful. Thanks!
Short & clear .thank you
Simply to the point 👍
i actually enjoyed this
What's the best place for we small business owners to post projects in the hopes of finding a talented developer to create a couple of websites for and not get ripped off?
Great video. Thanks.
Great introduction to Agile.
+Steve Dunn Thanks Steve!
It cleared many doubts for me.
Great explanation
good one Dave
This video is amazing...
Very Good explanation
Great post! Thanks for sharing. Here is my question. In agile development, do we still use the series of documentation : requirement analysis, specification, software architecture, Implementation, Testing, Documentation, training and support, maintenance. My assumption these documents are being produced in agile development, but they are being changed in each iteration. am I right?
Great video, clear and informative. The video could be shorter without the intro and outro talk. Thanks a lot.
Great explanation!
Thank you!
Well Explained
assalamualaikum; kemo aso????
"Snake In The Grave" dekhso? (true story)
U should...u ll find this on my wall.
How to approach getting an Agile certification? especially if you are not working within project management but as a field engineer ?
Very informative, thank you.
Thanks for the food for thought.
+Josh Roa Thanks for watching Josh!
nicely explained many thanks !! excellent
great video!! thankyou.
Thanks. This was a good video
we love changes !
I know now, what to answer in my interview...thanx
kumar Kosgi Good luck!
Thank you Dave, My question is I am a dot net developer , should I learn Agile Methodology ? If it is mandatory to learn which module should I learn? could you please guide me.
+vamsi krishna Everyone interprets agile differently, and enterprise/larger companies tend to use a mishmash of agile and waterfall practices together - it's always different. Since most .Net gigs are still with larger companies, you might want to lean enough about agile to be conversant in the topic, but I wouldn't go further than that.
for me is the onion
Thank you.
couldn't have added more grace to it
Can Somebody explain time-boxing? How does it work it an example?
I liked it except for the point, "Agile Development Is a Methodology." I do so based on the article by Jeff Sutherland, co-creator of Scrum, who states in a 2013 MSDN article, "Agile development is not a methodology in itself. It is an umbrella term that describes several agile methodologies." (See, msdn.microsoft.com/en-us/library/dd997578(v=vs.120).aspx). I think it's more accurate to state that Agile Development is a practice that adheres to the values and principles of Agile ideology using one of the currently available methodologies. That's probably not as simple as you want, but it's accurate and will likely reduce or eliminate questions down the road.
Fair enough - but I don't want to understate the amount of people who mostly want a real-world, non-esoteric, simple explanation of what agile is about. Once the higher level methodologies, philosophies, or manifestos are introduced we've already lost that audience.
So, this is just a simple way to get a simple idea of what agile development is about - in simple terms. If people want to learn more, there are plenty of resources who will provide long discourses about philosophy and ideology :)
I like his to the point aproach
+Amit Patil Thanks Amit! There's enough blather about agile around, thought it would be good to have a simpler take on it.
thanks man!
I loved your video. It's short and precise. Would love to watch more videos like it. If you could show me a way to join developer teams, it really would really be great :D
I was developing an E-commerce web application using .Net framework for a school project. I have developed each module of these web app like the sign in , signup , homepage etc and tested it before moving to the next module. Is this considered as a practice for Agile methodology?
+Adarsh Jayakumar It would be. In a slightly more formal method you would assign a "bigness" points to each item you mentioned. Then you decide on a number of points to do in a given sprint. At the end of each Sprint you decide whether or not your project is ready to be deployed.
thanks for the explanation, I am kind of worried to spend a lot of time getting agail with no benefits for my career. I work as a recruitment specialist, but I really got into agail and I am very interested in getting to master this methodology
do you recommend it ?
It's definitely the trend. Everyone defines it in a different way, but it's hard to imagine that learning agile won't help your career.
Great basketball comparison
thx for sharing a great explanation
short and sweet
thank you, now i am confident on applying on a new job, btw you have a great face
Great job! I can only find Part 1 and 2 of your series. Are there more parts named "What is Agile Development (Part X)?"
u said agile is good for high level.waht do you mean by high level?
Thank you!
nice explanation.
Thank you!
The actual definition starts at 0:48
Hello from Georgia Tech good luck on your cs2340 exam tmrw kidos
TY DAVE
Suppose that an organization did not use processes that were designed and built to be agile, particularly when it comes to IS/IT technologies. Predict the impact of environmental changes on an organization financially, socially, and in terms of survivability.
i'm a freelance programmer, and i have absolutely zero idea that my methodology is actually agile XD.
I like the way you described it. It's the first time someone said it is time-boxed but you are totally right with that. I never thought about it before. My colleague at Zenkit wrote an article on our blog about that topic and I would love to here your thoughts about it: zenkit.com/en/blog/agile-methodology-an-overview/
One other interesting take on the article is available at axisbits.com/blog/Agile-Scrum-and-Kanban-Software-Development-Processes
even the presentation itself was kind of agile.
Could an Agile methodology be used to build a strip mall in your town?
+daniel mendoza Agile has become such a buzzword lately, I bet there's someone doing 'agile strip mall', yes!
Hii Sir
Dave Hacker.
Hii Good Morning
The disrespect for the manifesto is disheartening. Agile is a philosophy, period. The basketball analogy is contrary to the "methodology" argument.
Your point is well taken, but please consider the fact that many people have a tough time getting their heads around what agile really means and a concrete example can be helpful for them. Manifestos and philosophies are important, but not everyone understands what they really mean in practice. There are also agile experts giving mixed messages about what agile is, not to mention a lot of dogmatic practitioners with rigid interpretations of agile.
There are plenty of videos that discuss the manifesto and philosophy of agile, yet we hear from people all the time who still struggle with the simple question, “what, exactly is agile development?” This video is for them!
Can you clarify what is wrong with the basketball analogy?
My G great videos m9 shame tom howaRD Has Nothing between his ears
:D ám a hecker
First of all it is not a methodology. It's a Framework. You are confusing ppl. Please do not make videos on it.
If you are getting into semantics and debates about nomenclature, you're not the audience for this video :)
Wishful thinking.
i vant concentrate because this guy is wearing an earing and its bugging me..
Great explanation!
Great introduction to Agile
+Aslam Khan Thanks Aslam!