Home 
Resources CM Yellow Pages Articles and Whitepapers CM Crossroads Articles Back to CM Basics: Change Control
Resources CM Yellow Pages Articles and Whitepapers CM Crossroads Articles Back to CM Basics: Change Control
Back to CM Basics: Change Control
Address
Dick Carlson dcarlson@iascar.us
Dick Carlson - Aug 2003
One of the first things asked by those “threatened” by the notion of controlling changes is, “Why do things have to change?”, and “What should be controlled?” As we all should realize, we don’t live in an ideal world, so when a configuration item or component is approved, there’s no need to change. However, we live in the real world where change is dynamic and inevitable. Requirements change, boundaries change, errors are found in documents and specifications or are just plain wrong, designs change, customers change their minds – in general, stuff happens! Get another prospective and point-of-view, just to keep it fresh
One of the first things asked by those “threatened” by the notion of controlling changes is, “Why do things have to change?”, and “What should be controlled?” As we all should realize, we don’t live in an ideal world, so when a configuration item or component is approved, there’s no need to change. However, we live in the real world where change is dynamic and inevitable. Requirements change, boundaries change, errors are found in documents and specifications or are just plain wrong, designs change, customers change their minds – in general, stuff happens! Get another prospective and point-of-view, just to keep it fresh
Reviews (0)
Be the first to review this listing!