Posted by Uberto Barbini on May 2, 2008
Nice reading, especially the comments. Anyway these are more or less “incomplete agile”.
Maybe partial Junit coverage is not agile, but it’s definitely better than no unit tests at all.
Nightly build are worse then continuous integration but are better than weekly builds, etc.
I agree that there is a kind of “click”, aka “when the team jells”, that happens when you’re correctly doing agile. Mmhh, I said one? Maybe there are several, one fore each step of agile you reach.
Not really sure anyhow, my personal experience is that when agile start to work, organizations reacts and dismantle agile teams.
Anyway I want to add other two Agile AntiPatterns I saw myself:
First signs: 40 hours a week is not a practice but a wish that will never came true. Iterations are fixed both in time and features, there’s no time for pair programming, spikes, crc/mindmap sessions.
Consequences: high turnover, personality problems, quality doesn’t improve much over the time. It’s like a tipical sofware sweatshop but usually managed by some “agile guru” with a bunch of underpaid newbies.
It happens when the Customer change his mind every iteration, and the Team continue to provide new estimates for more or less the same functionalities. At the end the project is cancelled because it’s too late on schedule but it’s still a “technical success”, that is a business failure. The best description I heard of this was at a Jeff Patton seminar at the XpDay2007 in London.
Posted in agile | Tagged: agile, agile sweatshop, anti-patterns, software development, technical success | Leave a Comment »
Posted by Uberto Barbini on March 23, 2008
I know I’m late, actually I’m always late so there’s nothing new here.
Anyway, some days ago, a post of mine in Milano Jug mailing list, has been quoted by .MOz on his blog.
This is his translation (my actual post was in Italian):
“Blockheads, agile or not, will never produce good code, just as even if you can produce the best software in the world but you don’t understand the domain your project is doomed: technical success is a foolish illusion.”
Maybe “blockheads” and “foolish illusion” are a bit too euphemistic for my tastes, but ok, the meaning is there.
Anyway if you don’t know me, you can think of it as a critique of Agile methods from my part, but it is not. I’m still regarding Agile Methodologies as the fastest and the most cost-effective way to develop software.
It’s only that they’re not a goal per se.
Being fair, probably 99% of Agile practitioners do agree here.
Moreover, methodology is not the Most Important Thing in Software Development, and neither the second one… probably it is the third one MITSD.
It’s like having a race between an old Fiat 500 and a Ferrari Maranello: if the Ferrari driver doesn’t know which way to turn, or if he doesn’t know how to drive a car… he simply cannot win.
Posted in agile | Tagged: agile, software development | Leave a Comment »