Results 1 to 2 of 2

Thread: Configuration management and change management

  1. #1
    Join Date
    Sep 2006

    Thumbs up Configuration management and change management

    Hello friends!

    Will anyone explain the difference between Configuration management and change management?

    Brijesh Jain
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  2. #2
    Junior Member
    Join Date
    Dec 2007

    Re: Configuration management and change management

    # CM is software artifact management
    # CM is management of artifacts and the processes that produce them
    # CM is the big picture encompassing Product Management, Project Management, Change Management, and perhaps Customer Management, depending on what your CM tool can manage.
    Configuration Management to manage requirements, to manage source code, test cases and documentation.


    # Product Management - what changes go into each release of the product.
    # Project Management - controlling the flow of changes to maximize chances of successful delivery of each release, on time and within budget
    # Change Control - ensuring that each change follows packaging, traceability and checkout guidelines.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.