Home » Archived » EPF » Please Provide Feedback on OpenUP
| Please Provide Feedback on OpenUP [message #23738] |
Wed, 15 November 2006 12:16  |
Eclipse User |
|
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<small><font size="+2"><small>The Eclipse Process Framework committers
are interested in knowing how well people are doing in deploying
OpenUP/Basic 0.9. There have been thousands of downloads of the process
but we haven't received much feedback on the results people are
experiencing. Understanding the successes and failures the OpenUP
community is experiencing will help us to deliver more value in the
future.<br>
<br>
If you've used OpenUP/Basic, even if it was just to review it as a
potential process you might use, please respond to this post and answer
the questions below. It should only take a couple of minutes of your
time. You'll be helping to improve OpenUP for yourself and others.<br>
</small></font></small>
<ul>
<li><big>If you decided not to use OpenUP, please explain why.</big></li>
<li><big>How successful were you in deploying OpenUP? What specific
problems did you encounter (e.g. lack of training, couldn't understand
a particular guideline, etc)? What parts of the process were easy to
deploy?</big></li>
<li><big>Are you using it as-is or are you modifying it?<br>
</big></li>
<li><big>If you're using EPF Composer, to what extent are you
modifying OpenUP (e.g. minor text changes, replacing templates,
changing entire disciplines, etc)?</big></li>
<li><big>What are the characteristics of your project (head count,
timeframe, industry, greenfield or maintenance, successful delivery,
etc)?</big></li>
</ul>
<big><big><small>Thanks for your input,<br>
<br>
Jim Ruehlin, EPF Committer<br>
<a class="moz-txt-link-abbreviated" href="mailto:jruehlin@us.ibm.com">jruehlin@us.ibm.com</a></small><br>
</big></big><br>
</body>
</html>
|
|
|
| Re: Please Provide Feedback on OpenUP [message #23829 is a reply to message #23738] |
Wed, 15 November 2006 19:08  |
| Eclipse User |
|
|
|
Jim... this post sould be placed on the site as well, near the download
section
Ana Pereira
Jim Ruehlin wrote:
> The Eclipse Process Framework committers are interested in knowing how
> well people are doing in deploying OpenUP/Basic 0.9. There have been
> thousands of downloads of the process but we haven't received much
> feedback on the results people are experiencing. Understanding the
> successes and failures the OpenUP community is experiencing will help us
> to deliver more value in the future.
>
> If you've used OpenUP/Basic, even if it was just to review it as a
> potential process you might use, please respond to this post and answer
> the questions below. It should only take a couple of minutes of your
> time. You'll be helping to improve OpenUP for yourself and others.
>
> * If you decided not to use OpenUP, please explain why.
> * How successful were you in deploying OpenUP? What specific
> problems did you encounter (e.g. lack of training, couldn't
> understand a particular guideline, etc)? What parts of the process
> were easy to deploy?
> * Are you using it as-is or are you modifying it?
> * If you're using EPF Composer, to what extent are you modifying
> OpenUP (e.g. minor text changes, replacing templates, changing
> entire disciplines, etc)?
> * What are the characteristics of your project (head count,
> timeframe, industry, greenfield or maintenance, successful
> delivery, etc)?
>
> Thanks for your input,
>
> Jim Ruehlin, EPF Committer
> jruehlin@us.ibm.com
>
|
|
|
| Re: Please Provide Feedback on OpenUP [message #25115 is a reply to message #23829] |
Thu, 30 November 2006 20:30 |
| Eclipse User |
|
|
|
Great idea Ana. Done.
"Ana Valente Pereira" <apereira@whatever.pt> wrote in message
news:ejga5d$ppi$1@utils.eclipse.org...
> Jim... this post sould be placed on the site as well, near the download
> section
>
> Ana Pereira
>
> Jim Ruehlin wrote:
>> The Eclipse Process Framework committers are interested in knowing how
>> well people are doing in deploying OpenUP/Basic 0.9. There have been
>> thousands of downloads of the process but we haven't received much
>> feedback on the results people are experiencing. Understanding the
>> successes and failures the OpenUP community is experiencing will help us
>> to deliver more value in the future.
>>
>> If you've used OpenUP/Basic, even if it was just to review it as a
>> potential process you might use, please respond to this post and answer
>> the questions below. It should only take a couple of minutes of your
>> time. You'll be helping to improve OpenUP for yourself and others.
>>
>> * If you decided not to use OpenUP, please explain why.
>> * How successful were you in deploying OpenUP? What specific
>> problems did you encounter (e.g. lack of training, couldn't
>> understand a particular guideline, etc)? What parts of the process
>> were easy to deploy?
>> * Are you using it as-is or are you modifying it?
>> * If you're using EPF Composer, to what extent are you modifying
>> OpenUP (e.g. minor text changes, replacing templates, changing
>> entire disciplines, etc)?
>> * What are the characteristics of your project (head count,
>> timeframe, industry, greenfield or maintenance, successful
>> delivery, etc)?
>>
>> Thanks for your input,
>>
>> Jim Ruehlin, EPF Committer
>> jruehlin@us.ibm.com
>>
|
|
|
| Re: Please Provide Feedback on OpenUP [message #25807 is a reply to message #23738] |
Tue, 19 December 2006 15:19 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0042_01C72367.E4267E00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We are preparing to define our updated processes in EPF. We have used a =
Wiki (TWiki) for the past several years to document our Product Release =
Life Cycle (PRLC), but have found maintenance of the information to be =
difficult.
If you decided not to use OpenUP, please explain why.=20
1.. The concepts and terminology of OpenUP are too different from our =
existing process definition. We are not prepared to force a change in =
terminology just to implement a tool.=20
2.. The nature of our major product lines requires a lot of attention =
to commitments, coordination, integration, and release that aren't =
covered in OpenUP. OpenUp defines a good, simple development LC for =
Agile projects that is useful for only a (small) subset of the work we =
do. We need much more for complex projects, and to redefine our more =
traditional lifecycle model, we'd have a lot of embellishment to do.
3.. We have not particular problem with OpenUP, and may use it in the =
future. Right now though, our focus is on our major, distributed, =
multi-team development LC.
How successful were you in deploying OpenUP? What specific problems did =
you encounter (e.g. lack of training, couldn't understand a particular =
guideline, etc)? What parts of the process were easy to deploy?=20
Well, we did look at it before deciding to roll our own, and the change =
was too big a pill to swallow.
Are you using it as-is or are you modifying it?
N/A
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're using OpenUP as an example of how to use the various model element =
types. To be honest, if the documentation were more complete/usable, =
that probably wouldn't be necessary.
What are the characteristics of your project (head count, timeframe, =
industry, greenfield or maintenance, successful delivery, etc)?=20
a.. Our market is Device Software Optimization - a methodology that =
enables companies to develop and run device software faster, better, at =
lower cost, and more reliably. Our customers sell into the automotive, =
aerospace and defense, telecommunications, industrial, and consumer =
products markets.=20
b.. We produce coordinated releases of our three major product lines =
(VxWorks, Linux, and Workbench) about twice yearly. Our work involves =
the parallel development and release of new features and the maintenance =
of existing supported products.
c.. We are updating process descriptions covering the engineering and =
management activities of about 400 people at 12 sites worldwide. We are =
using EPF to define a suite of uniform engineering (and related =
marketing and support) processes covering product requirements =
elicitation through product end of life, that will be tailored and used =
by all of our development projects worldwide.=20
d.. We will be rolling the initial updates out in iterations over the =
coming 6 months. After that, we'll be routinely improving and =
republishing the work.
"Jim Ruehlin" <jruehlin@us.ibm.com> wrote in message =
news:ejfi2g$7gl$1@utils.eclipse.org...
The Eclipse Process Framework committers are interested in knowing how =
well people are doing in deploying OpenUP/Basic 0.9. There have been =
thousands of downloads of the process but we haven't received much =
feedback on the results people are experiencing. Understanding the =
successes and failures the OpenUP community is experiencing will help us =
to deliver more value in the future.
If you've used OpenUP/Basic, even if it was just to review it as a =
potential process you might use, please respond to this post and answer =
the questions below. It should only take a couple of minutes of your =
time. You'll be helping to improve OpenUP for yourself and others.
a.. If you decided not to use OpenUP, please explain why.=20
b.. How successful were you in deploying OpenUP? What specific =
problems did you encounter (e.g. lack of training, couldn't understand a =
particular guideline, etc)? What parts of the process were easy to =
deploy?=20
c.. Are you using it as-is or are you modifying it?
d.. If you're using EPF Composer, to what extent are you modifying =
OpenUP (e.g. minor text changes, replacing templates, changing entire =
disciplines, etc)?=20
e.. What are the characteristics of your project (head count, =
timeframe, industry, greenfield or maintenance, successful delivery, =
etc)?=20
Thanks for your input,
Jim Ruehlin, EPF Committer
jruehlin@us.ibm.com
------=_NextPart_000_0042_01C72367.E4267E00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D1><BIG>We are preparing to define our =
updated=20
processes in EPF. We have used a Wiki (TWiki) for the past several years =
to=20
document our Product Release Life Cycle (PRLC), but have found =
maintenance of=20
the information to be difficult.</BIG></FONT></DIV>
<DIV><FONT face=3DArial><FONT =
size=3D1><BIG></BIG></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D1><EM><BIG>If you decided not to =
use OpenUP,=20
please explain why.</BIG> </EM></FONT></FONT></DIV>
<OL>
<LI><FONT face=3DArial size=3D2>The concepts and terminology of OpenUP =
are too=20
different from our existing process definition. We are not prepared to =
force a=20
change in terminology just to implement a tool. </FONT></LI>
<LI><FONT face=3DArial size=3D2>The nature of our major product=20
lines requires a lot of attention to commitments, coordination,=20
integration, and release that aren't covered in OpenUP. OpenUp defines =
a good,=20
simple development LC for <EM>Agile</EM> projects that is useful for =
only a=20
(small) subset of the work we do. We need much more for complex =
projects, and=20
to redefine our more traditional lifecycle model, we'd have =
a lot of=20
embellishment to do.</FONT></LI>
<LI><FONT face=3DArial size=3D2>We have not particular problem with =
OpenUP, and=20
may use it in the future. Right now though, our focus is on our major, =
distributed, multi-team development LC.</FONT></LI></OL>
<DIV><FONT face=3DArial><FONT size=3D1><EM><BIG>How successful were you =
in deploying=20
OpenUP? What specific problems did you encounter (e.g. lack of training, =
couldn't understand a particular guideline, etc)? What parts of the =
process were=20
easy to deploy?</BIG> </EM></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Well, we did look at it before deciding =
to roll our=20
own, and the change was too big a pill to swallow.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><BIG><FONT face=3DArial><FONT size=3D2><EM>Are you using it as-is =
or are you=20
modifying it?</EM></FONT></FONT></BIG></DIV>
<DIV><BIG><EM><FONT face=3DArial size=3D2>N/A</FONT></EM></BIG></DIV>
<DIV><BIG><FONT face=3DArial><FONT =
size=3D2></FONT> </DIV></FONT></BIG>
<DIV><FONT face=3DArial><FONT size=3D1><EM><BIG>If you're using EPF =
Composer, to=20
what extent are you modifying OpenUP (e.g. minor text changes, replacing =
templates, changing entire disciplines, =
etc)?</BIG></EM></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D1><BIG>We're using OpenUP as an =
example of how=20
to use the various model element types. To be honest, if the =
documentation were=20
more complete/usable, that probably wouldn't be=20
necessary.</BIG></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D1><BIG><EM>What are the =
characteristics of your=20
project (head count, timeframe, industry, greenfield or maintenance, =
successful=20
delivery, etc)?</EM></BIG> </FONT></FONT></DIV>
<UL><FONT face=3DArial size=3D2>
<LI><FONT face=3DArial size=3D2>Our market is Device Software =
Optimization - a=20
methodology that enables companies to develop and run device software =
faster,=20
better, at lower cost, and more reliably. Our customers sell into =
the=20
automotive, aerospace and defense, telecommunications, industrial, and =
consumer products markets. </FONT></LI>
<LI><FONT face=3DArial size=3D2>We produce coordinated releases of our =
three major=20
product lines (VxWorks, Linux, and Workbench) about twice yearly. Our =
work=20
involves the parallel development and release of new features and the=20
maintenance of existing supported products.</FONT></LI>
<LI>We are updating process descriptions covering the engineering and=20
management activities of about 400 people at 12 sites worldwide. =
</FONT><FONT=20
face=3DArial size=3D2><FONT face=3DArial size=3D2>We are using EPF to =
define a suite=20
of uniform engineering (and related marketing and support) processes =
covering=20
product requirements elicitation through product end of life, that =
will be=20
tailored and used by all of our development projects worldwide.=20
</FONT></LI>
<LI>We will be rolling the initial updates out in iterations =
over=20
the coming 6 months. After that, we'll be routinely improving and =
republishing=20
the work.</FONT></LI></UL>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV><FONT size=3D1>"Jim Ruehlin" <</FONT><A=20
href=3D"mailto:jruehlin@us.ibm.com"><FONT=20
size=3D1>jruehlin@us.ibm.com</FONT></A><FONT size=3D1>> wrote in =
message=20
</FONT><A href=3D"news:ejfi2g$7gl$1@utils.eclipse.org"><FONT=20
size=3D1>news:ejfi2g$7gl$1@utils.eclipse.org</FONT></A><FONT=20
size=3D1>...</FONT></DIV><SMALL><SMALL>The Eclipse Process Framework =
committers=20
are interested in knowing how well people are doing in deploying =
OpenUP/Basic=20
0.9. There have been thousands of downloads of the process but we =
haven't=20
received much feedback on the results people are experiencing. =
Understanding=20
the successes and failures the OpenUP community is experiencing will =
help us=20
to deliver more value in the future.<BR><BR>If you've used =
OpenUP/Basic, even=20
if it was just to review it as a potential process you might use, =
please=20
respond to this post and answer the questions below. It should only =
take a=20
couple of minutes of your time. You'll be helping to improve OpenUP =
for=20
yourself and others.<BR></SMALL></SMALL>
<UL>
<LI><FONT size=3D1><BIG>If you decided not to use OpenUP, please =
explain=20
why.</BIG> </FONT>
<LI><FONT size=3D1><BIG>How successful were you in deploying OpenUP? =
What=20
specific problems did you encounter (e.g. lack of training, couldn't =
understand a particular guideline, etc)? What parts of the process =
were easy=20
to deploy?</BIG> </FONT>
<LI><BIG><FONT size=3D1>Are you using it as-is or are you modifying=20
it?<BR></FONT></BIG>
<LI><FONT size=3D1><BIG>If you're using EPF Composer, to what extent =
are you=20
modifying OpenUP (e.g. minor text changes, replacing templates, =
changing=20
entire disciplines, etc)?</BIG> </FONT>
<LI><FONT size=3D1><BIG>What are the characteristics of your project =
(head=20
count, timeframe, industry, greenfield or maintenance, successful =
delivery,=20
etc)?</BIG> </FONT></LI></UL><BIG><BIG><SMALL><FONT size=3D1>Thanks =
for your=20
input,<BR><BR>Jim Ruehlin, EPF Committer<BR></FONT><A=20
class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:jruehlin@us.ibm.com"><FONT=20
=
size=3D1>jruehlin@us.ibm.com</FONT></A></SMALL><BR></BIG></BIG><BR></BLOC=
KQUOTE></BODY></HTML>
------=_NextPart_000_0042_01C72367.E4267E00--
|
|
|
| Re: Please Provide Feedback on OpenUP [message #568603 is a reply to message #23738] |
Wed, 15 November 2006 19:08 |
| Eclipse User |
|
|
|
Jim... this post sould be placed on the site as well, near the download
section
Ana Pereira
Jim Ruehlin wrote:
> The Eclipse Process Framework committers are interested in knowing how
> well people are doing in deploying OpenUP/Basic 0.9. There have been
> thousands of downloads of the process but we haven't received much
> feedback on the results people are experiencing. Understanding the
> successes and failures the OpenUP community is experiencing will help us
> to deliver more value in the future.
>
> If you've used OpenUP/Basic, even if it was just to review it as a
> potential process you might use, please respond to this post and answer
> the questions below. It should only take a couple of minutes of your
> time. You'll be helping to improve OpenUP for yourself and others.
>
> * If you decided not to use OpenUP, please explain why.
> * How successful were you in deploying OpenUP? What specific
> problems did you encounter (e.g. lack of training, couldn't
> understand a particular guideline, etc)? What parts of the process
> were easy to deploy?
> * Are you using it as-is or are you modifying it?
> * If you're using EPF Composer, to what extent are you modifying
> OpenUP (e.g. minor text changes, replacing templates, changing
> entire disciplines, etc)?
> * What are the characteristics of your project (head count,
> timeframe, industry, greenfield or maintenance, successful
> delivery, etc)?
>
> Thanks for your input,
>
> Jim Ruehlin, EPF Committer
> jruehlin@us.ibm.com
>
|
|
|
| Re: Please Provide Feedback on OpenUP [message #573842 is a reply to message #23829] |
Thu, 30 November 2006 20:30 |
| Eclipse User |
|
|
|
Great idea Ana. Done.
"Ana Valente Pereira" <apereira@whatever.pt> wrote in message
news:ejga5d$ppi$1@utils.eclipse.org...
> Jim... this post sould be placed on the site as well, near the download
> section
>
> Ana Pereira
>
> Jim Ruehlin wrote:
>> The Eclipse Process Framework committers are interested in knowing how
>> well people are doing in deploying OpenUP/Basic 0.9. There have been
>> thousands of downloads of the process but we haven't received much
>> feedback on the results people are experiencing. Understanding the
>> successes and failures the OpenUP community is experiencing will help us
>> to deliver more value in the future.
>>
>> If you've used OpenUP/Basic, even if it was just to review it as a
>> potential process you might use, please respond to this post and answer
>> the questions below. It should only take a couple of minutes of your
>> time. You'll be helping to improve OpenUP for yourself and others.
>>
>> * If you decided not to use OpenUP, please explain why.
>> * How successful were you in deploying OpenUP? What specific
>> problems did you encounter (e.g. lack of training, couldn't
>> understand a particular guideline, etc)? What parts of the process
>> were easy to deploy?
>> * Are you using it as-is or are you modifying it?
>> * If you're using EPF Composer, to what extent are you modifying
>> OpenUP (e.g. minor text changes, replacing templates, changing
>> entire disciplines, etc)?
>> * What are the characteristics of your project (head count,
>> timeframe, industry, greenfield or maintenance, successful
>> delivery, etc)?
>>
>> Thanks for your input,
>>
>> Jim Ruehlin, EPF Committer
>> jruehlin@us.ibm.com
>>
|
|
|
| Re: Please Provide Feedback on OpenUP [message #574238 is a reply to message #23738] |
Tue, 19 December 2006 15:19 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0042_01C72367.E4267E00
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
We are preparing to define our updated processes in EPF. We have used a =
Wiki (TWiki) for the past several years to document our Product Release =
Life Cycle (PRLC), but have found maintenance of the information to be =
difficult.
If you decided not to use OpenUP, please explain why.=20
1.. The concepts and terminology of OpenUP are too different from our =
existing process definition. We are not prepared to force a change in =
terminology just to implement a tool.=20
2.. The nature of our major product lines requires a lot of attention =
to commitments, coordination, integration, and release that aren't =
covered in OpenUP. OpenUp defines a good, simple development LC for =
Agile projects that is useful for only a (small) subset of the work we =
do. We need much more for complex projects, and to redefine our more =
traditional lifecycle model, we'd have a lot of embellishment to do.
3.. We have not particular problem with OpenUP, and may use it in the =
future. Right now though, our focus is on our major, distributed, =
multi-team development LC.
How successful were you in deploying OpenUP? What specific problems did =
you encounter (e.g. lack of training, couldn't understand a particular =
guideline, etc)? What parts of the process were easy to deploy?=20
Well, we did look at it before deciding to roll our own, and the change =
was too big a pill to swallow.
Are you using it as-is or are you modifying it?
N/A
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're using OpenUP as an example of how to use the various model element =
types. To be honest, if the documentation were more complete/usable, =
that probably wouldn't be necessary.
What are the characteristics of your project (head count, timeframe, =
industry, greenfield or maintenance, successful delivery, etc)?=20
a.. Our market is Device Software Optimization - a methodology that =
enables companies to develop and run device software faster, better, at =
lower cost, and more reliably. Our customers sell into the automotive, =
aerospace and defense, telecommunications, industrial, and consumer =
products markets.=20
b.. We produce coordinated releases of our three major product lines =
(VxWorks, Linux, and Workbench) about twice yearly. Our work involves =
the parallel development and release of new features and the maintenance =
of existing supported products.
c.. We are updating process descriptions covering the engineering and =
management activities of about 400 people at 12 sites worldwide. We are =
using EPF to define a suite of uniform engineering (and related =
marketing and support) processes covering product requirements =
elicitation through product end of life, that will be tailored and used =
by all of our development projects worldwide.=20
d.. We will be rolling the initial updates out in iterations over the =
coming 6 months. After that, we'll be routinely improving and =
republishing the work.
"Jim Ruehlin" <jruehlin@us.ibm.com> wrote in message =
news:ejfi2g$7gl$1@utils.eclipse.org...
The Eclipse Process Framework committers are interested in knowing how =
well people are doing in deploying OpenUP/Basic 0.9. There have been =
thousands of downloads of the process but we haven't received much =
feedback on the results people are experiencing. Understanding the =
successes and failures the OpenUP community is experiencing will help us =
to deliver more value in the future.
If you've used OpenUP/Basic, even if it was just to review it as a =
potential process you might use, please respond to this post and answer =
the questions below. It should only take a couple of minutes of your =
time. You'll be helping to improve OpenUP for yourself and others.
a.. If you decided not to use OpenUP, please explain why.=20
b.. How successful were you in deploying OpenUP? What specific =
problems did you encounter (e.g. lack of training, couldn't understand a =
particular guideline, etc)? What parts of the process were easy to =
deploy?=20
c.. Are you using it as-is or are you modifying it?
d.. If you're using EPF Composer, to what extent are you modifying =
OpenUP (e.g. minor text changes, replacing templates, changing entire =
disciplines, etc)?=20
e.. What are the characteristics of your project (head count, =
timeframe, industry, greenfield or maintenance, successful delivery, =
etc)?=20
Thanks for your input,
Jim Ruehlin, EPF Committer
jruehlin@us.ibm.com
------=_NextPart_000_0042_01C72367.E4267E00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D1><BIG>We are preparing to define our =
updated=20
processes in EPF. We have used a Wiki (TWiki) for the past several years =
to=20
document our Product Release Life Cycle (PRLC), but have found =
maintenance of=20
the information to be difficult.</BIG></FONT></DIV>
<DIV><FONT face=3DArial><FONT =
size=3D1><BIG></BIG></FONT></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D1><EM><BIG>If you decided not to =
use OpenUP,=20
please explain why.</BIG> </EM></FONT></FONT></DIV>
<OL>
<LI><FONT face=3DArial size=3D2>The concepts and terminology of OpenUP =
are too=20
different from our existing process definition. We are not prepared to =
force a=20
change in terminology just to implement a tool. </FONT></LI>
<LI><FONT face=3DArial size=3D2>The nature of our major product=20
lines requires a lot of attention to commitments, coordination,=20
integration, and release that aren't covered in OpenUP. OpenUp defines =
a good,=20
simple development LC for <EM>Agile</EM> projects that is useful for =
only a=20
(small) subset of the work we do. We need much more for complex =
projects, and=20
to redefine our more traditional lifecycle model, we'd have =
a lot of=20
embellishment to do.</FONT></LI>
<LI><FONT face=3DArial size=3D2>We have not particular problem with =
OpenUP, and=20
may use it in the future. Right now though, our focus is on our major, =
distributed, multi-team development LC.</FONT></LI></OL>
<DIV><FONT face=3DArial><FONT size=3D1><EM><BIG>How successful were you =
in deploying=20
OpenUP? What specific problems did you encounter (e.g. lack of training, =
couldn't understand a particular guideline, etc)? What parts of the =
process were=20
easy to deploy?</BIG> </EM></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Well, we did look at it before deciding =
to roll our=20
own, and the change was too big a pill to swallow.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><BIG><FONT face=3DArial><FONT size=3D2><EM>Are you using it as-is =
or are you=20
modifying it?</EM></FONT></FONT></BIG></DIV>
<DIV><BIG><EM><FONT face=3DArial size=3D2>N/A</FONT></EM></BIG></DIV>
<DIV><BIG><FONT face=3DArial><FONT =
size=3D2></FONT> </DIV></FONT></BIG>
<DIV><FONT face=3DArial><FONT size=3D1><EM><BIG>If you're using EPF =
Composer, to=20
what extent are you modifying OpenUP (e.g. minor text changes, replacing =
templates, changing entire disciplines, =
etc)?</BIG></EM></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D1><BIG>We're using OpenUP as an =
example of how=20
to use the various model element types. To be honest, if the =
documentation were=20
more complete/usable, that probably wouldn't be=20
necessary.</BIG></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial><FONT size=3D1><BIG><EM>What are the =
characteristics of your=20
project (head count, timeframe, industry, greenfield or maintenance, =
successful=20
delivery, etc)?</EM></BIG> </FONT></FONT></DIV>
<UL><FONT face=3DArial size=3D2>
<LI><FONT face=3DArial size=3D2>Our market is Device Software =
Optimization - a=20
methodology that enables companies to develop and run device software =
faster,=20
better, at lower cost, and more reliably. Our customers sell into =
the=20
automotive, aerospace and defense, telecommunications, industrial, and =
consumer products markets. </FONT></LI>
<LI><FONT face=3DArial size=3D2>We produce coordinated releases of our =
three major=20
product lines (VxWorks, Linux, and Workbench) about twice yearly. Our =
work=20
involves the parallel development and release of new features and the=20
maintenance of existing supported products.</FONT></LI>
<LI>We are updating process descriptions covering the engineering and=20
management activities of about 400 people at 12 sites worldwide. =
</FONT><FONT=20
face=3DArial size=3D2><FONT face=3DArial size=3D2>We are using EPF to =
define a suite=20
of uniform engineering (and related marketing and support) processes =
covering=20
product requirements elicitation through product end of life, that =
will be=20
tailored and used by all of our development projects worldwide.=20
</FONT></LI>
<LI>We will be rolling the initial updates out in iterations =
over=20
the coming 6 months. After that, we'll be routinely improving and =
republishing=20
the work.</FONT></LI></UL>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV><FONT size=3D1>"Jim Ruehlin" <</FONT><A=20
href=3D"mailto:jruehlin@us.ibm.com"><FONT=20
size=3D1>jruehlin@us.ibm.com</FONT></A><FONT size=3D1>> wrote in =
message=20
</FONT><A href=3D"news:ejfi2g$7gl$1@utils.eclipse.org"><FONT=20
size=3D1>news:ejfi2g$7gl$1@utils.eclipse.org</FONT></A><FONT=20
size=3D1>...</FONT></DIV><SMALL><SMALL>The Eclipse Process Framework =
committers=20
are interested in knowing how well people are doing in deploying =
OpenUP/Basic=20
0.9. There have been thousands of downloads of the process but we =
haven't=20
received much feedback on the results people are experiencing. =
Understanding=20
the successes and failures the OpenUP community is experiencing will =
help us=20
to deliver more value in the future.<BR><BR>If you've used =
OpenUP/Basic, even=20
if it was just to review it as a potential process you might use, =
please=20
respond to this post and answer the questions below. It should only =
take a=20
couple of minutes of your time. You'll be helping to improve OpenUP =
for=20
yourself and others.<BR></SMALL></SMALL>
<UL>
<LI><FONT size=3D1><BIG>If you decided not to use OpenUP, please =
explain=20
why.</BIG> </FONT>
<LI><FONT size=3D1><BIG>How successful were you in deploying OpenUP? =
What=20
specific problems did you encounter (e.g. lack of training, couldn't =
understand a particular guideline, etc)? What parts of the process =
were easy=20
to deploy?</BIG> </FONT>
<LI><BIG><FONT size=3D1>Are you using it as-is or are you modifying=20
it?<BR></FONT></BIG>
<LI><FONT size=3D1><BIG>If you're using EPF Composer, to what extent =
are you=20
modifying OpenUP (e.g. minor text changes, replacing templates, =
changing=20
entire disciplines, etc)?</BIG> </FONT>
<LI><FONT size=3D1><BIG>What are the characteristics of your project =
(head=20
count, timeframe, industry, greenfield or maintenance, successful =
delivery,=20
etc)?</BIG> </FONT></LI></UL><BIG><BIG><SMALL><FONT size=3D1>Thanks =
for your=20
input,<BR><BR>Jim Ruehlin, EPF Committer<BR></FONT><A=20
class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:jruehlin@us.ibm.com"><FONT=20
=
size=3D1>jruehlin@us.ibm.com</FONT></A></SMALL><BR></BIG></BIG><BR></BLOC=
KQUOTE></BODY></HTML>
------=_NextPart_000_0042_01C72367.E4267E00--
|
|
|
Goto Forum:
Current Time: Wed May 07 23:44:40 EDT 2025
Powered by FUDForum. Page generated in 0.07108 seconds |
Home