Integrations Change Management

The integrations change management process is an extension of the Business Technology Change Management process which is tailored to the SDLC of the integrations team.

The team develops integrations with two tools; Workato and Nestjs and the change management process currently differs between them.

Workato changes

Workato is a tool that helps you manage your integrations. It is a web application that allows you to manage integrations, environments, and deployments. All of this is done using a drag and drop interface which makes it an easy tool to quickly get started with, however it also makes change management more difficult. The current process for change management is this;

1. Follow the BT change management process but create the change issue within the Platypus project.
2. Add the appropriate change management label to the issue using the approval matrix. If the change is comprehensive, add the Business Owner Approval::Needs Approval label.
3. Receive approval from the business owners of any affected systems in the change and have them comment their approval and add the Business Owner Approval::Approved label to the issue.
4. Once the change is made in development, link the relevant recipes and changes in a comment on the issue and request peer approval from someone else on the integrations team. Have them comment with their approval and add the label Peer Approval::Approved to the issue.
5. After peer approval, move the code in test and request for manager approval by adding the comment BT Integration Manager::Needs Approval. Once reviewed and approved add the label BT Integration Manager::Approved.
6. Next, create an issue in Change Management project by using the change management issue template.
7. Once all the checklist items in change management issue are done, you’re ready to move the code in prod.

View page source - Edit this page - please contribute.