[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [epf-dev] Wednesday Release Planning Call
- From: Per Kroll <pkroll@xxxxxxxxxx>
- Date: Wed, 29 Aug 2007 12:13:31 -0400
- Delivered-to: firstname.lastname@example.org
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!
Project Lead: Eclipse Process Framework
Rational Software, IBM Corp
|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
|Eclipse Process Framework Project Developers
|Re: [epf-dev] Wednesday Release Planning
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,
PS: Perhaps some kind of survey can help to catch the
Steve Adolph <steve@xxxxxxxxxxxxxxxxx>
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…
epf-dev mailing list
Flickr agora em português. Você clica, todo mundo
epf-dev mailing list