Best Practices for Software Projects: Change Control

Member Submitted

When developing and enhancing software, a well-laid plan has a documented set of features, detailed designs, and estimates that allow the project manager to quickly determine if the project is on track to completion. As development proceeds, it is not uncommon for business or market conditions to change, thereby changing the needs of a software project that is currently in development.

Change control is the process of managing changes as to ensure that decisions are not made hastily and that the decision to add an additional feature is in the best interest of the project. If change control is missing from a project, new features will be introduced at random, jeopardizing the delivery date and quality of the software being developed.

To manage change, it is best to have a Change Control Board. The Change Control Board normally consists of the project manager, client manager, development (programming) manager, quality assurance manager, user documentation manager.

About the author

Steve Miller's picture Steve Miller

Steve Miller is the Vice President of ALM Solutions for AutomatedQA. With over 25 years of experience, Steve has extensive knowledge in project management, software architecture and test design. Steve publishes a monthly newsletter for companies that design and develop software. Be sure to check out our other newsletters.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!