Hi, The company I am consulting practicing RUP, it seems logical for her because she belongs in the Customer Service Industry category, an international OEM engineering firm. You will encounter countless meetings, documents, and the developing time is your own time. Your typical workday is 16 hours. The low week is 5 days and the peek is 6 days. OT compensation was in the last decade. :roll: Cheers, MCao
Anyone tried implementing RUP at their workplace??
I have, sort of, but that's the catch. Very few implement RUP at its full power. My personal experiences have included a very selective use of RUP accompanied with bad management. In other words, I have no basis to say whether it was the process, the partial implementation of the process, or the management who f****d up the project
Any links or case studies would be welcome..
Have you checked rational.com? They must have tons of marketing stuff (I mean, "case studies"
Keep in mind that RUP is a process *framework* - you are *supposed* to select what is appropriate for your project. Doing "full RUP" would be overkill for almost any project, and probably already has killed some. Rational even markets XP as an instance of RUP.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
My team started with RUP with extensive mentoring from Rational. We did a standard waterfall style with requirements gathering, use cases, design, construction, etc. for several years. We found we were dealing with overly large chunks of work, and recently shifted to an iterative development style with planning and tracking at story levels, like most agile methods. This is not a rejection of RUP; it is a legitimate customization of RUP. We still do our use cases, but we build them up one story at a time. We use Rational tools to connect use cases to a requirements matrix, and requirements design docs and everything else we do. Here's some info on our Story Driven Process.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
I'm currently working on a project using RUP and things are not going nearly as well as we had hoped. However, I strongly believe that it is not RUP that is the problem -- I'm not a proponent of RUP, but I can see that there's a lot of good there. I recommend that if you're interested in RUP then take Rational's advice -- do an assessment of an existing project, determine some part of the RUP that makes sense to use (make sure there's a benefit to using it) and try it. As you see more places that could benefit, introduce the portions of RUP that make sense to use. Do not try to start a new project using RUP "full bore" -- people need time to understand the what, why, and how of it and get used to the new process before they can get the full benefits from it. Well, that's my two cents. I hope you have high success. Burk
SCJP, SCJD, SCEA 5 "Any sufficiently analyzed magic is indistinguishable from science!" Agatha Heterodyne (Girl Genius)