Scribd Logo
Upload

Welcome to Scribd!

  • Change Management Process

    Uploaded by

    HubVroon
    840 views1 page
    The document outlines a change management process flow with the following key steps: 1. Changes are identified and logged before being assigned an initial priority and category. Emergency changes bypass some steps. 2. The change authorization board reviews and authorizes standard and significant changes. Minor changes are approved by managers. 3. Authorized changes are scheduled, built, tested, and implemented if tests are successful. Emergency changes are implemented after notification.

    Original Description:

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document outlines a change management process flow with the following key steps: 1. Changes are identified and logged before being assigned an initial priority and category. Emergency changes bypass some steps. 2. The change authorization board reviews and authorizes standard and significant changes. Minor changes are approved by managers. 3. Authorized changes are scheduled, built, tested, and implemented if tests are successful. Emergency changes are implemented after notification.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    840 views1 page

    Change Management Process

    Uploaded by

    HubVroon
    The document outlines a change management process flow with the following key steps: 1. Changes are identified and logged before being assigned an initial priority and category. Emergency changes bypass some steps. 2. The change authorization board reviews and authorizes standard and significant changes. Minor changes are approved by managers. 3. Authorized changes are scheduled, built, tested, and implemented if tests are successful. Emergency changes are implemented after notification.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    Change Management Process Flow

    ITSM Academy 4/10/2006

    MAJOR
    Emergency
    Circulates RFC
    Change
    to CAB
    Assign initial priority
    Identify
    Change (emergency, high, Emergency
    and Log
    Management medium, low), urgency Change?
    Change Determine SIGNIFICANT
    and preliminary impact
    Change Circulates RFC
    Category to CAB
    YES
    Conduct
    STANDARD impact
    Emergency Circulates RFC analysis and
    Change to CAB validate
    category
    (financial,
    MINOR business,
    Change technical
    Manager or impact)
    delegate
    decides

    Update and close


    Obtain Change Change RFC and Release not
    NO
    Authorization Authorized? communicate accepted
    decision

    Release
    YES Accepted

    Schedule change Build and Test


    and communicate Engage Release Change Test Implement Emergency
    NO YES
    to all affected Management? Successful? Change Change
    parties (Standard/Minor)

    Notify
    YES Configuration
    NO
    Managers
    Change
    All major and YES and
    Successful?
    some significant communicate
    change handled by to all affected
    Release NO parties
    Management
    Enact
    Backout
    Plan Update RFC
    YES
    Log
    Release
    Management

    Backout
    Successful? Conduct Post-
    Implementation
    Review
    NO

    Incident
    Configuration
    Management
    Management

    You might also like