Formal Change-Control Process Helps Keep Complex Projects on Track
With almost any complex information technology project, there are bound to be scope changes along
the way. Often, the difference between a successful project and one that gets bogged down by “project
scope creep” is the way those scope changes are managed.
As part of the project analysis and planning phase before work begins, it’s important for system
integrators and custom programmers to establish a process for requesting and managing project
changes. This change-control process would apply to any work products related to the project, including
existing software, requirements specifications for new projects, project procedures and processes, or
even user or technical documentation.