Ok, so as I watched this I was reminded of my time as a surface warfare office in the US Navy. Ship navigation is completely an agile approach! You have wind, currents and tides constantly taking you off coarse. You take hourly or at a minimum 4 hour positions using a variety of means and plot the coordinates on the navigation chart. Are you where you expect/want to be? Usually not...change course, change speed, etc. and take another position fix in an hour and see where you are on the chart. Keep doing this until you arrive at the planned destination!
Two images: A cheetah and a Gazelle? Which one is more agile? ... Cheetah = built for speed in a straight line Gazelle = built for ability to change direction quickly Learning: The gazelle is more agile and almost all cases wins - the cheetah focuses on picking out the young and the weak. Agile is about the ability to change direction quickly so you can experiment and adapt to changing market conditions (and avoid being eaten by the competition). I need to repeatedly remind people that Agile is not about going fast. Agile is about the ability to change direction quickly. Agile is a gazelle.
As much as I like the comparison, it's unfortunately untrue, the cheetah can use it's tail as a counter weight to make extremely fast and sharp turns :) ruclips.net/video/qukcc8wCxJo/видео.html
@@Asharas yes cheetah uses its tail to maneuver but important fact is its speed is limited. In average cheetah must catch gazelle in max. 17 seconds. After that cheetah must stop as its brain gets overheated whereas gazelle keeps its brain temperature stabile.
@@0247ozge than, I believe, gazelle is more Agile: "Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely." (Principles behind the Agile Manifesto agilemanifesto.org/principles.html)
Great video and analogy. The only comment I would make is that I kind of disagree when you say that for each stroke we get value because there is value only when you score a goal. Other than that I love the part on risks etc. The analogy I use is vacations: The waterfall way is using a pre-packaged tour. Everything is set at the beginning and even if things are not going as planned, there is very little possibility to adapt. So if you, as a customer, want to spend less time or more time somewhere, if it is raining during a planned outdoor activity, if, if, if... then well you might end up not being a satisfied customer. The agile way, you set a vision: destination, type of vacation (sports, cultural, beach, ...) and you fix your time and budget. You prioritise for the beginning of your trip the things you don't want to miss, your must haves. You may end up not doing everything you wanted to do, you may end up doing things you had not planned because once you are there you will adapt depending on what you see (not just what you had read). Your satisfaction of your vacations is not dependent on if you have done everything you had in mind before the trip (it does not depend on achieving the whole scope). And everything you do during your vacation is value delivered.
You're right, @Sophia; my analogy is more "Agile _project_ " than "Agile _product_ " - and we should be doing the latter. LOVE your holiday analogy; why haven't I thought of that before? Outstanding!
I ran across this analogy. You are a sailing ship, trying to get from Southampton to Boston. You can determine you position from the sun and stars, the direction and strength of the winds and currents. You know where you are, the current conditions, and where you want to get to. Your have a good crew; they are well trained, and can adapt the ship and sails to the conditions should they change rapidly, or if something unexpected happens. You can't predict your journey time at the outset, but you can dynamically make better estimates as you go along, checking your position and adjusting. You don.t worry about the past You have a strategy, good tactical doctrine, and no need of an operation plan.
I would add to that:You're halfway across the ocean and It turns out that there was a shipwreck at the entrance of the Boston harbor and it is now blocked, so you need to change course and go to Norfolk.
before we go into the analogy that you asked for, I just want you to know that I just found out about this channel this morning and subscribed immediately after, for your crisp and concise explanation of Scrum and Kanban. Okay, so I'd like to analogize Agile as indoor volleyball, and Waterfall as football (soccer). In indoor volleyball you only have 3 oportunity to hit the ball whenever it comes to your side of court, you and your team must try to defend, pass, and try to make killing deliveries in just 3 steps. After each time you deploy an attack, there's almost nothing you can do except to observe and anticipate what's coming before your opposition 'deliver' their 'feedback' attack on you. Speed of thinking and action is paramount in this game, if you need to change strategy you can only do that during timeouts (limited opportunity) and between sets (=product iteration).
This is brilliant. In New Zealand we played this game as kids but it was golf and you had to cross across the holes with the pencil line and work your way around the course. Sometimes you could even get a hole in one or two - if you were really good (I'm sure my brother cheated). This describes all the iterative development in Agile pretty well too. Thanks. Sue
Ok, I know you asked the question nearly 2 years ago but I really loved the pencil analogy so I would like to offer my analogy as well. Before seeing the video I felt like Agile is basically like most people's approach to life. You have set goals, but as things change along the way, you change what you want & so forth. A Waterfall approach might work for someone like a heir to a throne or a business. Their path is set, so they can move ahead with a rigid plan.
Specifically with Scrum (yeah I know you asked for agile), I've heard CURLING used as an analogy. The Developers are the rock (the stone) The Scrum Master is the sweeper, guiding, not forcing The Product Owner is the curler, or the stone pusher The Sprint is the "curling sheet" or the ice between point a and point b The Definition of Done is the curling target The Working Increment of Software is the score you get
Ha, this example actually taught me about curling by applying scrum as the analogy! Where I am from,no one seems to know what curling is, although we have a culring club in the region, I've yet to meeta member though.
Agile is demonstrated in full in the game of soccer. the team can shoot the ball overtime they have it straight at kickoff towards the opposing goal, with an AIM to score a goal. they can decide to play to score with small increments by kicking the ball around and making progress down the field to the opposing half, breaking their defence and scoring a goal. they coach can course correct on strategies, make changes by substituting players, until the game is over. this is my analogy of AGILE that i think may easily resonate with soccer loving fans in the our field or profession.
I like to use little wind-up racing cars. With the aid of two volunteers, both wind up their cars and aim to get them from point A to point B. The first person is instructed they can take as much time as they need to set up their car to make sure it goes in the right direction but they can not touch it once it's started moving. The other "driver" can move their car left or right but not move it forward or backward. Usually (with the aid of some knobbling of the first wind-up car), the first driver's car goes completely off course and misses point B while the other driver is able to course-correct to get their car to the finish line. The first car demonstrates a traditional all-up-front planning method like Waterfall. I use the second driver's method to demonstrate Inspection, Adaption and by asking the audience who saw the second driver "cheating" I can demonstrate Transparency. The 3 cornerstones of Scrum. Yes, I like Scrum but I've never learned Kanban!
Great analogy. I am trying to get into a project management career so am getting up to speed on these things. Liked the moment I saw St James'!!! Cheers!
This is a "trivial" analogy - which makes it absolutely SPLENDID 👏 Sometimes it's hard to describe agile's advantages to someone who doesn't have the agile mindset. I'm going to use this analogy in the future, thank you!
Imagine you’re in a forest, you start your journey with your feet and move forward looking for food and shelter, on the other hand you climbed on a horse as you thought it had the map of the forest and will land you in a good place but it can go wrong too 😃 thank you for the explanation
I am beginner in learning Agile concept and have already watched 3 videos was not cleared until I watched your video.. Precisely explained the concept..
I take an example from Sports itself. You are having a lovely day of cricket and chasing a good total. You are in front seat, plan is to keep run rate up without thinking about wickets much. but then you see black clouds coming in and you have to adapt to new condition. Now, you need to look after your wickets along with score as per DL method assessment.
Agile is an awesome perspective to have. If only companies would stop thinking agile is this rigid process that ends up burdening everyone with so much more work.
To briefly show what the agile method is all about, we will use a simple example. Since we live in a country near the frontline (in Poland), we can use a comparison to military rockets. Let's assume that the waterfall method is an ordinary unguided rocket. Before we launch the rocket, we need to designate the target of the attack. We calculate flight trajectories and make appropriate corrections related to wind strength and air humidity. Once we launch the rocket, there's nothing we can do. If the target of the attack moves a few meters, the rocket will miss the target. If anti-aircraft missiles appear, the rocket will be knocked down because it is incapable of evading the attack. Now it's time for agile, in our example it's a cruise missile. Before launching the rocket, the operator sets its target. After launch, the missile begins to maneuver, avoiding enemy air defenses. The rocket sometimes flies in a completely different direction than the indicated target, then returns to the correct course. The operator constantly sees the enemy target in the direction of which our clever projectile is flying. It may turn out that during the flight of the missile, the operator will see another, more attractive target and will direct the already flying missile there.
Lego’s You can build small working pieces, those can be added to other pieces, you can add pieces to strengthen what you’ve already built and remove other pieces not needed or that are cumbersome and replace them with more ‘agile’ pieces to finish your build. I’m new to agile. This is my day one.
Hi, Thanks for the video, I want to know if we can make a link between agile and travelling ? I want to create a conference topic about that metaphor but not sure from where to start?
People often talk about an aeroplane - off course most of the time but constantly adjusting... and able to change destination at a moment's notice. You might contrast that with a train. Could that work?
@@Developmentthatpays Thanks for your feedback, I wanted to combine my travelling adrevntures itself. Like planning the trip (planning the sprint) exploring the place to visit as much as I can although I don't know it before (like exploratory testing) ... My inspiration: medium.com/serious-scrum/travel-planning-is-a-nice-metaphor-to-help-explain-many-agile-ideas-ac5bf84f6fff?source=bookmarks---------1------------------
@@Developmentthatpays how about agile vs waterfall vacations? The agile vacation would be a road trip with camping along the way, carrying food and cooking equipment, having only a general destination in mind. The waterfall approach would be a fully planned tour with hotels, tourist spots and souvenir stops all scheduled in advance, with not much room for changes.
I appreciate these videos I used JIRA on my IT team at Bank of America like 2 years ago and I need to refresh myself for an interview I have. Thanks again
All your eggs in one basket. Filling the sack or basket with all of your eggs and walking to your destination. Bag bursts or gets wet, eggs drop and break. I you change sacks on the way or only deliver some at a time, then you have agile because you can always deliver.
The Gazelle is the target which can be seen as the user requirements. Now for the development process we can use large predator like lion or tiger to represent the plan-driven (waterfall) and the cheetah for agile. Cheetah has much higher likelihood to win.
Good analogy !! I liked it . May be sailing could bring another one. And yet another: a cannonball in oblique shot ( waterfall) vs. a guided missile (agile)
one more: professional photographers used to do a lot of previous preparation for "one shot" photography on expensive celluloid process (waterfall) .. Digital enables a try and improve iterative aproach (agile).
SO delighted that you mentioned photography: nearly two years ago I wrote an episode about getting my photos developed at the chemist ( yes, I'm THAT old!) - I'd forgotten all about it.
Hello you! :) I dont think that I have a agile analogy but Ive got some points. For me "agile" is like the "I" its formless. We are formless,we can be "good" or "bad" and both. We can be great or fail at things but we keep moving forward. Like Zen,we keep breathing. We breath life,we breath death and THATS the permernant that agile needs to have. Keep doing things. Just sit,learn - do things..have an enlightmend and then? Sit,learn and do things. The situation will change,the impediments will come but the experience will grow. "Just sit." - Nothing else. Out of this you will create velocity, you will create an environment,you will design everything you need. You will have agility without forcing it.
Yeah,how can you be agile if its only the "tool" you are working with? Then you "do agile" but "are" you agile? Thats the question that needs to be answers but not only from the dev.team also from a leader.
I think that question is unhelpful. Imagine you go to learn karate. On Day One, will you "be" karate? Of course not! Does that mean you should stop? To learn karate... Agile... anything... we have no choice to be "mechanical" in the early stages.
That is the hardest thing I think for people who are starting the journey. We hear about 'self-directed' and 'self-organized' teams all of the time. But, in my personal opinion, you need a good person to help the team understand the framework and what it means before they can be at that point of self-direction/organized. Now I'm not saying that you need to be directive yourself as a coach/mentor/scrum master to the point of telling people what to do, but you also cannot just come in, dump a bunch of stories and say "go for it" and expect them to be agile. You walk them through the process - some get it faster than others and you step back and let those help the others but are there to help them correct their form (going back to the karate metaphor). I thought I read about the four stages of learning and how it related to agile, but I can't find that article again.
@@Developmentthatpays can you cover other topics as well and explain in an innovative way lik this? - Topics such as customer success, Digital transformation, Cloud, etc.
256th comment. Perfect 2^8. Woo Hoo! Yes, agile is a response to uncertainty in design. It is sold as a method of certainty for management. Salaried employees (no overtime) work fixed, predictable calendar schedules (and therefore budgets) and produce predictable results. Mangers can put checkmarks in the schedule and budget checkboxes. Employees "commit" to finishing on time as the buy-in for doing the work. Copious amounts of overtime are expected before missing a schedule. A Product Owner oversees the process to make sure than business interests are primary. If work expands to fill all available time, then time can be shrunk to get any amount of work done. Theoretically. I suppose piece rate garment workers are the analogy. You get paid per piece no matter how much time it takes, handkerchief or wedding gown.
The anime/manga Initial D story revolves around the concept. In street racing, it's not how powerful your engine is. It's about how balanced the car your racing with is.
Another analogy is: LEGO! You build it piece by piece until you get what you wanted and sometimes what you wanted shifts to something else (especially if the client is a 3yo kid - he probably changed his mind about a car and now wants a car-spaceship.). But if something not right? Easy to fix. Please don't super glue your bricks when talking about a solid build using waterfall.
Great analogy! Maybe an analogy that actually represents a software product could make it more easy to apply in the real world. Like what would building RUclips be like in a agile vs waterfall approach
I played this game when I was in high school in Nigeria. I was really happy with the explanation, because you used what i could relate with. Now I understand what agile and waterfall methodology is. I am now a fan of yours.lol
Teach your customer what agile is and the benefits of agile. Show them what the cone of uncertainty is and give them full transparency as you work though the process. Also, explain to them story points, and value points and how you’re going to prioritize the value points towards the beginning of the product so at any given time once the value delivered is lower the customer can send the product (launch), or you can redirect some resources off of this product and onto another, therefore, lowering the sprint cost to the customer. Hope this helps
Waterfall - risking your entire bankroll on a sports bet. If you win, you win big, but if you lose, you're bankrupt. Agile - risking a portion of your bankroll on a sports bet. If you win, your bankroll grows, but if you lose, you've only lost a bit of your roll and you can still make future bets.
Let me see: So, the point is to reach an objective, no matter what, even if sometimes there might be a chance of a big-ass wrong movement. So you have to give your best to go to the correction move and go for the goal again, UNTIL you reach what you first aimed, in first place. It is an interesting analogy to what we SHOULD do to our lives, as in not waste time with stuff that is not related with our REAL goals. Cool! Greetings from Brazil =)
Let's race a hare against a tortoise, except the hare can only see the route from the starting line and then has to put on a blindfold for the race. The hare takes some extra time to plan before taking off. The tortoise takes off immediately, but goes more slowly. Who would you bet on to win the race?
OK so basically features are like fruit meeting when you have a fresh fruit that would be your highest party feature you don’t have to squeeze a very hard and you get a lot of juice or value and then wants to split squeezed that fruit there might be another fruit that comes along that’s easier squeeze I get more value from menu you don’t have to complete teachers to get maximum value and the goal should never be to completely drain the root of all it’s choose when it’s a huge amount of effort to get very little results
I have to say that I’m having a hard time staying subscribed to this channel. The last few weeks have been less about how to help people learn and execute proper software development practices and has felt like it’s more “Hey here’s a new video about my updated cheat sheet” or “Hey here’s a video about rehashing something I covered previously”. I love your previous content but lately (last 4-5 videos) it feels very repetitive and is causing me to lose interest.
I appreciate you taking the time to let me know. I can tell you that others have expressed similar sentiments. Over the summer, I had lots of ideas; alas, not all of them "landed" well.
Not every episode is right for every person. I really like this series as each episode is short and to the point. Some make me think, other are interesting and some are insightful while some may be a tad repetitive. But they're always short and sweet. I like the fact that Gary makes corrections and updates and that the series evolves. The question for Gary is where is he heading? My recommendation is to expand into the tools and methods for enabling the team. I believe that to truly make a team productive, simple useful tools are required. Another area is to look at the related roles, not just the development team, but the scrum master and how to coach. Then there is the product manager and his role which should include defining the requirements (functionality). A really giant leap is to dive into Nexus as the exoskeleton of scaled scrum development.
I've binge watched most, if not all, of your videos and I think at this point most of your subscribers have a good idea of what agile is. That said, it is a nice analogy. I think it would be nice to expand more on the ideas, linking back on your previous videos whenever necessary. I will post my analogy in another comment
Daniel - Agree that most subscribers have a good idea of what Agile is... but are they able to explain it to others? The intention of this episode wasn't to "teach my grandmother how to suck eggs"... but to provide a tool for "spreading the word". Does that make sense?
Great explanation, but I think I'll stick to the Mythical Man Month approach. 😂. But seriously, I feel like this methodology is something that IT Teams and Engineers are already doing in one way or another. I don't understand why we have to name it Agile or anything for that matter.
If agile is such a simple idea, why some authors write pages of books about agile? Do not get me wrong! I'm not criticizing your wonderful analogy. On the contrary, I criticize those cunning bastards. Time is money, after watching your video, I realized that I no longer have to read books for a method that I have already practiced every day. Agile means walking to the target with small increments. All long journeys start with a small step and agile continues with small steps.
You do raise a good point: if it (agile) is so simple... why the never-ending stream of books... podcasts... and video? For some reason, it made me think of dieting. It's, arguably, a much more straightforward thing than Agile: "Eat less. Move more." And yet there's no shortage of "column inches". We humans do tend to complicate things :)
Upbringing a child - A perfect agile - Can we plan for a child's live in a waterfall model from birth to education to profession to marriage to offsprings ! one at a time - have a baby - based on the characteristics displayed - dynamically adapt the best plan that suits the child -
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Grab a pad. Grab a pencil. You're armed and ready... to demonstrate AGILE!
Within a few seconds I understood more about agile than 35mins of other clips!! Thanks!!
Excellent!
Ok, so as I watched this I was reminded of my time as a surface warfare office in the US Navy. Ship navigation is completely an agile approach! You have wind, currents and tides constantly taking you off coarse. You take hourly or at a minimum 4 hour positions using a variety of means and plot the coordinates on the navigation chart. Are you where you expect/want to be? Usually not...change course, change speed, etc. and take another position fix in an hour and see where you are on the chart. Keep doing this until you arrive at the planned destination!
Two images: A cheetah and a Gazelle? Which one is more agile?
...
Cheetah = built for speed in a straight line
Gazelle = built for ability to change direction quickly
Learning: The gazelle is more agile and almost all cases wins - the cheetah focuses on picking out the young and the weak. Agile is about the ability to change direction quickly so you can experiment and adapt to changing market conditions (and avoid being eaten by the competition). I need to repeatedly remind people that Agile is not about going fast. Agile is about the ability to change direction quickly. Agile is a gazelle.
Like it! And I like this a LOT : "I need to repeatedly remind people that Agile is not about going fast". Nice one.
As much as I like the comparison, it's unfortunately untrue, the cheetah can use it's tail as a counter weight to make extremely fast and sharp turns :)
ruclips.net/video/qukcc8wCxJo/видео.html
I'll use your example in my assessment. I think this example yours can be in top 3 creative explanation of agile methodology.
@@Asharas yes cheetah uses its tail to maneuver but important fact is its speed is limited. In average cheetah must catch gazelle in max. 17 seconds. After that cheetah must stop as its brain gets overheated whereas gazelle keeps its brain temperature stabile.
@@0247ozge than, I believe, gazelle is more Agile: "Agile processes promote sustainable development.
The sponsors, developers, and users should be able to maintain a constant pace indefinitely." (Principles behind the Agile Manifesto
agilemanifesto.org/principles.html)
Great video and analogy. The only comment I would make is that I kind of disagree when you say that for each stroke we get value because there is value only when you score a goal. Other than that I love the part on risks etc.
The analogy I use is vacations:
The waterfall way is using a pre-packaged tour. Everything is set at the beginning and even if things are not going as planned, there is very little possibility to adapt. So if you, as a customer, want to spend less time or more time somewhere, if it is raining during a planned outdoor activity, if, if, if... then well you might end up not being a satisfied customer.
The agile way, you set a vision: destination, type of vacation (sports, cultural, beach, ...) and you fix your time and budget. You prioritise for the beginning of your trip the things you don't want to miss, your must haves. You may end up not doing everything you wanted to do, you may end up doing things you had not planned because once you are there you will adapt depending on what you see (not just what you had read). Your satisfaction of your vacations is not dependent on if you have done everything you had in mind before the trip (it does not depend on achieving the whole scope). And everything you do during your vacation is value delivered.
I thought the value was getting closer to the goal with every stroke.
You're right, @Sophia; my analogy is more "Agile _project_ " than "Agile _product_ " - and we should be doing the latter.
LOVE your holiday analogy; why haven't I thought of that before? Outstanding!
@Gary brief your educational and professional side. From where did you learn these?
I'm not really sure!
if you can teach it to a 10 year old, only then you know the concept properly. This is a masterclass
Love it! Thank you!
I ran across this analogy.
You are a sailing ship, trying to get from Southampton to Boston.
You can determine you position from the sun and stars, the direction and strength of the winds and currents. You know where you are, the current conditions, and where you want to get to.
Your have a good crew; they are well trained, and can adapt the ship and sails to the conditions should they change rapidly, or if something unexpected happens.
You can't predict your journey time at the outset, but you can dynamically make better estimates as you go along, checking your position and adjusting.
You don.t worry about the past
You have a strategy, good tactical doctrine, and no need of an operation plan.
PERFECT! Exactly what I was hoping for! Many thanks!
I would add to that:You're halfway across the ocean and It turns out that there was a shipwreck at the entrance of the Boston harbor and it is now blocked, so you need to change course and go to Norfolk.
Yes, exactly! Good addition.
before we go into the analogy that you asked for, I just want you to know that I just found out about this channel this morning and subscribed immediately after, for your crisp and concise explanation of Scrum and Kanban.
Okay, so I'd like to analogize Agile as indoor volleyball, and Waterfall as football (soccer). In indoor volleyball you only have 3 oportunity to hit the ball whenever it comes to your side of court, you and your team must try to defend, pass, and try to make killing deliveries in just 3 steps. After each time you deploy an attack, there's almost nothing you can do except to observe and anticipate what's coming before your opposition 'deliver' their 'feedback' attack on you. Speed of thinking and action is paramount in this game, if you need to change strategy you can only do that during timeouts (limited opportunity) and between sets (=product iteration).
Thank you for your message - glad you enjoyed the Scrum and Kanban videos.
Good analogy - like it!
Your pencil-football analogy hit the nail on its head. Great work!!
This is brilliant. In New Zealand we played this game as kids but it was golf and you had to cross across the holes with the pencil line and work your way around the course. Sometimes you could even get a hole in one or two - if you were really good (I'm sure my brother cheated). This describes all the iterative development in Agile pretty well too. Thanks. Sue
Ooo... I must give the golf version a go. 👍
Ok, I know you asked the question nearly 2 years ago but I really loved the pencil analogy so I would like to offer my analogy as well. Before seeing the video I felt like Agile is basically like most people's approach to life. You have set goals, but as things change along the way, you change what you want & so forth. A Waterfall approach might work for someone like a heir to a throne or a business. Their path is set, so they can move ahead with a rigid plan.
I like that analogy A LOT. - not least because I never would have thought of it. Love it!
Specifically with Scrum (yeah I know you asked for agile), I've heard CURLING used as an analogy.
The Developers are the rock (the stone)
The Scrum Master is the sweeper, guiding, not forcing
The Product Owner is the curler, or the stone pusher
The Sprint is the "curling sheet" or the ice between point a and point b
The Definition of Done is the curling target
The Working Increment of Software is the score you get
Like it! I'll put this one in the bank for a future episode.
Ha, this example actually taught me about curling by applying scrum as the analogy! Where I am from,no one seems to know what curling is, although we have a culring club in the region, I've yet to meeta member though.
Agile is demonstrated in full in the game of soccer. the team can shoot the ball overtime they have it straight at kickoff towards the opposing goal, with an AIM to score a goal. they can decide to play to score with small increments by kicking the ball around and making progress down the field to the opposing half, breaking their defence and scoring a goal. they coach can course correct on strategies, make changes by substituting players, until the game is over. this is my analogy of AGILE that i think may easily resonate with soccer loving fans in the our field or profession.
Very cool: the analogy works well.
5 min save my life with struggling with agile, great and easy explanation.
Best explanation ever. It's still good in 2021
Thank you very much. This is so simple to catch up and not waste any second.
Glad you liked it!
I like to use little wind-up racing cars. With the aid of two volunteers, both wind up their cars and aim to get them from point A to point B. The first person is instructed they can take as much time as they need to set up their car to make sure it goes in the right direction but they can not touch it once it's started moving. The other "driver" can move their car left or right but not move it forward or backward. Usually (with the aid of some knobbling of the first wind-up car), the first driver's car goes completely off course and misses point B while the other driver is able to course-correct to get their car to the finish line. The first car demonstrates a traditional all-up-front planning method like Waterfall. I use the second driver's method to demonstrate Inspection, Adaption and by asking the audience who saw the second driver "cheating" I can demonstrate Transparency. The 3 cornerstones of Scrum. Yes, I like Scrum but I've never learned Kanban!
Great analogy. I am trying to get into a project management career so am getting up to speed on these things. Liked the moment I saw St James'!!! Cheers!
Howay the Lads! And the very best of luck with your new career 🚀
This was an awesome analogy. Love it
Thank you! (I love that pencil!)
This is a "trivial" analogy - which makes it absolutely SPLENDID 👏
Sometimes it's hard to describe agile's advantages to someone who doesn't have the agile mindset.
I'm going to use this analogy in the future, thank you!
Sometimes trivial us good! 👍
I recently introduced my children to this game...played this growing up in india...we used it call it rocket!
Imagine you’re in a forest, you start your journey with your feet and move forward looking for food and shelter, on the other hand you climbed on a horse as you thought it had the map of the forest and will land you in a good place but it can go wrong too 😃 thank you for the explanation
Such a simple, beautiful example. Thanks!!
Thank you! I really appreciate that!
I am beginner in learning Agile concept and have already watched 3 videos was not cleared until I watched your video.. Precisely explained the concept..
Thank you! Glad you found the videos to be useful.
I take an example from Sports itself. You are having a lovely day of cricket and chasing a good total. You are in front seat, plan is to keep run rate up without thinking about wickets much. but then you see black clouds coming in and you have to adapt to new condition. Now, you need to look after your wickets along with score as per DL method assessment.
How do you charge the customer in Agile way of project development?
Powerful content, presentation, and delivery. Thanks a lot, Gary. Your voice is amazing.
Thank you!
How do we implement agile scrum method to new car development?
Agile is an awesome perspective to have. If only companies would stop thinking agile is this rigid process that ends up burdening everyone with so much more work.
brilliant analogy!!! Congrats!
Thank you! Much appreciated!
Thank you, I finally get it!
Wow, what an analogy!...
Glad you liked it!
The good thing about this simple analogy is that it also highlights a main negative of Agile too - it takes much longer to reach the goal.
+Mr Sammotube - Yes, I guess one of the messages is that it may take longer, but the chances of reaching the goal are increased.
+Kevin Krupp - You're another one that writes comments better than I write scripts. Excellent points well made.
+Kevin Krupp - Glad you liked the TDD v BDD episodes - and thanks for spreading the word!
great comment!
To briefly show what the agile method is all about, we will use a simple example. Since we live in a country near the frontline (in Poland), we can use a comparison to military rockets.
Let's assume that the waterfall method is an ordinary unguided rocket. Before we launch the rocket, we need to designate the target of the attack. We calculate flight trajectories and make appropriate corrections related to wind strength and air humidity. Once we launch the rocket, there's nothing we can do. If the target of the attack moves a few meters, the rocket will miss the target. If anti-aircraft missiles appear, the rocket will be knocked down because it is incapable of evading the attack.
Now it's time for agile, in our example it's a cruise missile. Before launching the rocket, the operator sets its target. After launch, the missile begins to maneuver, avoiding enemy air defenses. The rocket sometimes flies in a completely different direction than the indicated target, then returns to the correct course. The operator constantly sees the enemy target in the direction of which our clever projectile is flying. It may turn out that during the flight of the missile, the operator will see another, more attractive target and will direct the already flying missile there.
I am from India and I like the way you explain with pencil!!!
Glad you liked it!
SIMPLE, U WON A SUB
Welcome aboard!
Lego’s
You can build small working pieces, those can be added to other pieces, you can add pieces to strengthen what you’ve already built and remove other pieces not needed or that are cumbersome and replace them with more ‘agile’ pieces to finish your build.
I’m new to agile. This is my day one.
Like it! You're off to a flying start with your agile journey!
Thank you for this amazing and easy explanation!
Glad it was helpful!
Hi,
Thanks for the video, I want to know if we can make a link between agile and travelling ?
I want to create a conference topic about that metaphor but not sure from where to start?
People often talk about an aeroplane - off course most of the time but constantly adjusting... and able to change destination at a moment's notice. You might contrast that with a train. Could that work?
@@Developmentthatpays Thanks for your feedback, I wanted to combine my travelling adrevntures itself.
Like planning the trip (planning the sprint) exploring the place to visit as much as I can although I don't know it before (like exploratory testing) ...
My inspiration:
medium.com/serious-scrum/travel-planning-is-a-nice-metaphor-to-help-explain-many-agile-ideas-ac5bf84f6fff?source=bookmarks---------1------------------
@@Developmentthatpays how about agile vs waterfall vacations? The agile vacation would be a road trip with camping along the way, carrying food and cooking equipment, having only a general destination in mind. The waterfall approach would be a fully planned tour with hotels, tourist spots and souvenir stops all scheduled in advance, with not much room for changes.
No better explanation online!! Good job
I appreciate these videos I used JIRA on my IT team at Bank of America like 2 years ago and I need to refresh myself for an interview I have. Thanks again
Best of luck with your interview!
All your eggs in one basket. Filling the sack or basket with all of your eggs and walking to your destination. Bag bursts or gets wet, eggs drop and break. I you change sacks on the way or only deliver some at a time, then you have agile because you can always deliver.
Good analogy. Like it!
I am new to Agile and I enjoyed the analogy and especially the humor - great job
+Linda Trowbridge - Great comment! Thank you!
The Gazelle is the target which can be seen as the user requirements. Now for the development process we can use large predator like lion or tiger to represent the plan-driven (waterfall) and the cheetah for agile. Cheetah has much higher likelihood to win.
Like it!
Genuine analogy!
Thank you!
Good analogy !! I liked it . May be sailing could bring another one. And yet another: a cannonball in oblique shot ( waterfall) vs. a guided missile (agile)
one more: professional photographers used to do a lot of previous preparation for "one shot" photography on expensive celluloid process (waterfall) .. Digital enables a try and improve iterative aproach (agile).
Sailing is good. And I LOVE cannon ball vs. guided missile.
SO delighted that you mentioned photography: nearly two years ago I wrote an episode about getting my photos developed at the chemist ( yes, I'm THAT old!) - I'd forgotten all about it.
So I am ( THAT old! ) :)
Idoneos - :)
Hello you! :)
I dont think that I have a agile analogy but Ive got some points.
For me "agile" is like the "I" its formless. We are formless,we can be "good" or "bad" and both.
We can be great or fail at things but we keep moving forward. Like Zen,we keep breathing. We breath life,we breath death and THATS the permernant that agile needs to have. Keep doing things. Just sit,learn - do things..have an enlightmend and then? Sit,learn and do things. The situation will change,the impediments will come but the experience will grow. "Just sit." - Nothing else. Out of this you will create velocity, you will create an environment,you will design everything you need. You will have agility without forcing it.
True, true: the distinction between workman (workperson?) - and tool.
Yeah,how can you be agile if its only the "tool" you are working with? Then you "do agile" but "are" you agile? Thats the question that needs to be answers but not only from the dev.team also from a leader.
I think that question is unhelpful. Imagine you go to learn karate. On Day One, will you "be" karate? Of course not! Does that mean you should stop? To learn karate... Agile... anything... we have no choice to be "mechanical" in the early stages.
That is the hardest thing I think for people who are starting the journey. We hear about 'self-directed' and 'self-organized' teams all of the time. But, in my personal opinion, you need a good person to help the team understand the framework and what it means before they can be at that point of self-direction/organized. Now I'm not saying that you need to be directive yourself as a coach/mentor/scrum master to the point of telling people what to do, but you also cannot just come in, dump a bunch of stories and say "go for it" and expect them to be agile. You walk them through the process - some get it faster than others and you step back and let those help the others but are there to help them correct their form (going back to the karate metaphor).
I thought I read about the four stages of learning and how it related to agile, but I can't find that article again.
Great points beautifully made.
Very nicely explained 👍👍
Amazing presentation
Thank you!
@@Developmentthatpays can you cover other topics as well and explain in an innovative way lik this? - Topics such as customer success, Digital transformation, Cloud, etc.
256th comment. Perfect 2^8. Woo Hoo! Yes, agile is a response to uncertainty in design. It is sold as a method of certainty for management. Salaried employees (no overtime) work fixed, predictable calendar schedules (and therefore budgets) and produce predictable results. Mangers can put checkmarks in the schedule and budget checkboxes. Employees "commit" to finishing on time as the buy-in for doing the work. Copious amounts of overtime are expected before missing a schedule. A Product Owner oversees the process to make sure than business interests are primary. If work expands to fill all available time, then time can be shrunk to get any amount of work done. Theoretically. I suppose piece rate garment workers are the analogy. You get paid per piece no matter how much time it takes, handkerchief or wedding gown.
Brilliant analogy Gary.
Thanks, Roger. Glad you liked it!
@@Developmentthatpays love how you reply on videos from 4 years ago! 😀
I try my best 👍
Outstanding analogy!
Thank you!
Loved the introduction in the beginning about Newcastle united. Up the toons!!
The anime/manga Initial D story revolves around the concept.
In street racing, it's not how powerful your engine is. It's about how balanced the car your racing with is.
Like it!
Excellent.. I will share this with my team!
Don Nelson - Thank you! And thank for spreading the word - much appreciated.
Excellent!
Thank you!
Loved this analogy...
Glad you liked it!
Best and too realistic explanation 😀
Thank you!
Another analogy is: LEGO! You build it piece by piece until you get what you wanted and sometimes what you wanted shifts to something else (especially if the client is a 3yo kid - he probably changed his mind about a car and now wants a car-spaceship.). But if something not right? Easy to fix. Please don't super glue your bricks when talking about a solid build using waterfall.
LOVE IT! Not least because I LOVE Lego!
Very nice creative video...thanks
Great analogy! Maybe an analogy that actually represents a software product could make it more easy to apply in the real world. Like what would building RUclips be like in a agile vs waterfall approach
Good suggestion. I'll give it some thought.
Great. Loved it. Simple but very powerful.
Thank you!
I played this game when I was in high school in Nigeria. I was really happy with the explanation, because you used what i could relate with.
Now I understand what agile and waterfall methodology is.
I am now a fan of yours.lol
Good Explanation..But if I used Agile, How can I get profit if my client want a fixed cost for our project?
Estimate the number of sprints and add 50% and you will probably be very close
Teach your customer what agile is and the benefits of agile. Show them what the cone of uncertainty is and give them full transparency as you work though the process. Also, explain to them story points, and value points and how you’re going to prioritize the value points towards the beginning of the product so at any given time once the value delivered is lower the customer can send the product (launch), or you can redirect some resources off of this product and onto another, therefore, lowering the sprint cost to the customer. Hope this helps
Great analogy... Thanks for sharing it with the agile community.
Simply superb...
Many thanks!
Awesome metaphor.
Thank you!
Best definition !!!!!!
short but sure...i love this vid
Great analogy!
Glad you liked it!
Yes liked it!
first tech video that is very entertaining and interesting. Thank you!
Thank you! So glad you liked it.
Great explanation!
Nice analogy!
+Kumara K - Thank you!
Haha. I love this explanation. Thanks for sharing. 😀
Really glad you liked it!
Waterfall - risking your entire bankroll on a sports bet. If you win, you win big, but if you lose, you're bankrupt.
Agile - risking a portion of your bankroll on a sports bet. If you win, your bankroll grows, but if you lose, you've only lost a bit of your roll and you can still make future bets.
Nice one. I guess there's the potential for learning/adjusting between bets?
Pretty much! Learn from mistakes (agile) rather than go bust (waterfall)
😀
nice analogy.
Glad you liked it!
Fantastic explanation , thanks : )
Let me see:
So, the point is to reach an objective, no matter what, even if sometimes there might be a chance of a big-ass wrong movement. So you have to give your best to go to the correction move and go for the goal again, UNTIL you reach what you first aimed, in first place.
It is an interesting analogy to what we SHOULD do to our lives, as in not waste time with stuff that is not related with our REAL goals. Cool! Greetings from Brazil =)
Exactly!
Like explanation :)
Mr., great explanation, We Latinos say: "Clearer doesn't sing a rooster"
Like it!
I think this was made for yourself rather than the viewers but thanks for trying
Think there's some truth in that. Do you have a better analogy?
awesome
I love it!!
I'm so pleased!
Loved it 🙏👌🖖
Great! Glad you liked it!
Nice demonstration
+rajendra prasad - Thank you!
It wasn't.
Let's race a hare against a tortoise, except the hare can only see the route from the starting line and then has to put on a blindfold for the race. The hare takes some extra time to plan before taking off. The tortoise takes off immediately, but goes more slowly. Who would you bet on to win the race?
Like that a lot! Great stuff.
very well explained i thought.
Thank you!
Thanks, great vid!
You're welcome!
Features are like Fruit. Lmk if you want detail.
I do. I do!
OK so basically features are like fruit meeting when you have a fresh fruit that would be your highest party feature you don’t have to squeeze a very hard and you get a lot of juice or value and then wants to split squeezed that fruit there might be another fruit that comes along that’s easier squeeze I get more value from menu you don’t have to complete teachers to get maximum value and the goal should never be to completely drain the root of all it’s choose when it’s a huge amount of effort to get very little results
I was using voice to text apologies for the typos
Canny good like!
Wey Aye!
Nice Video!!
Carlos Navidad - Thank you!
I have to say that I’m having a hard time staying subscribed to this channel. The last few weeks have been less about how to help people learn and execute proper software development practices and has felt like it’s more “Hey here’s a new video about my updated cheat sheet” or “Hey here’s a video about rehashing something I covered previously”. I love your previous content but lately (last 4-5 videos) it feels very repetitive and is causing me to lose interest.
I appreciate you taking the time to let me know. I can tell you that others have expressed similar sentiments.
Over the summer, I had lots of ideas; alas, not all of them "landed" well.
Not every episode is right for every person. I really like this series as each episode is short and to the point. Some make me think, other are interesting and some are insightful while some may be a tad repetitive. But they're always short and sweet. I like the fact that Gary makes corrections and updates and that the series evolves. The question for Gary is where is he heading? My recommendation is to expand into the tools and methods for enabling the team. I believe that to truly make a team productive, simple useful tools are required. Another area is to look at the related roles, not just the development team, but the scrum master and how to coach. Then there is the product manager and his role which should include defining the requirements (functionality). A really giant leap is to dive into Nexus as the exoskeleton of scaled scrum development.
I've binge watched most, if not all, of your videos and I think at this point most of your subscribers have a good idea of what agile is. That said, it is a nice analogy. I think it would be nice to expand more on the ideas, linking back on your previous videos whenever necessary. I will post my analogy in another comment
Kevin, that's a cracking list of topics! Thank you so much. They're on the list!
Daniel - Agree that most subscribers have a good idea of what Agile is... but are they able to explain it to others? The intention of this episode wasn't to "teach my grandmother how to suck eggs"... but to provide a tool for "spreading the word". Does that make sense?
John Wick must have been agile with that pencil.
😂
Great explanation, but I think I'll stick to the Mythical Man Month approach. 😂. But seriously, I feel like this methodology is something that IT Teams and Engineers are already doing in one way or another. I don't understand why we have to name it Agile or anything for that matter.
made sense to me.. :D
Glad you liked it!
If agile is such a simple idea, why some authors write pages of books about agile? Do not get me wrong! I'm not criticizing your wonderful analogy. On the contrary, I criticize those cunning bastards.
Time is money, after watching your video, I realized that I no longer have to read books for a method that I have already practiced every day.
Agile means walking to the target with small increments. All long journeys start with a small step and agile continues with small steps.
You do raise a good point: if it (agile) is so simple... why the never-ending stream of books... podcasts... and video? For some reason, it made me think of dieting. It's, arguably, a much more straightforward thing than Agile: "Eat less. Move more." And yet there's no shortage of "column inches". We humans do tend to complicate things :)
"Eat less. Move more."... I think this is the best advice to cope with tausends of hypes and finding the real gems.
You're a secret Liverpool fan.
Upbringing a child - A perfect agile - Can we plan for a child's live in a waterfall model from birth to education to profession to marriage to offsprings ! one at a time - have a baby - based on the characteristics displayed - dynamically adapt the best plan that suits the child -