Change Management

Change Management

An ITIL change from request to review: the change manager assesses it, significant changes go to the CAB, then build, deploy, and close.

Use the process template as it is or adjust and extend it to your needs.

The change manager reviews and assesses the requested change. A gateway sorts the changes by risk. A significant change goes to the change advisory board (CAB), which assesses and authorizes it. All other changes are authorized by the change manager and go straight on.

If the CAB rejects a change, the change manager informs the requester. An authorized change is built and tested, deployed, and then reviewed and closed by the change manager.

The template treats a change as significant when its process instance has the label significant-change. The decision is the status of the approval work item: when it is resolved with the status Rejected, the process takes the rejection path. The workflow of the work type needs this status. Without it, the default path is taken.

Read more in The ITIL Change Management Process, Step by Step.

Learn More

Kickstart your Flower BPMN Workflow

Process managementJira Workflow vs. Business Process Management (BPM)The difference between a Jira workflow, a business process, and a project, and how Flower turns Jira into a BPM system.11 min read

Process managementAgile Business Process Management (Agile BPM) with JiraHow agile principles and business process management fit together, how continuous improvement works with PDCA, and how Flower supports it in Jira.10 min read

BPMNThe Ultimate Guide to BPMN in JiraBPMN in Jira in one read. What BPMN is, the elements you need, how a model becomes work in Jira with Flower, and where the full BPMN reference continues.5 min read