I usually vote up Agile attacks, because I love to hear developers talk about the difference between good and bad Agile. But it's getting a little old. It seems the world is full of cranky, half-informed folks who get a little coffee in them and suddenly are ready to make grand pronouncements about the entire state of things (Love the self-recursion here) Seriously, one last time. Agile is best practices around itera…
Seven Things I Hate About Agile
71–80 of 124 posts
Re: Seven Things I Hate About Agile
#72So who the hell are Assembla and why should anybody care what they have to say? All I'm seeing here is a lot of misinformed ranting. Sure, there's a kernel or two of truth hidden away in there, but most good rants have that. I don't see that TFA makes any sort of interesting point or arrives at any real conclusion that's helping anybody make a decision though. Oh wait, I'm almost 40, so I guess I'm too busy decaying…
Note the last line: 'If you are interested in new solutions to some of the issues listed above, please follow this blog over the next few weeks.'
Re: Seven Things I Hate About Agile
#73This has the smell of ad-hominem on it. How about a little evaluation of the ideas?
> Most organizations which use the word "agile" are using the word precisely because they are NOT agile, and want to be more agile.
Again, this is basically just saying, "It can't be cool because the cool kids aren't in on it." How about an evaluation of the ideas, not the marketing?
> I don’t think values have anything to do with productivity or collaboration. The Americans and the Russians didn’t share many values, but they teamed up into a mighty fighting force during WWII because they shared a goal.
I abhor this attitude. You meet people who are all about "making use of you" at "startup weekend" type events. Values aren't so necessary for productivity in general, but shared values are necessary for productivity in areas where quality and attention to detail are paramount.
> If you are a vendor selling “pairs”, you have an awesome situation where you can charge twice as much, and you can easily churn guys on and off the pairs, one at a time
So you are evaluating a practice by the scummiest abuse of the practice? I think this reveals something, but not so much about the practice.
Re: Seven Things I Hate About Agile
#74I cant decide if this article is sarcasm or not. It makes me think about how there is no methodology that is the savior of developers everywhere. You may be able to find some operational efficiency choosing one methodology over another, but at the end of the day you either have developers that can write the code, or not.
I really think this guy have had some very annoying situations on agile-teams. At least it is what pops the most out of the blog post. He actually contradicted himself a lot of times: - "old people": Being a developer for a relatively small period of time, but I really have a hard time talking about agile with old developers. At least is what happens here at São Paulo/Brazil. - "stagnation": Agile is not Scrum. How a…
Re: Seven Things I Hate About Agile
#75What do [Scrum Masters] do? I'm sorry, but if you don't know the answer to this question, you're not familiar enough with agile to write intelligently about it. If you're going to write about a technique, you should at least know the basic concepts, whether you agree with them or not. And pretending ignorance for effect doesn't add much to the discussion.
Personally, I think one can learn enough about agile to apply it usefully without ever learning what a "scrum master" does. Maybe this goes back to the discussion of process vs. best practices.
Re: Seven Things I Hate About Agile
#76> Pair programming is like those girls that go to the restaurant bathroom together. What are they doing? Why don't you ask somebody who pairs, rather than writing an uninformed rant against it? > If you are customer, you pay twice as much and you get churn. Oh I get it, you're approaching and commenting on all of Agile from your software-as-contract-work perspective. Let me enlighten you: most software isn't sponsore…
In programming the spectrum is larger. When I've been asked to program with somebody, its always been a terrific drag on my productivity. I crawl thru the day, trying to be nice, and when they go the hell home I stay late and do my real work.
Re: Seven Things I Hate About Agile
#77So who the hell are Assembla and why should anybody care what they have to say? All I'm seeing here is a lot of misinformed ranting. Sure, there's a kernel or two of truth hidden away in there, but most good rants have that. I don't see that TFA makes any sort of interesting point or arrives at any real conclusion that's helping anybody make a decision though. Oh wait, I'm almost 40, so I guess I'm too busy decaying…
Yeah, I stopped reading at "Old People", and I am not even in that demographic. Wholesale discounting all wisdom in an entire segment of people with lots of experience in the very field you work in is rarely a good idea. I mean what's up with Knuth being so old? Some young guy should finish out TAoCP and show him how its done.
Re: Seven Things I Hate About Agile
#78Pair programming was invented and evangelized by developers, and are its most ardent defenders at every vendor I know that offers Agile services. ThoughtWorks' sales folks hate selling pairs, for the obvious reason that most clients don't love the idea of buying them.
Re: Seven Things I Hate About Agile
#79> Old people: Agile has the smell of death on it. If you go to an “agile” event you will see few people under the age of 40 and many over 50. This has the smell of ad-hominem on it. How about a little evaluation of the ideas ? > Most organizations which use the word "agile" are using the word precisely because they are NOT agile, and want to be more agile. Again, this is basically just saying, "It can't be cool becau…