Change Management is one of the most crucial part of any implemented system, especially when integrated with an information system. All successful systems use some form of change management. Change management, when handled correctly, addresses scope and requirements analysis; when a project is created, it has an intended purpose. In the beginning stages of any project the scope is outlined, the requirements are outlined, and then it begins to take shape to become something tangible. It is at this point in a project that maintaining a specific course is crucial. If the project has no deadline, it will most likely never be completed. If the project has no defined scope, the project will never stop growing, and therefore never reach a termination stage. This is where change management becomes the difference between a project's life and death.
             Change management is defined as a "...process of controlling changes to the infrastructure or any aspect of services, in a controlled manner, enabling approved changes with minimum disruption" (OGC). In other words, change management is a way to control what changes are actually made to the project before its initial release, or additions that are added to any upgrade, or patch. This is true in not only the software world, but any other medium where changes need to be made to a project. One example is building a house. There are certain stages in the building process where changes made to the original plans will completely rework the building schedule. In many cases, adding new features to a housing project will not only set the build date behind, but cost the buyer much more of a financial investment.
             When applied to a software creation project, change management can be a nightmare for project managers. However, if the individual maintains rigid change management processes, he or she will be able to release the software or hardware required at the intended time or at the very minimum, alert th...