Understanding Change Control Management in Software Development

Change Control management is needed to prevent chaos when changes happen rapidly to the project. 

Change Control Management Workflow Chart

Key points of Change Control Management

  1. Changes are reviewed by Project Manager and Senior Developers/Testers. Project Manager is responsible for estimating impact of changes to Project Plan.
  2. If change has technical merits, side-effects, or it is estimated to break project plan, objectives of the change should be either weakened, or it should be rejected (if it does not concern critical requirements), or it should be billed at a separate price.
  3. Changes are sent to entire project team by email, and discussed at project team meeting.
  4. Changes are documented and stored in Version Control System for the sake of Configuration Management.


Post new comment

The content of this field is kept private and will not be shown publicly.