I'm familiar with the Harmony process promoted alongside Rhapsody. It's obvious that the process has a lot in common with Agile Methods (Extreme programming aka Test Driven Development) only the emphasis is on the model rather than the code.

Of course, with Rhapsody, the model and code are one in the same so this makes sense. A realization of Rhapsody's ability to raise the level of abstraction by the Agile Community is only a matter of time.

Anyone agree

Yes

Luke.

Looks like it's just you and me Luke.

I can only conclude that there's still lots of Waterfall process going on out there.

I wonder what would happen if a company took a chance and really embraced Agile and Rhapsody? I hear BPD's next book is going to be about this subject. An obvious link from Harmony already exists.

Two comments,
1. I know that there are some groups at a large defense industry company that makes airplanes in Fort Worth, Texas (have I been obvious enough) that uses Agile with Rhapsody. They are not doing the test driven development yet, but are looking into it. The teams that embrace Agile (that is, really do it, not just say they are) are being fairly successful.

2. My own development teams did a flavor of Agile relying heavily on Rhapsody and UML-based modeling. I kept the sprints to two weeks (occasionally, I had to extend it because we didn't quite finish). At first, the Program Manager hated it because I was giving schedule warnings very early. Soon, he saw they were real and tried to get the electrical guys running on the same type of schedule.

So yes, Agile and Rhapsody go very well together.

BTW: Didn't Scott Ambler used to write about Agile and UML? I seem to recall reading lots of articles in his Dr. Dobbs column about it.

OK, so BPD has published a book on this. I've just ordered it. I'll read it and post my opinion.

http://www.amazon.co.uk/Real-Time-Agili ... 0321545494