Change request process design

Your company has one or more processes for tracking and managing change. For example, your company might have a process for performing IT tasks, such as installing a phone line or moving a workstation, and a different process for modifying software products. Your company might even have a unique process to meet the change management needs of each organization.

The change request process (CR process) contains the general information and models, or lifecycles, for each of these processes.

Each lifecycle in a CR process defines the properties and behaviors of changes (or change requests) from submission to completion. Each lifecycle also includes the information tracked and managed by a change request (CR) and how, when, and by whom a CR can be updated.

The more complete and accurate your CR process is, the more effective your CR tracking and management will be.

Before using the CR process editing interface to create your own CR process, follow these steps:

1. Consider using a delivered CR processes.
2. Define the attributes to track.
3. Decide the user privileges.
4. Determine states and attributes.
5. Define transitions and attributes.
6. Consider how these features work together to create one or more lifecycles. See Next steps.