What is change control and why is it necessary?
Contents In any software project there are changes. Changes can be due to many factors: varying markets, different technology, shift in budget, government regulations, new and modified user requirements, plus many more. One of the keys in this area of the project lifecycle is to manage the requested changes and don t let scope expansion take over the project. A common approach to managing this aspect of a project is to define a change control process. This process consists of a change board and a set of procedures to review requested modifications and add or reject the proposed change to the project schedule. A change board consists of a number of people from the management, user and development groups associated with the project. The number should be limited to keep the group small enough to get the work done. The mission of a change board is to be the clearing house for changes to the project. They review requests made to the application design, determine if the change replaces an ex
