It is never fun to make changes, especially amidst a big project, but at times change is necessary. There might be personnel who are not working out, or the scope might be wrong or ill-defined, or perhaps the schedule needs to be overhauled; all of these things and others can cause changes on the project. There is always a chance that the change will be disruptive for the project and the project team, so changing anything on a project just for the sake of change is never a good idea. Leaders should consider the issue from every angle and solicit input from all concerned parties before they can even decide if a change is warranted. If change is indeed necessary for the project, then the following checklist will help ensure that all bases are covered as the project manager implements the change(s)...
Author: Brad Egeland