[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[epf-dev] "Selling" OpenUp...
|
As an end user of EPFC and OpenUP, I can tell you that I would greatly appreciate having additional materials around how to successfully use OpenUP.
Our very small shop (4 developers) is moving from having virtually no documented processes to a customized version of OpenUp and the amount of material to review, ingest and integrate with our unwritten process is nearly overwhelming.
Further, we will need to be able to eventually present OpenUp from the stakeholders' point of view and that will have to an even more simplified view.
That said, I really like the idea of having an abridged version of OpenUp as a starting place. It's essentially what I'm in the process of building now since my group does not want to try to delve into OpenUp too deep or too fast.
Jan Fincher
Business Applications Analyst
Division of Rehabilitation and Liquidation
jan.fincher@xxxxxxxxx
-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of epf-dev-request@xxxxxxxxxxx
Sent: Wednesday, August 29, 2007 12:31 PM
To: epf-dev@xxxxxxxxxxx
Subject: epf-dev Digest, Vol 20, Issue 39
Send epf-dev mailing list submissions to
epf-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/epf-dev
or, via email, send a message with subject or body 'help' to
epf-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
epf-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of epf-dev digest..."
Today's Topics:
1. Re: Wednesday Release Planning Call (Per Kroll)
2. Fw: Notes from today's call (Per Kroll)
----------------------------------------------------------------------
Message: 1
Date: Wed, 29 Aug 2007 12:13:31 -0400
From: Per Kroll <pkroll@xxxxxxxxxx>
Subject: Re: [epf-dev] Wednesday Release Planning Call
To: Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx>
Message-ID:
<OF2ADC32EE.009EE58F-ON85257346.0058CE1D-85257346.005921A6@xxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Paulo,
I think this is an excellent point.
I think that these examples needs to come from projects where people
harvest, versus being produced as examples... Otherwise people will not
see them as 'real'
Also, in practices, you need examples from different project types... We
have repeatadle run in to the problem when showing customers examples that
they say "hey, this is from insurance industry. We are in telecom. We
cannot use these examples..."
So, I think the solution needs to be that people are willing to harvest
(and clean up) actual artifacts. It is ok that they are imperfect. No
project produces all 'perfect' artifacts, you produce just enough for what
you need to move on....
So, if anybody has projects to harvest from, pls go ahead!
Cheers
Per Kroll
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
(M) 408-219-2963
Paulo Moreira <p_r_moreira@xxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
08/29/2007 10:59 AM
Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>
To
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>
cc
Subject
Re: [epf-dev] Wednesday Release Planning Call
Hello,
I just want to say some words to collaborate :-)
Here in Brazil, i see people leaving college with no knowledge of software
development process, but they want to learn a process that gives them a
way to do their job.
IMHO, i think if we give to community, complete examples(cases) of the
process with all artifacts filled and linked/related with tasks that
generate it, something like a reverse approach to the normal way of using
a process, it will be easier to learn the process because they will have
concrete things on hand, that could be adapted to their reality.
hope this help,
Cheers,
Paulo Moreira
PS: Perhaps some kind of survey can help to catch the community desire.
Steve Adolph <steve@xxxxxxxxxxxxxxxxx> escreveu:
Hello everyone:
After last week?s call, I was thinking more about what I believe is
necessary to include in the next release of OpenUP. In my opinion a
methodology does not survive and prosper based on its own merits, it
survives because there is a community. IMHO, XP and Scrum have taken off
because they are easy to get started with (although the ease of getting
started does not necessarily imply ease of use), they have charismatic
champions telling their audience what the audience wants to hear. There is
a wide range of supporting material including books and courses to help
people get started with these methods. If OpenUP is to survive and find
its place in the hearts and minds of developers then we need to focus on
capturing people?s imaginations. In this era of 10 second sound bites we
need to do that quickly. I would like to propose the following activities
for general and overarching issues:
1) We need an OpenUP course ? or more to the point, course material
we can spin into a half day tutorial or re-spin into a two day ?hands on?
workshop. Something that not only introduced OpenUP but iterative
development. A possible course title is ?Iterative Development with
OpenUP?.
2) I think we need a version of OpenUP that is less intimidating than
the version we have at the moment. OpenUP is suppose to be for small teams
yet it has the appearance of a voluminous and complex process. What if we
created some kind of ?abridged? version that reduced the cognitive load on
the early adopters? This version would not be maintained as part of the
composer. Rather, it would be more like a cheat sheet that simply captured
the essence, phase, iterations, work item list, focus on architecture,
risk management. A version that if a person took a half day OpenUP
tutorial they had at least a chance of making a positive change using
OpenUP.
3) I also believe we need to strongly encourage and support
translation efforts. I know there was some interest in creating a Russian
translation of OpenUP, but I do not know what has happened since.
4) A book? I was intrigued by the suggestion of creating a ?red
book?. I don?t know if I can physically sequester myself with a writing
team, but I am willing to wager that we have enough material between us to
create a simple book. Perhaps ?Post Agile Development with OpenUP?
These are just some thoughts I had for tomorrow?s call. Look forward to
chatting with you all?
Steve
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
Flickr agora em português. Você clica, todo mundo vê. Saiba mais.
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://dev.eclipse.org/mailman/listinfo/epf-dev/attachments/20070829/d4fdf58e/attachment.html
------------------------------
Message: 2
Date: Wed, 29 Aug 2007 10:07:03 -0600
From: Per Kroll <pkroll@xxxxxxxxxx>
Subject: [epf-dev] Fw: Notes from today's call
To: "EPF Dev " <epf-dev@xxxxxxxxxxx>
Message-ID:
<OFECD782D1.59B85BEF-ON85257346.00587E93-85257346.00588A88@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: Aug 29 EPF PlanningTelecon.doc
Type: application/octet-stream
Size: 51712 bytes
Desc: not available
Url : https://dev.eclipse.org/mailman/listinfo/epf-dev/attachments/20070829/b6c3ca1f/Aug29EPFPlanningTelecon.obj
------------------------------
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
End of epf-dev Digest, Vol 20, Issue 39
***************************************
