I was mildly surprised to read a paper on Rational's Unified Process (RUP) that looks distinctly agile. How to Fail with the RUP starts with a fairly thorough debunking of the Waterfall lifecycle model. It hammers home the importance of doing iterations. Inception, Elaboration, Construction and Transition are not just a fancy way of saying requirements, design, implementation, system test/deployment. I had heard that you could customize RUP to be a fairly agile process. I did not realize that it was the way Rational expects people to use it.
By the way, I found I had to mentally remind myself several times while reading the paper that the practices listed are exactly the opposite of what they would recommend.
[ Found via Jeff Sutherland's log ]
Update: cpm would like to thank the diligent reader who spotted the missing verb after "mentally" and the other diligent reader who spotted "by they way" earlier in the same sentence. I've found I usually cannot catch all the errors myself before publishing.