Page 278 - ITIL® Foundation 3.15

Change Proposals
Kudzu was originally introduced into the United States as an ornamental vine at the Philadelphia Centennial Exposition of 1876.
This introduction was made without a clear understanding of the impact upon the natural environment...As a result, the entire southeastern U.S. now has to continually fight the spread of this plant to prevent it taking over entire forest areas and killing all of the other vegetation.
Major changes, or those that involve significant cost, risk or organizational impact will usually be initiated through the service portfolio management process. Service Portfolio management charters new services allowing development/design to commence. Prior to that happening, a change proposal is sent to change management for Review Activitiesing the potential impact that this new service could have on other services, shared resources, or planned changes already on the change schedule. This submission prior to chartering allows potential conflicts to be identified early. Change management authorizing the change proposal does not authorize the change, but simply identifies that conflict analysis has been done, and allows the service to be chartered. Service Design activity can then proceed. After a service has been chartered, normal RFC procedures will be used for approval of specific changes.
The change proposal should include:
• A high-level description of the new, changed or retired service, including business outcomes to be supported, and utility and warranty to be provided
• A full business case including risks, issues and alternatives, as well as budget and financial expectations
• An outline schedule for design and implementation of the change. Copyright © 2018. Knowledge ToolWorks. All Rights Reserved.