All projects must have some sort of change-control process, whether it' s chiefly informal or highly polished and regulated. You need to have a way of accepting change requests, figuring out what kind of change is being asked for, and then responding accordingly.
This section talks about what kinds of elements you might track when setting up a change-control process. You could utilize a database of some kind, an intranet site, or even a simple spreadsheet for tracking your change requests, but you need to have a method for this.
Note that in most cases, you are not the one who approves or denies changes. In larger projects, a full change-control committee will be formed to oversee changes to the project. You might be a member of that committee, but it's not a committee of one. Smaller projects should require that changes be at least passed through the sponsor and at least one stakeholder. In the case of indecision about whether to implement a change, the PM can be the tie-breaker.
Note that the elements described in the preceding section are certainly still pertinent. You still have to go through the process of determining the impact of the change to the scope of the project, notifying stakeholders, etc.
Following are some items that you might want to consider adding when setting up a change-control system. These items speak to specific elements of any project that may be subject to a change.
Was this article helpful?