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.