4 ms·
Agile is A) vague and inspiring enough that everybody can project their desires, hopes and dreams on it and B) vague enough that it can be twisted by any author
by pydry 5y ago
Agile is A) vague and inspiring enough that everybody can project their desires, hopes and dreams on it and B) vague enough that it can be twisted by any authority to serve pretty much any purpose they like.
This is intrinsic to the entire movement and was from the very beginning as far as I can see.
There were some good ideas that emerged from the auspices of the movement but the movement itself never really committed itself too hard to any of them.
- hurflmurfl 5y agoMy opinion is that Agile is intended to be vague, as there can't be a silver bullet plan that fits every occasion. Of course, "no silver bullet" sells way worse than "I've got a silver bullet for you right here, Mr. CEO, just sign here". Let's check some "principles" posted at https://agilemanifesto.org/principles.html https://agilemanifesto.org/principles.html Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. To me it looks like all of the above is screaming at you "quit your great perfect plan and look at the real world instead". If something's wrong, adapt and adjust - this is what agility is about. You can't calcify agility. P.S. not really in any particular argument with you, just that your comment prompted me to write some thoughts that have coagulated in my mind while going through the comments here.
- oblio 5y agoWasn't the original manifesto written by consultants?
- jk20 5y agoAgile may have started with good intentions,but was repurposed by nontechnical managers looking for a chunk of money which really belongs to the developers. Agile theory and practice does not address any concrete technical issues, but it is a hand-waving about meetings, demos, hierarchy, convoluted bureaucracy related to the tickets (cf. the Law of Triviality). I do hope that the advent of remote work and networking as opposed to corporatocracy will wipe the Agile grifters out of existence.
- corpMaverick 5y agoSome of the them were practitioners and very technical. Kent Beck, Alistair Cockburn, Ward Cunningham, Dave Thomas, Robert C. Martin, Martin Fowler. In general there was a movement about better ways to develop software (beyond waterfall) and people were trying to figure it out. In 2002 they just got together and put it in writing.