HomeНаука и техникаRelated VideosMore From: SourceSeek

What is Agile Development (Part 1): What is Agile Development?

2314 ratings | 285352 views
“What is agile development?” It’s always been surprisingly hard to get a simple answer to this question. There are esoteric and convoluted descriptions of agile all over the web, complete with concentric circles meant to sum it all up into a simple concept, and yet that simple answer eludes us. To be fair, agile development methodology isn’t a simple thing. Sourceseek is a free service that handpicks software developers for your exact project needs. Get started here: https://www.sourceseek.com/get-started/ We’ll start with wikipedia’s agile methodology definition: From Wikipedia: Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle. The first sentence starts by saying that agile development is a software development methodology. A software development methodology is a set of practices and procedures that help a team get organized and build software. It’s not the software itself, it’s the rule-book for organizing the team. That first sentence goes on to describe an iterative and incremental development approach. This is a key concept, and if you only take away one thing about agile this is the one to take away. In agile, we do iterations (circles) where we plan, execute, then review the results so that we can refine the plan and start all over again. We love change, and we want as many iterations and feedback loops as possible during the project. At the end of that first sentence, wikipedia describes collaboration: This really just means that we emphasize partnership and collaboration, with each member of the team serving a specific role but everyone expected to be flexible and to work together. In agile, we love teamwork. The second sentence brings in the concepts of adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and rapid and flexible response to change. In this part of the definition, we see how it all comes together! I interpret this sentence like this: ● We are adaptive. We don’t plan it all at the beginning and then stop planning. We do iterations and we are adjusting the plan all the time. This is why agile is so good for product development, we change and improve as we learn. ● We love evolutionary development. This is essentially the same thing, we learn as we go and we adjust, refine, improve... ● Time-boxing. This basically means that we manage our project using set blocks of time, like days or weeks, and we try to get as much done in those time-boxes as possible. This is the reverse of managing features. We consider what features we can build next week rather than looking at a list of features and asking how long it will take to build them. ● Rapid and flexible response to change: this is critical, and along with ‘iterations’ is the core answer to the question ‘what is agile development?’. We move fast, we are flexible, and we are truly ‘agile’! This is our mantra - fast and flexible - say it again and again!! What is agile development? ● Agile is a way of managing software projects. ● Agile is iterative, and goes in repeated cycles instead of in a long list of steps.. ● Agile is super collaborative and team-oriented. ● Agile is adaptive, constantly changing and refining plans, and moves fast! In almost every project, the client has a harder time expressing what they want at the beginning, and it gets gradually clearer towards the end. The can be a frustrating experience as mid-project changes are pretty disruptive. Let’s try it in agile. 1) Client hires developers by the hour, day, or week. 2) Client describes what they want to the developers 3) Developers start making designs and programming the theme based on what they client thinks they want. 4) Developers show their progress to the client constantly, even every day, to make sure they are on track. 5) The client makes frequent changes and tweaks, always refining the plan and improving the result. The developer also has input and suggestions. 6) The team keeps going until the project is done.. It all sounds very good, and it can be, but the reality is that the agile development methodology requires a solid team of smart people who know what they are doing or it can be a train wreck. It also requires that the entire team (client included) be committed to an honest, forthcoming approach that emphasizes success for the client. SourceSeek is free for clients; we find you the best teams and the perfect match. It's that simple. SUBSCRIBE NOW FOR MORE OUTSOURCING VIDEO TIPS AND NEWS! https://www.youtube.com/subscription_...
Html code for embedding videos on your blog
Text Comments (131)
Ten Minute Tokyo 2 (12 days ago)
Wishful thinking.
Ferid Alibegic (2 months ago)
Please subscribe if u find my effort useful. Here's the Agile playlist on my YouTube Channel "Aspire - Crisp Tutorials": https://www.youtube.com/playlist?list=PLcxAz8Bj26q_B7AMsm-akG3NDP3YMRJ87
Noctumus (2 months ago)
This is the second time today you've had a video that explained precisely what I was looking for. Thanks a lot for that!
Hussain Akram (3 months ago)
Very informative and great explanation - thanks Sir!
Peter Rottenhoffer (4 months ago)
:D ám a hecker
SenseofDeath (5 months ago)
i'm a freelance programmer, and i have absolutely zero idea that my methodology is actually agile XD.
amusicated (7 months ago)
The actual definition starts at 0:48
mustang19ms (8 months ago)
This video is amazing...
Michael (9 months ago)
Great video with a clear explanation.
Samin Yeasar (9 months ago)
Thanks. This was a good video
Jazy G. (10 months ago)
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: https://zenkit.com/en/blog/agile-methodology-an-overview/
isoplayer (10 months ago)
short and sweet
Jason K. (10 months ago)
Great basketball comparison
imran qaiser (11 months ago)
How to approach getting an Agile certification? especially if you are not working within project management but as a field engineer ?
Personal Email (11 months ago)
Nice vid mate....tight, easy to understand, conceptualized well
Wei Ling Lin (11 months ago)
Great video, clear and informative. The video could be shorter without the intro and outro talk. Thanks a lot.
mark cadag (11 months ago)
thank you, now i am confident on applying on a new job, btw you have a great face
Greer Trefethen (11 months ago)
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!
Stephan Jensen (1 year ago)
Great job! I can only find Part 1 and 2 of your series. Are there more parts named "What is Agile Development (Part X)?"
anupam kakkar (1 year ago)
First of all it is not a methodology. It's a Framework. You are confusing ppl. Please do not make videos on it.
SourceSeek (11 months ago)
If you are getting into semantics and debates about nomenclature, you're not the audience for this video :)
Marwan Issa (1 year ago)
Simply to the point 👍
Jesupelumi Adetunji (1 year ago)
Such a great tutorial. This was really helpful. Thanks!
Mary Berry (1 year ago)
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!
tonix1993 (1 year ago)
GIve this man an Oscar!
David Lim (1 year ago)
Hello from Georgia Tech good luck on your cs2340 exam tmrw kidos
Ken Brenner (1 year ago)
Hi Dave. You did a good job on this video - thanks!
dedi supardi (1 year ago)
At Last, I found it. Thanks This is a great video!
Development That Pays (1 year ago)
Great video. Like what you said at 02:08 about Agile being streamlined.
Prabhat Tiwari (1 year ago)
Can Somebody explain time-boxing? How does it work it an example?
Jayaprakash Reddy (1 year ago)
even the presentation itself was kind of agile.
ruchit jain (1 year ago)
Great Explanation Sir..Thanks
Vicki (1 year ago)
nicely explained many thanks !!  excellent
Daniel Spajic (1 year ago)
Great explanation. Cheers
H.M. Rafsanzani (1 year ago)
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
Pertsa (2 years ago)
Thanks for vid, nicely explained!
caleb tan (2 years ago)
that is a good video, it is clear and easy understand. Thank your sharing :D
Richa Adhia (2 years ago)
good one Dave
Gudipati sai ajay (2 years ago)
u said agile is good for high level.waht do you mean by high level?
Vysakh Yathindradas (2 years ago)
Short & clear .thank you
Sorina Chirila (2 years ago)
thx for sharing a great explanation
Ilya Markin (2 years ago)
Cool video.I had been finding the video like this for a long time.Thank you for this.Agile is veru interesting and useful topic.Especially if you you manager the project.So in my turn I'd like to share with you https://www.cleveroad.com/blog/a-fresh-take-on-5-software-development-methodologies
Milind Nandanikar (2 years ago)
nice video on agile I found
Brian F. Schutt (2 years ago)
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, https://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.
SourceSeek (2 years ago)
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 :)
Diamond_markj (2 years ago)
i actually enjoyed this
Tasneem Shaikh (2 years ago)
Really great video, please keep up the good work :)
Charles Jesseniah (2 years ago)
couldn't have added more grace to it
Great explanation!
Sajeevan Mp (2 years ago)
Simple and clear explanation of 'Agile' terminology !
Scrum (2 years ago)
The disrespect for the manifesto is disheartening. Agile is a philosophy, period. The basketball analogy is contrary to the "methodology" argument.
AbdalHassan (6 months ago)
Can you clarify what is wrong with the basketball analogy?
SourceSeek (2 years ago)
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!
karthik raman (2 years ago)
really nice, unlike other channels who often confuse
SourceSeek (2 years ago)
Thank you!
Mr. Whoever (2 years ago)
This is so well put together, thanks a lot!
SourceSeek (2 years ago)
Thank you!
Tam Tran (2 years ago)
Excellent Overview, brief, directive and very informative. A+++ Thanks for sharing.
Ajay Menon (2 years ago)
This simplifies things a lot. Thanks.
Mohammed Karim (2 years ago)
Great clear basic introduction to Agile.
Yasir Choudhary (2 years ago)
Nice Explanation Now I clear of word "Agile"
vikrant singh (2 years ago)
thanks, it was great help to understand the concept.
drift318 (2 years ago)
i vant concentrate because this guy is wearing an earing and its bugging me..
Mark Johnson II (2 years ago)
Great video. Thanks.
Murali Mohan Reddy (2 years ago)
It cleared many doubts for me.
KamyFlex Gaming (2 years ago)
we love changes !
Ivano Sporitus (2 years ago)
What is 100% Agile: http://www.slideshare.net/ishmelev/agileeng
Delphine Kelly (2 years ago)
Very clear Explanation. Thank you Dave.
Ify Onwuamaegbu (2 years ago)
mrearlygold (2 years ago)
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?
Joe Ouellette (2 years ago)
Well done!
Merari G (2 years ago)
Very informative, thank you.
xoulZz (2 years ago)
Damas 68 (2 years ago)
Great explanation
Eido Askayo (2 years ago)
Dave Hacker.
renzschumi (2 years ago)
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/
Phil Adams (3 years ago)
THANKYOU for a clear explanation. Literally spent months trying to get a straight answer out of various people I know.
Ahmad Waseem (3 years ago)
Thank you.
Jim Chapman (3 years ago)
Hello. Thank you for an interesting video. I still cannot get what agile development is, everyone gives different definitions. Wiki says it is a set of principles in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams - https://en.wikipedia.org/wiki/Agile_software_development. I have always thought that it is always so - development companies consists of teams that work together, isn’t it so? I cannot see the difference. For example, here - https://magora-systems.com/mobile-application-developers-london/ - they provide development, design and post-launch services. Can I say that the practice agile development? I have used Scrum, here - https://www.smartsheet.com/agile-vs-scrum-vs-waterfall-vs-kanban they list a number of its disadvantages, including the fact that some Scrum projects can experience scope creep due to a lack of specific end date. Does it happen often? I would be glad if you answered to my questions.
look4faris (3 years ago)
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 ?
SourceSeek (2 years ago)
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.
Amazzal El-habib (3 years ago)
thanks man!
Emanuel Simón (3 years ago)
Great video Dave! Keep it up!
SourceSeek (2 years ago)
Thanks Emanuel!
Keelan Eeles (3 years ago)
Great little video giving a clear underlying definition :)
SourceSeek (2 years ago)
Thanks Keelan, be sure to let us know if there is a topic you want us to cover.
Nihal Muradoglu (3 years ago)
Bravo. Finally change is the only constant its tool is recycling ...you guys arrived ...humans did want to create and hold it on untill to the end....of..... But nature has the the most wonderfull recycling sytem... Dig on... Make it happen for writing goverment management... May be thats why uk do not have constutition but teams keep on running to the egg like sperms...nihal nicky muradoglu
milan tiwari (3 years ago)
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
Stephen Christian (3 years ago)
Couldn't have been clearer. So hard to find a straight answer to a question these days......Cheers
Adarsh Jayakumar (3 years ago)
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?
Aaron Montague (3 years ago)
+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.
Salman Salim (3 years ago)
Amazing explanation. Very clear.
Vamsi Krishna (3 years ago)
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.
Nicola Napolitano (2 years ago)
for me is the onion
SourceSeek (3 years ago)
+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.
Pr Sr (3 years ago)
Very Good explanation
Javed Khatri (3 years ago)
Very clear and straight explanation. Thanks Dave.
SourceSeek (3 years ago)
+Javed Khatri Thanks Javed!
Sales ITB (3 years ago)
A really clear and straightforward explanation! thanks, Dave!
SourceSeek (3 years ago)
+Diana Kulish Thank you!!
Amit Patil (3 years ago)
I like his to the point aproach
SourceSeek (3 years ago)
+Amit Patil Thanks Amit! There's enough blather about agile around, thought it would be good to have a simpler take on it.
Josh Roa (3 years ago)
Thanks for the food for thought.
SourceSeek (3 years ago)
+Josh Roa Thanks for watching Josh!
Aslam Khan (3 years ago)
Great introduction to Agile
SourceSeek (3 years ago)
+Aslam Khan Thanks Aslam!
Steve Dunn (4 years ago)
Great introduction to Agile.
SourceSeek (3 years ago)
+Steve Dunn Thanks Steve!
daniel mendoza (4 years ago)
Could an Agile methodology be used to build a strip mall in your town?
SourceSeek (3 years ago)
+daniel mendoza Agile has become such a buzzword lately, I bet there's someone doing 'agile strip mall', yes!
Mohammed Abulsoud (4 years ago)
Great presentation very clear information Thanks .
SourceSeek (4 years ago)
@Mohammed Abulsoud Thanks Mohommed. Let me know if you have any questions.
Syed Zaidi (4 years ago)
very good explanation
SourceSeek (4 years ago)
+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. 
Georgy Louis (4 years ago)
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?
WingsOfTruth (3 years ago)
Mr Irrepressible (4 years ago)
nice explanation.
Dave Hecker (4 years ago)
Thank you!
TheSuperstition95 (4 years ago)
Great explanation!
SourceSeek (4 years ago)
Thank you!
Andre Simones (4 years ago)
I think it's critical to mention that every Agile methodology/practice exists to satisfy the Agile values and principles listed at http://agilemanifesto.org/.  
SourceSeek (4 years ago)
Absolutely that is a great point. thanks, Andre
Ben Ruiz (4 years ago)
Well presented.
Ahsan Habib (4 years ago)
Well Explained
K. M. Sharif Ahmed (4 years ago)
assalamualaikum; kemo aso???? "Snake In The Grave" dekhso? (true story) U should...u ll find this on my wall.
aruna s (4 years ago)
great video!! thankyou.

Would you like to comment?

Join YouTube for a free account, or sign in if you are already a member.