Completing a change request in Concurrent Change Management

This video explains how to create and complete a change request in 1:1 Operations Manager with Concurrent Change Management.

U+ Bank plans to launch a premium rewards credit card targeting high-value customers. They are planning to launch this offer for their upcoming first quarter release. The bank has enabled CCM to enable the teams to work in parallel.

To implement the current business requirement, log in as a Business User to 1:1 Operations Manager.  Then you must create a change request to introduce the new offer. First, enter the name and completion date of the change request. On the change request form, there is the option to choose a release vehicle. According to your release plan, you can either tag the change request to a release vehicle while creating the change request, or you can add the change request at the Plan stage of the release vehicle. This flexible relationship enables business users to move change requests between releases as needed.

The list shows only release vehicles that are in the Plan stage with an In-progress status, and the system filters the release vehicles based on the completion date that you enter. In the current scenario, the offer is planned for first quarter. Provide a description and create the change request.

As in the traditional change management process, you must complete the Define action details tasks. If you are using any artifacts from a change request that has not been deployed, the system detects them and adds as a dependent change request to the current change request. Finally, you finish the Plan stage of the change request.

The next step is to prioritize the change request. As a Team Lead, you do this by opening the change request and ranking it.

As an NBA Specialist, complete the action building tasks. On completion, the status of the change request turns to Deployment-Ready.

Notice that the workflow no longer includes the Generate Artifacts and Validate Artifacts steps, as in traditional change management. This is because of Just-in-Time Rule generation, in which the rules are not generated immediately. Instead, the system generates the rules only when needed.

Now, as a Team Lead, complete the change request. The status of the change request turns to Resolved-Completed. In Concurrent Change Management, as a Team Lead, you can reopen the change request if you need to make further changes, even after completion.

You have reached the end of this video. You have learned:

• How to complete a change request in Concurrent Change Management.
• What are the differences in the lifecycle of a change request in Concurrent Change Management.