3 ms·
I Hate the Agile Manifesto
- ajross 18y agoHonestly, I think this is exactly backwards. The voodoo juice in "agile" comes from the mindset, and not the specific practices. The mindset is encapsulated pretty well by the manifesto, IMHO. Could someone write a better one? Maybe. But if you want to know what agile is all about, read the manifesto. Decades of experience in XP, *DD, AUP, etc... isn't going to teach you much about the "why" of those paradigms. If I were an agile proponent (and I'm really not) interviewing a candidate, I'd want to know that they can explain the handful of ideas in the manifesto. Process stuff is something any monkey can implement.
- DanielBMarkham 18y agoWhoa horsey. Nobody is arguing specific practices here. I'm arguing that feel-good marketing bleck doesn't make a project run. In fact, it confuses more than it helps. Want a good checklist of what agile is? Try http://www.whattofix.com/blog/archives/2008/04/the_agile_check.php http://www.whattofix.com/blog/archives/2008/04/the_agile_che... Or: * Adapt - Always ask yourself what is wrong and what you need to do to fix it. If you continuously communicate to identify problems and fix them, I believe that in a normal world you will do the following things that I can observe: * Time-Box - You have a fixed, immutable time-box in which you deliver tested changes (either code, documents, processes, beans, whatever) that be demonstrated * Togetherness - The closer everybody is, the better. Co-located, non-cubicle, non-office spaces are best. Highly matrixed, separated teams are worst. * Value - You have a clear way of determining the most valueable thing to do each iteration. Business Owners give you business value. Technical Owners give you architectural value. * Ownership - The team, and only the team, owns its estimates. Outside factors are considered and can be communicated, but at the end of the day the team has the power to determine the amount and type of work it can take on for each iteration. * Forecast - Being agile and empirical does not preclude precictability or forecasting. In fact, the value of agile teams is their ability to take highly-changing environments and put some kind of predictable forecastable order in them.
- ajross 18y agoHorsey? I don't much disagree with any of that. I might quibble with a few things (I'm not sure that "forecast" is really a central theme in most schemes, lots of very successful, nominatively "agile" development gets by without much of a timetable), but that's not particularly at issue. Your list looks good to me. But it also looks like a manifesto. And that's fine. So maybe your point is that you like your manifesto better than the official one? I like the poetry of the original better, but yours seems good too. But I don't understand the idea of "feel-good marketing bleck". The points of the original look awfully profound to me. I think you're being too hard on it here. If you like concrete guidelines more than statements of purpose, feel free. Just don't throw tomatoes at those of us who prefer the poetry.
- DanielBMarkham 18y agoI think you miss my point. I'm not crazy about manfiestos or checklists period. If you made me pick something, it'd just be "Adapt" But if you insist on having some list of statements that define what agile means to you, at least pick something that is measurable and doesn't leave you in a confused quandry. Valuing one thing over another has the impression that it is giving you information, when in fact it's leaving things more murky. If it's all relative, when would the other thing hold true? Why must there be tension between the two things? People come to me all the time because they don't understand that the manifesto is empty of meaning. Instead they think there is something profound there. They say things like "we should eliminate all documentation because it's in the manifesto" or "we value people over contracts, so offshoring can't work" But the manifesto says no such thing. In fact, it doesn't give much practical advice at all. It's just feel good, mom and apple pie stuff.
- festivusr 18y agoI'd take the manifesto over any stack of "Agile Programming with Blub" books any day, or the advice of any Agile Coach, for that matter. Each statement is giving you information. "When faced with one of these two things to concentrate on, we suggest you concentrate on the first one." That information might be obvious to you as an expert, but is non-obvious to some people, including many decision makers that don't develop software on a day-to-day basis. Is it an exact recipe to follow? Nope, but neither is development an exact science, or something you can do by rote following of a checklist. Which is exactly the point of the first item in the manifesto, incidentally.