Yeah right. All this bad stuff is inherent to waterfall (including the golf). I've never worked on a successful Agile project. Waterfall has been pretty much a slam-dunk every time. People who think about what they do before doing it tend to be successful. Waterfall is like having a blueprint before you build a house. Agile is like just hiring contractors and telling them to go at it.
Rusty developed work based depression shortly after this video, he couldn't handle the pressure, his wife didn't care when he tried to talk to her about it and his mother developed an illness. Rusty had a lot on his plate, then one day he was browsing youtube while at work and found a video called "Agile vs. Waterfall: A Tale of Two Teams" based on him, he felt irrelevant and, later that day, killed himself with an, ironically, rusty knife. THIS VIDEO IS CRUEL!
Let me get this right, while in the Waterfall methodology the client is rafting, in the Agile one, the client is holding an arm full of documents faking a smile :-?. I think the client will prefer rafting.
Very Nice video, thanks a lot. Agile is impressive but I have little confusion, how the budget will decided after finishing the project? It might be like (total hours needed to finish the project X Rate per hour) as clients get updates after 2 weeks ???
@zakiur81 Yes, your assumption/question can work well. $/hour/person/sprint is a logical way to develop contracts. Good agile teams can clearly demonstrate to the client, in advance, their velocity and capacity so that the client is able to predict the cost of their relationship over many cycles.
Imo this is a pretty poor video, as it doesn’t really present the pro's and con's of either methodology. Which are present for both styles! Simply put, the team needs to fit the methodology, the methodolgy needs to fit the product. If the three are not in sync then you will always have an unhappy customer irrespective of the team, quality or methodology.
unfortunately, this "SCRUM" and "AGILE" crap is just that: crap. it is just an excuse for managers to continuallly change the requirements and slow down production. having a solid plan at the beginning saves time and money and keeps developers from wanting to choke their managers
OneMoreYear....I don't have a problem mate, I know where to find hard information on software methodologies. My criticism of this presentation is that it paints a very idealistic picture of the agile methodology but without sufficient contextual information to make it credible.
This video is rubbish. It tells us nothing concrete. I was hoping to hear about how much money/time was saved by using one approach vs another. Instead we get motherhood statements. IMO...agile is fine for many projects but the lack of documentation can lead to tricky maintenance risks/costs down the road.
Awesome video that uses blantant imagery about difference between two styles. Both approach can work but agile can adapt. It starts producing something right away. Its is about iterations of product which is code word for innovation.
Agile solves all problems. Even Boeing uses Lean. The people who keep saying that the answer is usually a mix are the people responsible for all the failed projects in the Standish Report. But please never compare building projects, or even electronic projects (such as Nasa and airforce projects) with software projects. They are different things and should be treated as such. For software projects, Agile is the only way to fly.
I had to press the dislike button I'm afraid, this is so biased that I don't know whether it's funny or sad. I'm a big proponent of Agile because short cycles are insurance against many of the major software disasters we know, but in real life major software projects aren't one or the other. I've been in this industry for 20 years, now I'm overseeing security for a solution of 150 (growing!) components by 20 teams. Some working in silos - doh - shouldn't happen, right? Maybe I'm just too old...
It is hard to do a complex project 100% in Agile and neither company do that. So the solution is based in a mix of "ideologies". Personally i think the main problem with Agile is that, to determine the working hour is more a "i am estimating that.." rather a exact science.
A ludicrous portrayal of waterfall, clearly interpreted by zealots trying to start a religious war. The correct answer is determined by the project, and both methodologies have strengths and weaknesses.
Play to the strengths of each methodology, and realize that the weaknesses are simply the cost of acquiring those strengths.
I love when people try to make the claim that one way is the solution for all for your problem. Nothing in the world works that way. Each development methodology has is pluses and minuses and work for different types of projects and teams. The trick is finding the one that works for your situation. Process should work for the team not the inverse.
@VigenToT You're right, I probably don't understand what "Agile" means, but I bet there is a week's course I can sign up to for $30,000 that will line the pockets of High Priests Schwaber, Fowler et al. I'm very sure it will teach me exactly what the latest fashion is regarding whacky americanised terminology used by middle-management fad loving drop-outs to re-brand common sense and well-documented engineering concepts that have been around since the early part of the last century.
there is no need to "line the pockets" of anybody if you want to learn and practice Agile. i am quite well in Agile and all i learned by myself. Also, for many year i have been practicing waterfall as Project Manager. now i can say agile is an excellent method to adopt for fast changing, risky projects. if you are a construction project manger, then go ahead and use waterfall, but in IT projects waterfall is a complete failure.
there is no need to "line the pockets" of anybody if you want to learn and practice Agile. i am quite well in Agile and all i learned by myself. Also, for many years i have been practicing waterfall as Project Manager. now i can say agile is an excellent method to adopt for fast changing, risky projects. if you are a construction project manger, then go ahead and use waterfall, but in IT projects waterfall is a complete failure.
@VigenToT What many disciples of Schwaber fail to realise (yourself being a good case in point) is that "Agile" and "Waterfall" are exactly the same model, but using extreme values for the parameters in this model. The Agilist have hijacked and are attempting to brand engineering concepts that preceded this "movement" by 100+ years. On top of that, throws in branded terminolgy for already recognised and understood entities such as "team", "manager", "architect" and "release".
@VigenToT Oh and by the way Agilists..."Kate" isn't a real person, she is fictional. Back to reality for you all!...a reality that requires one has scientific talent to be sucessful. Spouting buzzwords coined by the Agile priest just doesn't cut it!
There are no facts here. Nice story though. I'd like to share with you another story based on using scrum (on many projects) where the projects have slipped several sprints and the product quality is very low, oh, and not once have I seen the customer on site and able to answer developer questions. There are aspects of agile that I like but generally (in my experience) it's a tool used by managers to obtains their metrics and micro manage development.
I am in an agile process now, and it's chaos. The code is a mess. There is no documentation. Specs are unclear. Nobody knows where we stand. In short: it's pandemonium. Everybody's just hacking their way through those "story point" cards or whatever bullshit they call it this time. The rest of the time is wasted on "story planning" or "retrospectives" or whatever. It's like trying to build a house on quicksand.
@MomoTheBellyDancer Obviously you are not using it right. Better talk to the customer and show them almost weekly a new prototype. That would help to focus.
Great video and very funny.. I appreciate this approach to training. I am tyhowardthepmcoach(com) I invite you to join ghostrade a new generation commerce portal founded by PMI Award Winning Ty Howard, PMP (and CIO Magazine Leader's to watch). I invite you to join Ghostrade(com) to witness the fruits of labor in regards to PM work and strategic planning.
I ahte agile and everything it stands for. We used to call it "quick and dirty". The worst think about it is the swearing at meetings. It is all very unseemly.
This is terrible distortion. Without Rusty, Kate would be nowhere. Henry Ford was a Rusty. Caesar, Napoleon and Alexander were Rusties. They planned things. Beethoven, Schiller, Einstein and Shakespeare were Rusties. They all used a Waterfall type methodology. What has Agile given us? Lady Gaga, Justine Bieber and the Global Financial Crisis?
Agile may be young and trendy against the old fashioned and staid methods. The great things of beauty in the world were not built by Agile methods.
@SupBA the great things of beauty in the world cost a lot to keep "great" and "beautiful" - agile means future proof. if Ford was a kate, his assembly lines would be the best in the world by now. but they're not. they make Fords.
A very nice video comparing horses and pears. I suspect this has been made by somebody who has never used either of the methods in practice in many projects. Methods don't work, people work, with the right devised method for the project at hand. Scrum is a nice way to do some work, but not for any (IT) project, or any type of work.
It's only a matter of time when the new films arrive with: "In the old days we did waterfall, RAD, SCRUM, but now we have finally fould the right method: URG!" ...
you can always upload this kind of presentation at Slideshare with out converting them to flash. Slideshare will do it for you and with a better navigation.
you can always upload this kind of presentation at slideshare with out converting them to flash. Slideshare will do it for you and with a better navigation.
I work in a scrum team and I can't say that I'm the happiest person! The problem is not the methodology itself, but the people and their natural flaws. Selforganized works well when you have a small group of very commited persons. In a big, distributed organization it doesn't work that well. I'm working in agile for two years and the amount of "real", sellable work doesn't impress.
@AliceDamnation, pause the above video at 6:55. Sounds like no action was taken in two years for this critical step. Scrum will expose all the natural flaws. Sometimes it means pointing out these flaws, perhaps making a change. Other times, it means making a tough decision like letting someone go.
Oh wow. Propagandizing a dev life cycle methodology using cliches & stock photos. Did it ever occur to anyone that Agile formalizes what a great many departments have done for ages anyway, that they improvised processes that worked for them & delivered successful systems? Propping up strawmen RAD problems won't dismiss the salient point that RAD & cyclical Waterfall were progenitors to Agile? To the old farts Agile looks like yet another way to SELL something new & groovy (just like this vid).
Oh wow. Propagandizing a dev life cycle methodology using cliches & stock photos. Did it ever occur to anyone that Agile formalizes what a great many departments have done for ages anyway, that they improvised processes that worked for them & delivered successful systems? Propping up strawmen RAD problems won't dismiss the salient point that the RAD concept is a progenitor to Agile & cyclical Waterfall. Hmmm, just like this video, Agile looks like a way to *SELL* something new & groovy.
i always thought that the Boeing employees just sat around a huge table with a bottle of vodka each, drinking until the plane just took off on its own!!
.Is it not hard to budget with agile methods? For example when the client comes up with a new idea every 2 weeks, do they stick another couple £100 on the bill?
@benshelly In the "agile" projects I've worked, the team does spend time estimating the approximate cost of a project. So the answer is, ask the client. The client can either add a couple hundred to the bill, or remove some equivalent-costing feature that is less valuable. Agile tends to empower the customer as much as it empowers the team.
Makes Agile look like the "solution selling" propaganda machine that it really is. Let's see: Groovy name (remember "RAD"?), groovy jargon (SCRUM, sprint, mock objects, yadda yadda), the whole bit. And this is because of what? OOP? Gimme a break.
It doesn't make sense to apply SCRUM to maintenance (software development).. just think of how would you estimate the tasks involved for bug fixing. Most probably you inherited a system not developed by you so you don't even know where to get started.
It looks like SCRUM may have been needed to make this video... sooooooo painfully looooooooooooooooong. The point should have been made more quickly and thus effectively.
agile is good software engineering process model: but team member and other person have spent lots of there time in meeting: it could be good so that other member should have knowledge of team member what they are doing. but only issues with meeting to spending lots of there time in meeting. I mean progress could be judged as individual a part from it when we are going to assign task to them
Yeah, we should remind that each model to be used while approaching the project is up to us to choose from.
They're all in different characteristics and different in mind desigining approach. They all have good and bad points if view from different view point.
So it will be better if we just dont say that this is bad, so we should go to another.
More over I think If we combine it and make use of each of them in the real implementation would be great.
Honestly, I do think Agile is the way to go IF you want that sort of flexibility in your project. If its something thats very unique and highly custom to the users needs, Agile might be something you'd consider.
But for a more standard application thats been done a few times before, Agile isn't necessary and Waterfall will work fin. The only bennefit Agile offers is the increased communication and the ability to add new modules later int he project. If u dont need these then WF is fine.
wow that had to be the most biased overview done by a marketter rather than an engineer i have ever seen LOLOL. Waterfall vs Agile are just buzz words made by marketting to describe nothing really. EVERY project i have worked on has had changes along the way some u HAVE to intergrate some you HAVE to push back on and say no.
Biased, possibly. Agile people are quite enthusiastic about what they have learned and how it had changed their lives (when properly done; there are also people who've tried Agile, probably done it wrong, and don't want to touch it ever again).
But it is true. Agile development does make a difference. Saying it is buzz words is unfair and uninformed. It's an entirely different _mindset_, from which somewhat different practices emerge.
Of the video itself, should've been half the length :).
The longer a defect exists the more expensive it is to deal with. Wrong or missing requirements are very expensive, design mistakes are costly too. So, better to ask the customer and or other developers to help find the costly defects, then we can all go home early. And remember, to go home early, most of the time consuming defects need to be found.
There is no methodology to fit them all. If you've got a solid project that absolutely needs to be designed correctly (aircraft software) then you need to use a methodology like waterfall since these things take an enormous amount of time to design, formalise, and test.
I can't say it in this public forum. Send me your email and I'll let you know exactly how I know Boeing is doing agile. I'm chris(at)edgehopper(dot)com
@cspag67 could that be why the 787 dreamliner is over 18 months behind schedule and bursts into flames during test flights? ;-)))) nanny nanny pants on fire, my methodology is better than yours ;-)))) come on, folks. agile/scrum is the "du jour" methodology. give it time and something will come along to replace it.
i always thought that the Boeing employees just sat around a huge table with a bottle of vodka each, drinking until the plane just took off on its own!!
@coldplasma I do agree with you. No one size fits all. Although the video highlighted the pros of agile, it depends on the scope of the project. If the scope of project is not huge, we might be better off with waterfall. Imagine you need to meet client frequently on a small project...
@coldplasma I agree with coldplasma, you cant just choose one methodology for creating a software... small applications doesnt need any better than Waterfall, but large & close deadline projects for which require accurate results with less support time needs Agile... However, there are more methodology than only those two of course...
That is a really abysmal video. Totally naive and thoroughly boring. Also one of the most blatant advertisements for why you're current method are completely f-ed up and we're the only ones that can help you and our fee is only $5000 a day. What a deal, right?
I have been looking at this video and doing some research on Agile and although it seems to shorten the process and allows you to stay abreast to change in requirements, it seems that it is really poor in its ability to provide tracibility to core business cases and strategies.
How do Agile processes provide clear visibility to match software features on the to do list to actual strategies that can be used to calculate returns?
@faruqh - I agree. With agile, its hard to closely match deliverables with corporate strategies and the business case process gets messy too.
When new requirements arise, you need to keep matching against strategies and check feasibility. It really does slow the process. Agile certainly has its trade offs.
. @faruqh - I agree. With agile, its hard to closely match deliverables with corporate strategies and the business case process gets messy too.
When new requirements arise, you need to keep matching against strategies and check feasibility. It really does slow the process. Agile certainly has its trade offs
This comment has received too many negative votesshow
Excellent video, but Agile methodology is rubbish! I really pity the people involved in this disaster of a methodology that simply forces developers to deliver "anything" by a certain date just so as the product owner is happy knowing developers are not messing about at work. Too bad they don't realise that some are so passionate about software they'll do it for free! Unfortunantely for all these companies, those developers exert that passion into open-source development after work. Go figure!
Guess the internet allows anyone to comment from the illiterate and uninitiated to the expert. Hope you realize where you stand with your commments about Agile.
....And what category do you fall in? The ones that feel superior to everyone else and need to state it through sarcasm? Actually I don't really care, but I do need to make a correction to an error. I wanted to state the Scrum aspect of Agile and not the entire collection of practices that Agile is about. Although I come from an era where that was simply called common sence.
Touchy touchy. I wasn't being sarcastic - I was simply asking you to be more specific about what you object to. Scrum isn't part of Agile. Agile isn't even a methodology - like say Extreme Programming or Scrum. It is a set of principles which you can apply to your development process. To be honest "common sense" isn't that common, and never has been. If it was we would need to discuss development methodologies.
Actually, I was responding to desobri. But Ill just say this and although my thoughts belong to the developers end. How well something is designed is what counts for a software company. Its the intellectual property of the company and it should be designed ingeniously. Stop worrying about how to do this is and how to do that, but concern yourselves with the quality of your products. Question is this; can you design it? Or r u to busy worrying if youre following methodologies not of your own?
Design is necessary but not sufficient. The quality of the developers, the teamwork among them, the discipline applied and the commitment to quality are all critical factors which have a far larger contribution to project success. You can do too much design. Methodologies should not be handcuffs - they are tools.
Again, I repeat, my comments were in regards to Scrum. But what I was trying to describe was simple; there is no substitute for the sheer will of developers to carry something out to the best of their abilities. And usually developers find open source as a place to do that, where they are free from constraints.
@DesiBabaJi - we're in the process of showing waterfall to the door in our organization. Agile processes like scrum encourage accountability, responsibility, and ownership -- every day. It's not micro-management though. The scrum team has authority during the sprint and is free from outside influences. In my experience, employees really like the increased visibility and ownership of their work.
If I were a business owner, I would prefer the agile method, however as a corporate employee, waterfall seems more appropriate. Agile seems more micro managed where employees report on daily progress. Name an employee who wants that and appreciate being watch like hawks?!
Agile is quite the opposite to micro management. In Agile the manager is there to support and enable the team. The team becomes motivated and empowered by having ownership in the project. On one project I was running I had to demand that my developers work LESS because they were getting tired the next day. Thats real commitment. This isn't management bullshit; it really works.
Wow, this is a great video. Really effective use of positive imagery. And we were not beaten over the head with acronyms. Direct, simple, effective and above all emotionally compelling. Just love it.
Yeah right. All this bad stuff is inherent to waterfall (including the golf). I've never worked on a successful Agile project. Waterfall has been pretty much a slam-dunk every time. People who think about what they do before doing it tend to be successful. Waterfall is like having a blueprint before you build a house. Agile is like just hiring contractors and telling them to go at it.
DaveZiffer 2 weeks ago
Did anybody else find this video painful to watch?
missanthropy19 1 month ago
Thumbs up if you think Ian is a cum-dumpster.
IDerpinstein 1 month ago 5
Comment removed
sinart93 1 month ago
Rusty developed work based depression shortly after this video, he couldn't handle the pressure, his wife didn't care when he tried to talk to her about it and his mother developed an illness. Rusty had a lot on his plate, then one day he was browsing youtube while at work and found a video called "Agile vs. Waterfall: A Tale of Two Teams" based on him, he felt irrelevant and, later that day, killed himself with an, ironically, rusty knife. THIS VIDEO IS CRUEL!
LikeABaugh 1 month ago 7
@LikeABaugh Hi Ian :D
Noctis2709 1 month ago
@Noctis2709
Hey Dean! ;D
up626 1 month ago
@up626 HEY DAN!
LikeABaugh 1 month ago
i love how these videos try to make work look like soooo much of fun.
askbob 2 months ago
Great job!;) I makes sense if you already have a background on these methodologies though:D
303MIS 3 months ago
Great job!;)
303MIS 3 months ago
incorrect
atiquh 3 months ago
Let me get this right, while in the Waterfall methodology the client is rafting, in the Agile one, the client is holding an arm full of documents faking a smile :-?. I think the client will prefer rafting.
MarinoviciR 4 months ago
Very Nice video, thanks a lot. Agile is impressive but I have little confusion, how the budget will decided after finishing the project? It might be like (total hours needed to finish the project X Rate per hour) as clients get updates after 2 weeks ???
zakiur81 4 months ago
@zakiur81 Yes, your assumption/question can work well. $/hour/person/sprint is a logical way to develop contracts. Good agile teams can clearly demonstrate to the client, in advance, their velocity and capacity so that the client is able to predict the cost of their relationship over many cycles.
DavidSabine 2 months ago
who would you hire to work on your project?
ME, because it is MY project
WhISp3R 4 months ago
Poor Rusty.
ejdst21 4 months ago
Imo this is a pretty poor video, as it doesn’t really present the pro's and con's of either methodology. Which are present for both styles! Simply put, the team needs to fit the methodology, the methodolgy needs to fit the product. If the three are not in sync then you will always have an unhappy customer irrespective of the team, quality or methodology.
GregWilliamBryant 5 months ago 3
This video was clearly made AGILE style...it's choppy, overcomplicated, and the end result has no value.
legacymate 5 months ago
unfortunately, this "SCRUM" and "AGILE" crap is just that: crap. it is just an excuse for managers to continuallly change the requirements and slow down production. having a solid plan at the beginning saves time and money and keeps developers from wanting to choke their managers
tommyjonestheband 5 months ago
Excellent video I must say. You cleared my many of the doubts on Agile development. Thanks for providing such valuable info.
prashantzombade 5 months ago
FUCK YOUR TEAM!
fulltimepassgiri 5 months ago
Kate's boss is always there to...Make oversized supervillan deathtraps from the 60s Batman series? Each time more fiendishly than the last?
6Man666666 6 months ago
hahaha Kate is not working in software development =D
Jharek16 6 months ago
i will hire kate
ZeroCrack 7 months ago
OneMoreYear....I don't have a problem mate, I know where to find hard information on software methodologies. My criticism of this presentation is that it paints a very idealistic picture of the agile methodology but without sufficient contextual information to make it credible.
uptightkid 8 months ago 2
This video is rubbish. It tells us nothing concrete. I was hoping to hear about how much money/time was saved by using one approach vs another. Instead we get motherhood statements. IMO...agile is fine for many projects but the lack of documentation can lead to tricky maintenance risks/costs down the road.
uptightkid 8 months ago
Awesome video that uses blantant imagery about difference between two styles. Both approach can work but agile can adapt. It starts producing something right away. Its is about iterations of product which is code word for innovation.
gouldrobertj 8 months ago
Kate and Rusty should totally get it on. Then we could have the best of both worlds. Plus, their kid would probably be really attractive.
junnebugg11 8 months ago
Kate and Rusty should totally get it on. Then we could have the best of both worlds. Plus, their kid would probably be really attractive.
junnebugg11 8 months ago
Agile solves all problems. Even Boeing uses Lean. The people who keep saying that the answer is usually a mix are the people responsible for all the failed projects in the Standish Report. But please never compare building projects, or even electronic projects (such as Nasa and airforce projects) with software projects. They are different things and should be treated as such. For software projects, Agile is the only way to fly.
AussiePlague 8 months ago
Isn't Boeing over half a decade late on their newest plane.
EricDalnas 8 months ago
I had to press the dislike button I'm afraid, this is so biased that I don't know whether it's funny or sad. I'm a big proponent of Agile because short cycles are insurance against many of the major software disasters we know, but in real life major software projects aren't one or the other. I've been in this industry for 20 years, now I'm overseeing security for a solution of 150 (growing!) components by 20 teams. Some working in silos - doh - shouldn't happen, right? Maybe I'm just too old...
onlineove 9 months ago
It is hard to do a complex project 100% in Agile and neither company do that. So the solution is based in a mix of "ideologies". Personally i think the main problem with Agile is that, to determine the working hour is more a "i am estimating that.." rather a exact science.
eng3d 9 months ago
A ludicrous portrayal of waterfall, clearly interpreted by zealots trying to start a religious war. The correct answer is determined by the project, and both methodologies have strengths and weaknesses.
Play to the strengths of each methodology, and realize that the weaknesses are simply the cost of acquiring those strengths.
stephenspielberger 9 months ago
that's somewhat an irritating video but it gives you an idea what agile is briefly about.
oglakci 9 months ago
i think rusty and kate sud get it on lol
angelacssdy 9 months ago
This is all a lie, there are no attractive looking women in this profession
sadhukar 9 months ago 48
This has been flagged as spam show
@sadhukar That attractive woman was the client. So you see. It all makes sense
sazabi02 8 months ago
This has been flagged as spam show
@sadhukar That attractive woman was the client. So you see. It all makes sense
sazabi02 8 months ago
@sadhukar
Choose women who do fine arts or those from linguistic background. Never choose engineers or doctors...Most girls are ugly in this profession
dees900 6 months ago
Comment removed
omnidrifter 4 months ago
@sadhukar You haven't met me yet :p
onegirl8997 4 months ago
@onegirl8997 pics or gtfo
sadhukar 3 months ago
This has been flagged as spam show
@sadhukar You'll get nothing if you speak like that.
onegirl8997 3 months ago
lol 2:20 the guy has a 'DERP' face
sadhukar 9 months ago
I love when people try to make the claim that one way is the solution for all for your problem. Nothing in the world works that way. Each development methodology has is pluses and minuses and work for different types of projects and teams. The trick is finding the one that works for your situation. Process should work for the team not the inverse.
jobelobes 10 months ago
i do not take this vid any serious, btw.
you must admit that for several types of projects the Agile methodology is the best one in comparison with waterfall.
as for "extremism", yes, there are many situations and business cases that DO require such an extreme approach
anyway, thanks for feedback ("watelfallists" by default can not like feedback :) i guess
VigenToT 10 months ago
Hey mommy look at me look at me! I'm Agile! I'm so special! Lavish attention on me!
Ermmmm shut up and do something meaningful and scientific with your lives you snake oil peddling parasites.
billiepipersteeth 10 months ago
@billiepipersteeth you are a stupid man loving to show up
you really do not understand what being agile means.
VigenToT 10 months ago
@billiepipersteeth you are a stupid man loving to show up
you really do not understand what being agile means. but of course its not your fault but the team's or organization"s where you work
VigenToT 10 months ago
@VigenToT You're right, I probably don't understand what "Agile" means, but I bet there is a week's course I can sign up to for $30,000 that will line the pockets of High Priests Schwaber, Fowler et al. I'm very sure it will teach me exactly what the latest fashion is regarding whacky americanised terminology used by middle-management fad loving drop-outs to re-brand common sense and well-documented engineering concepts that have been around since the early part of the last century.
billiepipersteeth 10 months ago
@billiepipersteeth
there is no need to "line the pockets" of anybody if you want to learn and practice Agile. i am quite well in Agile and all i learned by myself. Also, for many year i have been practicing waterfall as Project Manager. now i can say agile is an excellent method to adopt for fast changing, risky projects. if you are a construction project manger, then go ahead and use waterfall, but in IT projects waterfall is a complete failure.
VigenToT 10 months ago
@billiepipersteeth
there is no need to "line the pockets" of anybody if you want to learn and practice Agile. i am quite well in Agile and all i learned by myself. Also, for many years i have been practicing waterfall as Project Manager. now i can say agile is an excellent method to adopt for fast changing, risky projects. if you are a construction project manger, then go ahead and use waterfall, but in IT projects waterfall is a complete failure.
VigenToT 10 months ago
@VigenToT to your note: all great IT products are delivered via agile :and browser you are using right now (be it Chrome of IE)
VigenToT 10 months ago
@billiepipersteeth to your note: all the great software is delivered via agile including the browser you are currently using (be it Chrome or IE)
VigenToT 10 months ago
@VigenToT What many disciples of Schwaber fail to realise (yourself being a good case in point) is that "Agile" and "Waterfall" are exactly the same model, but using extreme values for the parameters in this model. The Agilist have hijacked and are attempting to brand engineering concepts that preceded this "movement" by 100+ years. On top of that, throws in branded terminolgy for already recognised and understood entities such as "team", "manager", "architect" and "release".
billiepipersteeth 10 months ago
@VigenToT Oh and by the way Agilists..."Kate" isn't a real person, she is fictional. Back to reality for you all!...a reality that requires one has scientific talent to be sucessful. Spouting buzzwords coined by the Agile priest just doesn't cut it!
billiepipersteeth 10 months ago
This has been flagged as spam show
I recommend reading The Agile Method and Other Fairy Tales By David Longstreet. Just seek it out before you decide anything based on this video.
difficultix 11 months ago
Comment removed
difficultix 11 months ago
There are no facts here. Nice story though. I'd like to share with you another story based on using scrum (on many projects) where the projects have slipped several sprints and the product quality is very low, oh, and not once have I seen the customer on site and able to answer developer questions. There are aspects of agile that I like but generally (in my experience) it's a tool used by managers to obtains their metrics and micro manage development.
jodscho 11 months ago
I would be useful for a short summary of the two techniques.
SpaceHeaterStudios 1 year ago
bullshit
ykravchenko 1 year ago
if i have team lead like kate then iam gonna work 24x7 :)..
876sop 1 year ago
Nice video. Nice music. Thanx to share with us.
wmsudheera 1 year ago
Nice video, what song is playing in the back?
KhanSlayer 1 year ago
Holy Smackers, Batman! What a pile of horse droppings. Agile is the answer to all development problems, ever! Wow! Why hadn't I thought of that?!?
Get a clue, slackers. The Agile Turd Polishing Method.
SomeUselessGeek 1 year ago
Nice video, but takes a long time to say what is says. The music gets boring/annoying. A snappy voice over would have been much more engaging.
spasmoid1971 1 year ago
I am in an agile process now, and it's chaos. The code is a mess. There is no documentation. Specs are unclear. Nobody knows where we stand. In short: it's pandemonium. Everybody's just hacking their way through those "story point" cards or whatever bullshit they call it this time. The rest of the time is wasted on "story planning" or "retrospectives" or whatever. It's like trying to build a house on quicksand.
MomoTheBellyDancer 1 year ago 2
@MomoTheBellyDancer Obviously you are not using it right. Better talk to the customer and show them almost weekly a new prototype. That would help to focus.
Supreme40x 1 year ago
Great video, but I think you can make your point in less time.
xinianlai 1 year ago 22
@xinianlai God yes, why is this sooooooo drawn out. i guess they used the waterfall method to make the video :-)
Nefferello 4 months ago
Great video and very funny.. I appreciate this approach to training. I am tyhowardthepmcoach(com) I invite you to join ghostrade a new generation commerce portal founded by PMI Award Winning Ty Howard, PMP (and CIO Magazine Leader's to watch). I invite you to join Ghostrade(com) to witness the fruits of labor in regards to PM work and strategic planning.
Ghostrade2010 1 year ago
pictures say thousand words...
aa01 1 year ago
This has been flagged as spam show
@aa01 pictures say thousand words...
boring 90's style crap =)
LevitskiSRGE 1 year ago
if you had speeded up the video like 3x, would have been great. Dude, it's the internet generation... quick reception, short attention span ;)
anke41 1 year ago
awesome video. ever hear of Mendix? time to market five times faster at half the cost... its worth checking out.
ericp578 1 year ago
awww... what a happy family :)
preetiedul 1 year ago
nice one, thanks
findingadly 1 year ago
I ahte agile and everything it stands for. We used to call it "quick and dirty". The worst think about it is the swearing at meetings. It is all very unseemly.
SupBA 1 year ago
This is terrible distortion. Without Rusty, Kate would be nowhere. Henry Ford was a Rusty. Caesar, Napoleon and Alexander were Rusties. They planned things. Beethoven, Schiller, Einstein and Shakespeare were Rusties. They all used a Waterfall type methodology. What has Agile given us? Lady Gaga, Justine Bieber and the Global Financial Crisis?
Agile may be young and trendy against the old fashioned and staid methods. The great things of beauty in the world were not built by Agile methods.
SupBA 1 year ago
@SupBA the great things of beauty in the world cost a lot to keep "great" and "beautiful" - agile means future proof. if Ford was a kate, his assembly lines would be the best in the world by now. but they're not. they make Fords.
ericp578 1 year ago
@SupBA
"They all used a Waterfall type methodology."
I don't think you can use software development methodology on art. It's a totally different process.
MomoTheBellyDancer 1 year ago
A very nice video comparing horses and pears. I suspect this has been made by somebody who has never used either of the methods in practice in many projects. Methods don't work, people work, with the right devised method for the project at hand. Scrum is a nice way to do some work, but not for any (IT) project, or any type of work.
It's only a matter of time when the new films arrive with: "In the old days we did waterfall, RAD, SCRUM, but now we have finally fould the right method: URG!" ...
paulduran88 1 year ago
you can always upload this kind of presentation at Slideshare with out converting them to flash. Slideshare will do it for you and with a better navigation.
akashag1001 1 year ago
you can always upload this kind of presentation at slideshare with out converting them to flash. Slideshare will do it for you and with a better navigation.
akashag1001 1 year ago
I work in a scrum team and I can't say that I'm the happiest person! The problem is not the methodology itself, but the people and their natural flaws. Selforganized works well when you have a small group of very commited persons. In a big, distributed organization it doesn't work that well. I'm working in agile for two years and the amount of "real", sellable work doesn't impress.
AliceDamnation 1 year ago
@AliceDamnation, pause the above video at 6:55. Sounds like no action was taken in two years for this critical step. Scrum will expose all the natural flaws. Sometimes it means pointing out these flaws, perhaps making a change. Other times, it means making a tough decision like letting someone go.
oegunal 1 year ago
nice presentation thanks for the video
reallycool59 1 year ago
This assume high capability maturity.
rickbangkok 1 year ago
interesting
dlarkaigh 1 year ago
This has been flagged as spam show
Oh wow. Propagandizing a dev life cycle methodology using cliches & stock photos. Did it ever occur to anyone that Agile formalizes what a great many departments have done for ages anyway, that they improvised processes that worked for them & delivered successful systems? Propping up strawmen RAD problems won't dismiss the salient point that RAD & cyclical Waterfall were progenitors to Agile? To the old farts Agile looks like yet another way to SELL something new & groovy (just like this vid).
leebertarian 1 year ago
Oh wow. Propagandizing a dev life cycle methodology using cliches & stock photos. Did it ever occur to anyone that Agile formalizes what a great many departments have done for ages anyway, that they improvised processes that worked for them & delivered successful systems? Propping up strawmen RAD problems won't dismiss the salient point that the RAD concept is a progenitor to Agile & cyclical Waterfall. Hmmm, just like this video, Agile looks like a way to *SELL* something new & groovy.
leebertarian 1 year ago
Can anyone tell me the source of the audio in this video??
I just love the music. Its soothing in an astonishing sort of way, and classy.
aguytr65 1 year ago
@aguytr65 It's "Rubber" by Williamson.
seanparmelee 1 year ago
agile does not work
mathewjohn5174 1 year ago
i always thought that the Boeing employees just sat around a huge table with a bottle of vodka each, drinking until the plane just took off on its own!!
i can't believe i'm wrong about it!
i think i may cry.
jampez77 1 year ago
.Is it not hard to budget with agile methods? For example when the client comes up with a new idea every 2 weeks, do they stick another couple £100 on the bill?
benshelly 1 year ago
@benshelly In the "agile" projects I've worked, the team does spend time estimating the approximate cost of a project. So the answer is, ask the client. The client can either add a couple hundred to the bill, or remove some equivalent-costing feature that is less valuable. Agile tends to empower the customer as much as it empowers the team.
traviscalder 1 year ago
Ah, right. When you're on Waterfall, that means your boss gets to golf, instead of work.
Wait, what?
gsadamb 2 years ago 2
@gsadamb
Makes Agile look like the "solution selling" propaganda machine that it really is. Let's see: Groovy name (remember "RAD"?), groovy jargon (SCRUM, sprint, mock objects, yadda yadda), the whole bit. And this is because of what? OOP? Gimme a break.
leebertarian 1 year ago
great video, thanks!
dazcorupt 2 years ago
Brilliant! far better than a long speech!!
dipendrabs 2 years ago
We used to have the waterfall model, but now we have silver bullets!
F00dTube 2 years ago 2
Hi I love the presentation except for the music ;)
usinelogicielle 2 years ago
Comment removed
Ma3xdedu111ka 2 years ago
Awesome video!
sabanerjee 2 years ago
I would love to see a video that puts both agile and waterfall in their best light. BOTH have their place BOTH have value. But choose wisely!
jflahiff 2 years ago 2
Comment removed
Ma3xdedu111ka 2 years ago
Rusty needs a video editor.
FPChris 2 years ago
I'm interested to know how you bill (estimate) an agile project, which is ever expanding and changing, and how you set and meet timelines?
And also why did it take half the time? I can't see why that happened! Scoping doesn't take that long.
Is this just a blue ocean buzz word to charge for doing the same old?
I can't see how it woud meet Prince 2 (best practice) standards either.
midiwhale 2 years ago
is SCRUM methodology applicable to warranty/maintenance support?
joeyhcmc 2 years ago
It doesn't make sense to apply SCRUM to maintenance (software development).. just think of how would you estimate the tasks involved for bug fixing. Most probably you inherited a system not developed by you so you don't even know where to get started.
unfielusuario 2 years ago
though you could use a Kanban approach
jflahiff 2 years ago
It looks like SCRUM may have been needed to make this video... sooooooo painfully looooooooooooooooong. The point should have been made more quickly and thus effectively.
lovesmario 2 years ago 2
agile is good software engineering process model: but team member and other person have spent lots of there time in meeting: it could be good so that other member should have knowledge of team member what they are doing. but only issues with meeting to spending lots of there time in meeting. I mean progress could be judged as individual a part from it when we are going to assign task to them
shahgeb 2 years ago
Yeah, we should remind that each model to be used while approaching the project is up to us to choose from.
They're all in different characteristics and different in mind desigining approach. They all have good and bad points if view from different view point.
So it will be better if we just dont say that this is bad, so we should go to another.
More over I think If we combine it and make use of each of them in the real implementation would be great.
haxpor 2 years ago 2
This is such a stupid video. Let's put trendy people in a video and you positive words like "happy" and "success."
luomio 2 years ago 2
Honestly, I do think Agile is the way to go IF you want that sort of flexibility in your project. If its something thats very unique and highly custom to the users needs, Agile might be something you'd consider.
But for a more standard application thats been done a few times before, Agile isn't necessary and Waterfall will work fin. The only bennefit Agile offers is the increased communication and the ability to add new modules later int he project. If u dont need these then WF is fine.
YoshimotoMakoto 2 years ago
anybody wanna know whtz da AGILE is...
here it goes....
Great video........ superb
mrlsilva1 2 years ago
A-W-E-S-O-M-E
sdds14 2 years ago
Terrific video, very creative and I really recommend!
agiletechnosys 2 years ago
Do you guys live in the real world? This garbage has put me completely off Agile as a methodology.
smda2000 2 years ago
Well... you stick with Rusty then :-)
Mewlotova 2 years ago
Nice Video,it was awesome when for every incomplete sentence the next slide shows the picture for than missing word.Nicel done and great creativity
palimds 2 years ago
wow that had to be the most biased overview done by a marketter rather than an engineer i have ever seen LOLOL. Waterfall vs Agile are just buzz words made by marketting to describe nothing really. EVERY project i have worked on has had changes along the way some u HAVE to intergrate some you HAVE to push back on and say no.
militantmindset 2 years ago
Biased, possibly. Agile people are quite enthusiastic about what they have learned and how it had changed their lives (when properly done; there are also people who've tried Agile, probably done it wrong, and don't want to touch it ever again).
But it is true. Agile development does make a difference. Saying it is buzz words is unfair and uninformed. It's an entirely different _mindset_, from which somewhat different practices emerge.
Of the video itself, should've been half the length :).
Emmerald1 2 years ago 2
The longer a defect exists the more expensive it is to deal with. Wrong or missing requirements are very expensive, design mistakes are costly too. So, better to ask the customer and or other developers to help find the costly defects, then we can all go home early. And remember, to go home early, most of the time consuming defects need to be found.
JapaneseLearningVid 2 years ago
There is no methodology to fit them all. If you've got a solid project that absolutely needs to be designed correctly (aircraft software) then you need to use a methodology like waterfall since these things take an enormous amount of time to design, formalise, and test.
coldplasma 2 years ago
Interesting you should mention aircraft software. Boeing uses agile and scrum in particular to develop their software. You might want to guess again.
cspag67 2 years ago 10
Really? Can you cite any sources on this? I'm not saying you're wrong, but you are going to need to cite something here.
coldplasma 2 years ago 3
I can't say it in this public forum. Send me your email and I'll let you know exactly how I know Boeing is doing agile. I'm chris(at)edgehopper(dot)com
cspag67 2 years ago
Comment removed
TheFlowmasterGroup 1 year ago
@cspag67 could that be why the 787 dreamliner is over 18 months behind schedule and bursts into flames during test flights? ;-)))) nanny nanny pants on fire, my methodology is better than yours ;-)))) come on, folks. agile/scrum is the "du jour" methodology. give it time and something will come along to replace it.
an old timer...
ibnanouk 1 year ago
@coldplasma
i always thought that the Boeing employees just sat around a huge table with a bottle of vodka each, drinking until the plane just took off on its own!!
i can't believe i'm wrong about it!
i think i may cry.
jampez77 1 year ago
@coldplasma I do agree with you. No one size fits all. Although the video highlighted the pros of agile, it depends on the scope of the project. If the scope of project is not huge, we might be better off with waterfall. Imagine you need to meet client frequently on a small project...
kevin009 1 year ago
@coldplasma I agree with coldplasma, you cant just choose one methodology for creating a software... small applications doesnt need any better than Waterfall, but large & close deadline projects for which require accurate results with less support time needs Agile... However, there are more methodology than only those two of course...
angelsevil2002 1 year ago
I find this video to be a bunch of lies. Good luck with the clients.
shklm0 2 years ago
That is a really abysmal video. Totally naive and thoroughly boring. Also one of the most blatant advertisements for why you're current method are completely f-ed up and we're the only ones that can help you and our fee is only $5000 a day. What a deal, right?
jeffcowanpdx 3 years ago
I have been looking at this video and doing some research on Agile and although it seems to shorten the process and allows you to stay abreast to change in requirements, it seems that it is really poor in its ability to provide tracibility to core business cases and strategies.
How do Agile processes provide clear visibility to match software features on the to do list to actual strategies that can be used to calculate returns?
faruqh 3 years ago 7
@faruqh - I agree. With agile, its hard to closely match deliverables with corporate strategies and the business case process gets messy too.
When new requirements arise, you need to keep matching against strategies and check feasibility. It really does slow the process. Agile certainly has its trade offs.
Anjxi 1 year ago
This has been flagged as spam show
. @faruqh - I agree. With agile, its hard to closely match deliverables with corporate strategies and the business case process gets messy too.
When new requirements arise, you need to keep matching against strategies and check feasibility. It really does slow the process. Agile certainly has its trade offs
Anjxi 1 year ago
it's all about who's the slave and who gives orders in this world, sadly....
I want to give orders, if I have that choice.... :D
trr12 3 years ago
PowerPoint forever:)
ahatur 3 years ago
This comment has received too many negative votes show
Excellent video, but Agile methodology is rubbish! I really pity the people involved in this disaster of a methodology that simply forces developers to deliver "anything" by a certain date just so as the product owner is happy knowing developers are not messing about at work. Too bad they don't realise that some are so passionate about software they'll do it for free! Unfortunantely for all these companies, those developers exert that passion into open-source development after work. Go figure!
sithiro 3 years ago
Guess the internet allows anyone to comment from the illiterate and uninitiated to the expert. Hope you realize where you stand with your commments about Agile.
desobri 3 years ago
....And what category do you fall in? The ones that feel superior to everyone else and need to state it through sarcasm? Actually I don't really care, but I do need to make a correction to an error. I wanted to state the Scrum aspect of Agile and not the entire collection of practices that Agile is about. Although I come from an era where that was simply called common sence.
sithiro 3 years ago
Touchy touchy. I wasn't being sarcastic - I was simply asking you to be more specific about what you object to. Scrum isn't part of Agile. Agile isn't even a methodology - like say Extreme Programming or Scrum. It is a set of principles which you can apply to your development process. To be honest "common sense" isn't that common, and never has been. If it was we would need to discuss development methodologies.
cheetah100 3 years ago
Actually, I was responding to desobri. But Ill just say this and although my thoughts belong to the developers end. How well something is designed is what counts for a software company. Its the intellectual property of the company and it should be designed ingeniously. Stop worrying about how to do this is and how to do that, but concern yourselves with the quality of your products. Question is this; can you design it? Or r u to busy worrying if youre following methodologies not of your own?
sithiro 3 years ago
Design is necessary but not sufficient. The quality of the developers, the teamwork among them, the discipline applied and the commitment to quality are all critical factors which have a far larger contribution to project success. You can do too much design. Methodologies should not be handcuffs - they are tools.
cheetah100 3 years ago
Perhaps you can elaborate on how Agile is less like open source development compared to say waterfall?
cheetah100 3 years ago
Comment removed
sithiro 3 years ago
Comment removed
sithiro 3 years ago
This has been flagged as spam show
Again, I repeat, my comments were in regards to Scrum. But what I was trying to describe was simple; there is no substitute for the sheer will of developers to carry something out to the best of their abilities. And usually developers find open source as a place to do that, where they are free from constraints.
sithiro 3 years ago
@DesiBabaJi - we're in the process of showing waterfall to the door in our organization. Agile processes like scrum encourage accountability, responsibility, and ownership -- every day. It's not micro-management though. The scrum team has authority during the sprint and is free from outside influences. In my experience, employees really like the increased visibility and ownership of their work.
trippfenderson 3 years ago 4
Good video - very informative.
If I were a business owner, I would prefer the agile method, however as a corporate employee, waterfall seems more appropriate. Agile seems more micro managed where employees report on daily progress. Name an employee who wants that and appreciate being watch like hawks?!
5 stars for the video.
DesiBabaJi 3 years ago
Agile is quite the opposite to micro management. In Agile the manager is there to support and enable the team. The team becomes motivated and empowered by having ownership in the project. On one project I was running I had to demand that my developers work LESS because they were getting tired the next day. Thats real commitment. This isn't management bullshit; it really works.
cheetah100 3 years ago 2
One critical suggestion--The visual of the cogs doesn't well support the idea of working software over design docs.
You still got 5 stars out of me though.
lancerkind 3 years ago
@lancerkind I find it interesting that the cog configuration used doesn't allow ANYTHING to move.
Msplqaokws 6 months ago
This video was lovely! The music, the visuals, the words, it all worked so well. Were the photos canned or did you shoot them for the video?
The video had none of the hazy resolution of usual YouTubes. How did you get such good video quality?
lancerkind 3 years ago
Wow, this is a great video. Really effective use of positive imagery. And we were not beaten over the head with acronyms. Direct, simple, effective and above all emotionally compelling. Just love it.
cheetah100 3 years ago
i love how the clients are having a good time and having new ideas while the dev team are working their a** off
fatalz 3 years ago 2