Change Management Process (Notional)

This is a notional Change Management process that can be adapted to fit specific needs. It is not intended to be all-encompassing or fit every application.

Diagram

flowchart TB
    Create[Create a Formal Request for Change]
    Analyse[Analyse the Request for Change]
    Develop[Develop a Change Implementation Strategy]
    Approve[Approval of the Change]
    Plan[Plan, Develop and Schedule the Change]
    Implement[Implement and Test the Change]
    Review[Review Change Effectiveness]
    Report[Report to Management]

    Create --> Analyse
    Analyse --> Develop
    Develop --> Approve
    Approve --> Plan
    Plan --> Implement
    Implement --> Review
    Review --> Report

Process

Create a Formal Request for Change

Stakeholder(s) create a formal Request for Change in the Change Management system. This request may be technical or non-technical in nature.

For example: Install a breakfast bar in the kitchen area

Analyse the Request for Change

Stakeholders and Analysts analyse the Request for Requirements, Feasibility, Impact, Security and Timeline.

For example: The breakfast bar will need to seat 4 people and will open up the kitchen area. This will improve fire safety by enabling quicker egress to fire exits through the kitchen area. Staff should be discouraged from working from the breakfast bar as laptop screens may be visible from the street, representing an avenue for data leaks. The bar should be installed before June.

Develop an Implementation Strategy

Stakeholders and Analysts develop a strategy for the implementation of the change. This should include how success of the change will be measured.

For example: The breakfast bar will sit perpendicular to the main window without blocking the doorway. We can mitigate the data leak security risk by also installing one-way film to the window. This should be completed before June and but needs to wait until completion of electrical works in the room.

Approval of the Change

Stakeholders and Change Advisory Board (where neccessary) approve the change.

Plan, Develop & Schedule the Change

Analysts and Engineers further plan, develop, and then schedule the change.

For example: The breakfast bar is built to specification and prepared for delivery. Then the installation team are scheduled to remove the old table and install the breakfast bar

Implement and Test the Change

Engineers implement and test the change against requiremnts. Further tests may be conducted by Analysts, Requestors and other Stakeholders.

Review Change for Effectiveness

Stakeholders and Analysts review the change and ensure it meets Stakeholder requirements

Report to Management

Stakeholders and/or Analysts report the Change Request result to broader stakehoders and management.