James,
It would seem to me that the issue is what is most important. If creativity
of the artistic variety is most important, then change management should
take at most second chair. What happens, however, in most situations that I
have seen, is that no change management in the early stages of a project
result in _no_ change management in the later phases. What appears to be
the best course is to put everything under version control from the outset
and have a "generalized" change management process during the early phases.
By generalized I mean that there is a small set of Change Requests (CR's)
that can be used for a wide variety of activities in the early phases. When
the later phases are reached, the CR's are more closely defined, become more
numerous, and hence assist in tracking and deconflicting changes.
My sense is that this is an issue where YMMV, but what I have tried to
describe should be capable of adaptation. Change Management should not
exist for the sake of Change Management, but as a tool to reach an ultimate
project goal.
Ted
---------------
Ted Jardine Sr. SCM Administrator
Aspen Technology, Inc. 19204 North Creek Parkway
425.492.2272 (office, voice mail) Bothell, WA 98011 USA
mailto:ted.jardine@aspentech.com Avocation:
http://www.aspentech.com Flight Instructor, Airplanes &
Instruments
"Keep the pointy end forward, the dirty side down."
-----Original Message-----
From: Couball, James [mailto:James.Couball@cotelligent.com
Sent: Monday, September 25, 2000 10:13 AM
To: 'cmtalk@cmtoday.com'; 'cciug@rational.com'
Subject: [cciug] At what point in a project should formal change
management begin?
Hello,
I work for a company that develops software for others. There seems to be
some issue here about when we should start using a change management process
on projects. We follow Rational Unified Process (roughly). One manager
here has argued that a project should not use change management until the
beginning of the construction phase (most analysis and design finished).
Prior to more formal change control, all artifacts would be in our version
control repository. The idea is that change should be encouraged (and
loosely tracked in the version control system) in the beginning phases of a
project and controlled when those changes start having an adverse impact to
budget and schedule.
I was wondering what others had to say about this.
Sincerely,
James Couball
Cotelligent
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:26:48 EDT