What the hell is Agile Development? It feels like a buzzword

>>59368663

you do what is asked, nothing more.

It's about adjusting development towards fulfilling features over finished projects with well established plans and roadmaps.

The idea is that changing requirements are real and agile solves this problem by simply redirecting work towards the new vision of the month.

>>59368695
>>59368719
Thank you good lads.

>>59368663
BU by any chance?

>>59368808
No. Sorry.

>>59368695
>>59368719
So it is just a buzzword for "plan as you go".
Who comes up with this shit anyway?

>>59368663
Google SCRUM.

File: 1445639257842.jpg (106KB, 768x1024px) Image search: [Google]

106KB, 768x1024px

>>59370241
Agile Development is just GO HORSE with more meetings

>>59368719
This basically. Saying anything more than this would be too specific as everyone has their own flavor of it. It's just a methodology and like all methodologies there are things it's good at and things it's bad at, unfortunately people have latched onto it like it's a panacea with which they can solve any and all productivity problems regardless of context.

>>59370299
>like it's a panacea with which they can solve any and all productivity problems regardless of context.

To be honest it's a pretty good work methodology. Especially if you look at what was used before i.e waterfall and what not.

>>59370373
>Especially if you look at what was used before i.e waterfall and what not.
This is precisely the problem. Whenever anyone criticizes agile you get the same cookiecutter response: "It's not waterfall". Yeah, we know, that doesn't make it suitable in every context or actively good, it's basically just saying "Some structure is better than none".

It's the realization that you can't create a perfect finished software product by theory/plans alone. You have to accept imperfection in order to actually get something done and continuously work on those imperfections and new ones that appear while you develop.