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