Scrum and RUP

Let us hypothesize that having a Scrum plug-in for RUP is an idea worth
pursuing. Then I have the following questions:
1. How good was the effort at the XP plug-in. Does it help or hurt? Did the
greater distribution cause the essence of XP to be more widely distributed,
or did the translation of XP into RUP cause XP to lose it's "soul?"
2. Given the meta model of a process within Rose, that is used to generate
RUP, how can an agile process be effectively described? The models of
processes that we used in our process management software always revolved
around hierarchies or tasks, with the lowest level tasks having estimates,
roles, inputs, outputs, techniques and task descriptions. And, of course,
each of the roles, techniques, inputs, and outputs were further described.
Is this type of metaphor appropriate for agile processes, or does this level
of delineation lead to them being fodder for M/S project,for "hands-off"
management, and for robotic tracking of plans while ignoring realities?
3. If the first two questions are adequately addressed, what is our best way
to proceed with the effort?
Ken



-----Original Message-----
From: Adriano Comai [mailto:comai@xxxxxx]
Sent: Sunday, December 15, 2002 2:35 AM
To: scrumdevelopment@xxxxxxxxxxxxxxx
Subject: R: [scrumdevelopment] great article on agile/waterfall re rup


Alan,

I agree, and I'm doing exactly the same thing, here in Italy.

Adriano Comai
www.analisi-disegno.com

> -----Messaggio originale-----
> Da: Alan Shalloway [mailto:alshall@xxxxxxxxxxxxxxxxx]
> Inviato: domenica 15 dicembre 2002 3.28
> A: scrumdevelopment@xxxxxxxxxxxxxxx
> Oggetto: RE: [scrumdevelopment] great article on agile/waterfall re rup

[...]
>
> 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


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/