hiho,
We do a lot of work with companies -- often as small as yours -- as they
move into applying RUP. A pilot project is an important part of the
strategy. So is biting off just enough RUP so that it doesn't bury you.
The first thing to get in place is the overall lifecycle model. Make sure
everyone understands the RUP milestones and their real intent. Make sure
everyone understands how RUP applies an iterative model within the framework
provided by the phases/milestones.
Then visit each workflow and ask relevant questions. For example with the
requirements workflow: what do we do now, what works and what doesn't, how
much do we need to nail up front, how much can we do up front, how precise
does the customer want to be, how is our relationship with our customer, how
much will external forces require changes to the requirements, etc. For
each workflow decide how you are going to apply the RUP
activities/artifacts.
Revisit your previous understanding of the milestones and the iterative
model with your new understanding of how you will apply the workflows.
Make sure you are fitting into the issues of being use-case-driven and
architecture-centric. We've seen people go requirements crazy; we've seen
people go technology crazy. RUP works well when there is the right balance
of power amongst those two issues.
Lastly, realize that this is a people issue. Understand your company's
culture and make sure the transition can be demonstrated as supporting the
needs of the individual participants.
We've been to places that do a pilot project that just does some version of
the RUP Project Management workflow and Requirements and leaves the rest of
the stuff as-is (or as as-is as it can be when being fit into the iterative
model). Other places have attacked the lifecycle model and then focused on
testing and change management for the first go-around. You'll have to find
your own answer to "where will we get the most bang for our buck?"
-------- b
--
Brian G. Lyons
Number Six Software - Voted Rational's Best Complementary Service Provider
1655 North Fort Myer Drive, Suite 1100
Arlington, VA 22209-3196
http://www.numbersix.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Remco van Veenendaal
Sent: Friday, February 23, 2001 9:20 AM
To: [EMAIL PROTECTED]
Subject: (ROSE) Experiences introducing RUP
Hi,
Are there any people out there that can tell us of their experiences
introducing UML/RUP to their company?
We are a language technology company (about 20 people), have some experience
with visual modeling in Rose, but now we would like to switch our "ad hoc"
(my manager will kill me if she reads this) software engineering method to
RUP ("ad hoc" is fairly Ok for smaller companies, but now we are
growing...).
Our current idea is to try to use the RUP in a small pilot project and then
we will decide how to continue (yes, I've read the RUP HTML documentation).
Does this fit in the "good things" or in the "bad things" category? Ok, in
theory yes, but in practice?
Thanx in advance,
Remco
drs. R. van Veenendaal
Polderland Language & Speech Technology
Postbus 31070
6503 CB Nijmegen
Tel: +31-24-3522866
Fax: +31-24-3522860
WWW: WWW.Polderland.Nl
@Work: [EMAIL PROTECTED]
@Home: [EMAIL PROTECTED]
"Very funny Scotty, now beam down my clothes!"
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
