RE: great article on agile/waterfall re rup

Adriano:
I appreciate this and have just seen BDS' article as well because of it
- thanks.

I'm surprised Philippe said that and if he is lurking here I'd
appreciate his comments.  Until a little over a year ago, I admit not
knowing RUP very well and just dismissed it as a heavy methodology.  I
based this not on what I knew RUP to be but on the fact that every
company I knew that followed RUP was mired in a heavyweight process.  I
even had a student who came to one of my design pattern classes say -
"Please come to my firm, we've just implemented RUP and now all I do is
documentation!"

I finally decided I better actually learn something about it and read
Philippe's great book and Larman's as well.  At first I was skeptical -
did Rational _really_ suggest RUP was agile?  I finally had a great
conversation with Gary Pollice and found out - yes!  

My opinion of RUP has changed considerably out of this (I still like
Scrum best) and showing companies how to do RUP in an agile manner has
now become a possibility.

My point, however, is - since RUP _is_ so mis-applied, I think it is
important to talk about this aspect of it so people become aware that
this is _not_ what RUP is supposed to be.  Without exposing this at
every opportunity, many people will continue to be under a
misunderstanding of what RUP is.  Personally, I loved this article and
think it was exceptionally written and would love for many "heavy
weight" managers to read it.

Alan Shalloway, Sr. Consultant, CEO
office: 425-313-3065. mobile: 425-531-0810

Net Objectives' vision is effective software development without
suffering. Our mission is to assist software development teams in
accomplishing this through a combination of training and mentoring. 


-----Original Message-----
From: Adriano Comai [mailto:comai@xxxxxx] 
Sent: Saturday, December 14, 2002 12:14 PM
To: scrumdevelopment@xxxxxxxxxxxxxxx
Subject: R: [scrumdevelopment] great article on agile/waterfall re rup

Alan,

some time ago, I posted a reference to this article to the RUP-Forum,
asking
about why it was not published on Rational or Valtech websites.

Some Rational people answered they use it internally as a list of
"process
antipatterns".

Philippe Krutchen said (I quote from his email):

"And since we speak about this paper (How to fail with the RUP), for
various
reasons
[...], mostly because of the possible misinterpretations and malicious
misuses of what was initially thought as a "tongue in cheek" paper, we
have
not released it,
and I still wonder how this draft ended up on this web site. "

Anyway, on Rational restricted access website (www.rational.net) has
been
recently posted another interesting article about the same topics. It is
by
Black Diamond Software (a Rational Partner company), and you can find it
(look under "white papers") at www.bds.com . They ask for your email to
download it.

Adriano Comai
www.analisi-disegno.com

> -----Messaggio originale-----
> Da: Alan Shalloway <alshall@xxxxxxxxxxxxxxxxx>
> [mailto:alshall@xxxxxxxxxxxxxxxxx]
> Inviato: sabato 14 dicembre 2002 20.22
> A: scrumdevelopment@xxxxxxxxxxxxxxx
> Oggetto: [scrumdevelopment] great article on agile/waterfall re rup
>
>
> The title alone (How to Fail with the Rational Unified Process:
> Seven Steps to Pain and Suffering by Larman, Kruchten and Bittner)
> make this article worth reading ;)  See
> http://www.dcs.bbk.ac.uk/~cc/courses/isad/articles/larman01howto.pdf
>
> However, on page 2 (Figure 1) there is a "Changing Requirements Are
> the Norm" graph which shows the bigger the project, the more the
> requirements change as a % of the original.  This is precisely the
> point made earlier about why very large up-front requirements are
> virtually never that useful.  If you really need them because the
> project is big, by the time you get to using them they are out of
> date.  Nice to have some documentation about this.
>
> Great article - worth reading and recommending IMHO.
>
> Alan Shalloway
> CEO, Net Objectives
> www.netobjectives.com
>
>
> To Post a message, send it to:   scrumdevelopment@xxxxxxxxxxx
> To Unsubscribe, send a blank message to:
> scrumdevelopment-unsubscribe@xxxxxxxxxxx
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
>
>


To Post a message, send it to:   scrumdevelopment@xxxxxxxxxxx
To Unsubscribe, send a blank message to:
scrumdevelopment-unsubscribe@xxxxxxxxxxx 

Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/ 




To Post a message, send it to:   scrumdevelopment@xxxxxxxxxxx
To Unsubscribe, send a blank message to: 
scrumdevelopment-unsubscribe@xxxxxxxxxxx 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/