[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epf-dev] Renaming "Change Management" practice
|
Here is my summary of all the name changes
proposed so far, with pros and cons.
I'd like to discuss this at tomorrow's
meeting, and make this change for the upcoming minor release.
Note that the callin information for
has changed.
I've posted it below.
See you then.
Bruce MacIsaac
EPF Content
Status Call [Edit]
[Delete]
|
Date:
| Wednesday September
10, 2008
|
|
Time:
| 8:00 am - 9:00 am
|
|
Author:
| rbal1970
|
|
Repeat:
| This event repeats every week
until Friday October 31, 2008.
|
|
Type:
| Appointment
|
|
Reminder:
| There is a reminder set for
30 minutes before this event. |
Time is Pacific time.
Participant Passcode: 570921
Location Local Access (Preferred) Toll Free
Argentina 0800 666 3713
Australia, Sydney +61 (0) 2 8207 3478
Australia 1 800 065 224
Austria, Vienna +43 (0) 1 994 560 01
Austria 0800 295 351
Belgium, Brussels +32 (0) 2 300 1970
Belgium 0 800 76 199
Brazil, Sao Paulo +55 11 3351 7034
Canada and Caribbean 1-719-387-8316 1-866-907-1016
Chile 123 0020 9188
China, Northern Region 10 800 714 1267
China, Southern Region 10 800 140 1270
Colombia 01 800 518 0958
Czech Republic 800 700 467
Denmark, Copenhagen +45 70 14 50 72
Denmark 80 889 658
France, Paris +33 (0) 1 72 69 79 52
France 0 800 910 810
Germany, Frankfurt +49 (0) 69 12009 860
Germany 0 800 182 3970
Greece 00 800 161 2205 7826
Hong Kong +852 3008 0320 800 933 339
Hungary 06 800 167 29
Indonesia 001 803 017 7825
Ireland, Dublin +353 (0) 1 437 0823
Ireland 1 800 949 018
Israel 1 80 924 3006
Italy, Milan +39 02 897 819 60
Italy, Rome +39 06 833 604 24
Italy, Turin +39 011 2173 446
Italy 800 871 917
Japan, Tokyo +81 (0) 3 4455 1491
Japan 00531 16 0925
Luxembourg 800 2 3012
Malaysia 1 800 814 090
Mexico 001 800 514 7826
Monaco 800 93 510
Netherlands, Amsterdam +31 (0) 20 262 0120
Netherlands 0 800 022 3061
New Zealand 0 800 445 637
Norway 800 104 59
Poland 00 800 111 48 41
Portugal 800 819 980
Russia 810 800 2567 1012
Singapore 800 101 2139
South Africa 0 800 981 573
South Korea 003 0813 2179
Spain, Barcelona +34 93 802 2431
Spain, Madrid +34 91 829 8651
Spain, Valencia +34 96 314 0650
Spain 900 981 587
Sweden, Stockholm +46 (0) 8 5031 1718
Sweden 02 079 0504
Switzerland, Geneva +41 (0) 22 555 0213
Switzerland, Zurich +41 (0) 44 556 8423
Switzerland 0 800 895 072
Thailand 001 800 156 205 7826
UK, London +44 (0) 20 8150 0610
UK 0 808 101 5336
USA 1-719-387-8316 1-866-907-1016 |
|
|
|
Bruce MacIsaac
Manager - RUP/OpenUP Content
bmacisaa@xxxxxxxxxx
phone: (408)463-5140
Bruce Macisaac/Cupertino/IBM@IBMUS
Sent by: epf-dev-bounces@xxxxxxxxxxx
08/15/2008 08:19 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] Renaming "Change
Management" practice to "Basic Change Management" |
|
The meeting I called to try to resolve this didn't have quorum - just Chris
Sibbald and myself.
We agreed to defer any change for now, and discuss it at the next regular
meeting on Wed.
This means we'll leave the practice with its current name of "Change
Management", but on Wed we can discuss whether a name change for the
planned patch release in Oct would be
appropriate or not.
Bruce MacIsaac
| Bruce Macisaac/Cupertino/IBM
08/14/2008 02:01 PM
|
|
To
| Eclipse Process Framework
Project Developers List <epf-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [epf-dev] Renaming "Change
Management" practice to "Basic Change Management"Link |
|
Just to put another name out there for consideration:
Work Item Change Management.
to make it clear that change is managed via the work item list management,
not using a separate process.
Bruce MacIsaac
Manager - RUP/OpenUP Content
bmacisaa@xxxxxxxxxx
phone: (408)463-5140
"Ken Clyne" <ken.clyne@xxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
08/14/2008 12:02 PM
|
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
|
To
| "Eclipse Process Framework
Project Developers List" <epf-dev@xxxxxxxxxxx>
|
|
cc
| Brad Sandler/Raleigh/IBM@IBMUS, Lee
Gay/Houston/IBM@IBMUS, Shmuel Bashan <BASHANSH@xxxxxxxxxx>, Yvonne
M Dailey/Lexington/IBM@IBMUS, David J Trent/New York/IBM@IBMUS
|
|
Subject
| Re: [epf-dev] Renaming "Change
Management" practice to "Basic Change Management" |
|
I am doubtful for tomorrow but I do think this deserves further discussion.
I do not like the qualifiers before "Change Management"
as I don't think they capture the essence of what it is we are trying to
convey. They connote dumbing it down and we're not, this is deadly
serious but low ceremony. On today's projects the product backlog
is continuously evolving and changing in response to business needs and
technology. Defect, enhancement, new feature we don't really care.
So I think this practice belongs with other practices creating and
prioritizing the product backlog and I don't think right now this is the
Shared Vision practice. So my vote is for the status quo (Change
Management) until we can fix this and fix it right.
My 0.02d
On Thu, Aug 14, 2008 at 2:21 PM, Bruce Macisaac <bmacisaa@xxxxxxxxxx>
wrote:
Since tomorrow is the last day for making changes, we need to close
on this.
It may be fine to have a sub-optimal name for this release, and continue
the discussion for a follow-on release.
I propose a meeting to resolve this tomorrow morning 8am pacific time.
Toll-free dial-in:
1-877-421-0014
Toll/International dial-in: 1-770-615-1376
Tie-line dial-in:
421-0014
Participant passcode: 722417
If you can't make the meeting, then please clearly state your preferred
name, and whether you are able to help adjust the text by end of day tomorrow
to fit the new name,
or if you have more than one, then your favorite, next favorite, etc.
Here is mine, favorite first:
1. Informal Change Management
2. Basic Change Management
3. Change Management
Rationale:
a. It's a bit late in the game for a radical name change - the practice
descriptions have already been written in terms of "change management"
and it's an easy fix to add an adjective.
A more substantial name change means defining some new terms and possibly
rewriting a bigger chunk of text - I think it's late for that - but if
those suggesting the better name want
to do the work... :-)
b. Several of the other name proposals suffer from the same problem as
the original "change management" name - the name still doesn't
separate this informal variant from how this area is traditionally managed.
Bruce MacIsaac
Manager - RUP/OpenUP Content
bmacisaa@xxxxxxxxxx
phone: (408)463-5140
Hi.
For me "Change Management" is a discipline, but not a practice.
The difference is that change management just implies that a solution
for managing change is needed, but not the concrete set of practices and
procedure that are performed to achieve this need of managing change. The
same with Requirements Management or Project Management: Not practices,
just disciplines. Putting an ambiguous adjective such as Basic or Flexible
in-front of it makes it in IMHO even worse as it even becomes less clear
what it means. There is also no value communicated with these words.
Many of our other practices much better communicate what the practice is
actually about, such as Evolutionary Architecture, i.e. the practice of
not creating an architecture up-front, but evolving it out of the solution
development.
Hence, better names would be "everyone can request change" or
"state-machine driven change tracking" or "attribute-driven
work item list management". If we do not have a practice for actually
managing changes in OpenUP then the name should also reflect that such
as "submitting changes into a work item list" is all I can see
for now.
Thanks and best regards,
Peter Haumer.
______________________________________________________________
PETER HAUMER, Dr. rer. nat.
Rational Method Composer | Eclipse Process Framework
Rational Software | IBM Software Group
Tel.: +1 (408) 463-5096
______________________________________________________________
| From:
| "Ken Clyne" <ken.clyne@xxxxxxxxx>
|
| To:
| "Eclipse Process Framework Project
Developers List" <epf-dev@xxxxxxxxxxx>
|
| Date:
| 08/13/2008 12:51
|
| Subject:
| Re: [epf-dev] Renaming "Change
Management" practice to "Basic Change Management" |
Good dialog. Bruce I wasn't inferring we were claiming copyright
on "Change Management" but rather those people challenging your
use of the term were.
I like Ana's suggestion and Maciel's endorsement but also put forward one
of my own that is a bit a narrower but maybe apropos to the limited content
of this practice "Change Request Management".
On Wed, Aug 13, 2008 at 2:08 PM, Maciel, Eduardo (Brazil R&D) <maciel@xxxxxx>
wrote:
Hello all,
I´m not sure if contributions
are expected from non usual contributors, such as me, but I´d like to opine
about this subject.
I agree with Ana Pereira. In
my humble opinion, Scope Management is the best term.
- For most
of people Change Management reminds a very strict and formal process.
- By "managing
the scope" one can understand it comprehends the management of changes
also.
- The type
of change management most of lightweight processes implement is a different
paradigm if compared to traditional change management and usually are nothing
more than keeping the scope under control (tracking, creating or removing
work items).
Regards,
Maciel
From: epf-dev-bounces@xxxxxxxxxxx
[mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ana Paula Valente Pereira
Sent: quarta-feira, 13 de agosto de 2008 14:09
To: Eclipse Process Framework Project Developers List
Subject: Re: [epf-dev] Renaming "Change Management"
practice to "Basic Change Management"
what about Flexible ? ... Flexible Change or Scope Management?
... contrasting with traditional change management that seems to be more
rigid ...
Ana
On Wed, Aug 13, 2008 at 5:20 PM, Bruce Macisaac <bmacisaa@xxxxxxxxxx>
wrote:
Hi Ken,
I think the point is that without the qualifier, it makes it hard to name
alternative change management practices.
In other words, if we have 3 change management practice alternatives, and
one is called change management, it's hard from the name to know what kind
of change management is being described
by the practice. Also, it may seem unfair for us to claim copyright
to "change management" - by adding some kind of qualifier, at
least we are only claiming our brand of change management.
Another suggestion from Per is "Informal Change Management".
Is that better than "Basic"?
Note that this practice, as it stands, just has one task, which is to submit
change requests, and otherwise changes are really being addressed as part
of
work item management done by the iterative development practice. It's
not a traditional formal change management approach with a CCB and unique
states for change requests.
Bruce MacIsaac
Manager - RUP/OpenUP Content
bmacisaa@xxxxxxxxxx
phone: (408)463-5140
I don't know I think you got it right the first time. Firstly, I
don't think its fair for any one group to claim copyright to the term Change
Management. Secondly the term "Basic" is almost pejorative and
somehow diminishes the importance of the practice (think about Basic Project
Management, Basic Architecture etc). Thirdly, I'm not sure we need
a qualifier, one would think the context would be sufficient if we put
"Basic" before one practice what does that mean about the other
practices.
My $0.03
On Tue, Aug 12, 2008 at 3:46 PM, Bruce Macisaac <bmacisaa@xxxxxxxxxx>
wrote:
Chris Sibbald and I would like to make this change to address concerns
raised by reviewers.
The basic concern is that they expected from the name that this would be
a formal change management practice, and it's not.
See bugzilla:
I plan to make this change tomorrow, so if there are any
concerns at all with this, please let me know as soon as possible.
Thanks,
Bruce MacIsaac
Manager - RUP/OpenUP Content
bmacisaa@xxxxxxxxxx
phone: (408)463-5140
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
Attachment:
discussion to rename change management.doc
Description: Binary data
