Good morning Jim:
Two of my clients in Vancouver BC are using OpenUP. One is a vendor of e-commerce software with approximately 60 staff members, the other is a vendor of HR software with approximately 100 people on staff. For the initial adoption of OpenUP we had team sizes of approximately 10 and 7 people respectively. Why did we decide to use OpenUP? There were several reasons we used OpenUP, 1. OpenUP's focus on architecture and risk management 2. There was a perception of more structure with OpenUP than other agile methodologies on the part of the client. It may seem counter intuitive but good formalizations help "liberate" creativity. 3. None of the team members or management had objectives to OpenUP, but they did have concerns with their perceptions regarding other agile methodologies. 4. They had an available OpenUP expert (myself) to coach the team. Are we using it as is, or modifying it? We adapted OpenUP to assimilate practices already in use at the client sites. This consisted of mostly replacing documentation work products with wiki based work products. We did not use EPF composer. I know this is brief but I hope it helps. Best regards, Steve Adolph Consultant WSA Consulting Inc Vancouver BC From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Crowley, Jim Sent: Tuesday, August 21, 2007 8:54 AM To: [email protected] Subject: [epf-dev] Feedback on OpenUP On the website you had asked for feedback, even if we were just considering using OpenUP, so below is my feedback along with some questions: If you decided not to use OpenUP, why? - We are still undecided on this, but are leaning heavily towards using OpenUP. What specific problems did you encounter (e.g. lack of training, couldn't understand a particular guideline, etc)? - While you ask this question in relation to deployment, our biggest problem is getting legal acceptance. We are going to have to modify the content to some extent, and this raises some concerns about how do we add content without infringing on someone's intellectual property or copyrights? The biggest concern would be that whatever we added may end up looking too similar to what is already in RUP. Because we have employees that have worked with RUP in other shops, they are familiar with the process, so it's really hard to divorce them from the process when they add new content. Are you using it as-is or are you modifying it? - We will definitely be modifying it. We have some roles, guidance, and artifacts that we use in house that we would like to get added. If you're using EPF Composer, to what extent are you modifying OpenUP (e.g. minor text changes, replacing templates, changing entire disciplines, etc)? We would be using EPF Composer to make the changes mentioned in the last question. What are the characteristics of your project (head count, timeframe, industry, greenfield or maintenance, successful delivery, etc)? - We would start off with projects that had 10 - 50 people on them, and eventually work our way up to 100+ project members. We could have upwards of 5000 unique people accessing the content over the course of a year. My Questions: * Who are some of the shops that have already adopted OpenUP for more than just 6 - 10 developers? * What kind of legal issues, if any, have people run into as they add their own content? * Will there ever be a search feature in OpenUP? This is one thing that I know our people have liked in the past with RUP. * Will there ever be a search feature in your list archive? I had tried scanning to find answers to some of my questions, but there are a lot of posts to wade through without a search. Thanks, Jim Crowley -----Message Disclaimer----- This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to [EMAIL PROTECTED] and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation. Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act ("E-Sign") unless a specific statement to the contrary is included in this message. While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements.
_______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
