Change Request
Change Request
Change Request
Information & Media Technology
Change Request ID: Date Submitted: Request Title: IMT Lead: Requestor: Department: Primary Stakeholder: Requested Install Date: Change Goal: Upgrade Bug Fix Maintenance Explanation of Proposed Change: Change Process: Normal Risk:
Ext: Ext: Ext: Description of Work Problem Fix Performance Improvement Other
Business Drivers:
System Drivers:
Business Impact:
System Impact:
Primary Deliverables (Scope): 1. Other Stakeholders: Client Resources Needed: provide name & extension Cost Information: Orig Budget: Account #: Aprvd Budget: APPROVAL SECTION Actual Cost: Ext: Date:
Name: Requestors Supervisor Director IMT Cabinet (as needed) Other (as needed) Comments:
Page 1 of 3
revision 1.f 7/1/2011
CHANGE REQUEST
Risk: 1-High
2-Medium 3-Low
Maintenance
Problem Fix
DESCRIPTION: Tracking number assigned by IMT The procedure that is followed to implement your change (IMT assessment of nature of change) Production Service(s) is available for use. Business need may be implemented within standard lead times. A change required to fix a problem that is impacting the production environment or to satisfy an immediate business requirement with no advance warning - severe risk/impact to university is at hand. IMT assessment of potential impact of requested change: Involves several, or critical, systems. Major impact if change fails. Will disrupt hardware, software, data if change unsuccessful. Very difficult or impossible to recover. {7 day Lead Time for Implementation Notification to customer/stakeholders is required. Involves several systems. May disrupt hardware, software, data if change unsuccessful. Recovery is difficult or lengthy. {5 day Lead Time for Implementation Notification to customer/stakeholders is required. Involves non-critical systems. Small impact on failure. Recovery is simple or not necessary. {3 day Lead Time for Implementation Notification to customer/stakeholders is required Date Change Request submitted to the Project Management Office (PMO) Meaningful request identifier to associate with the ID Name of the IMT staff member who is overseeing the change and is the point of contact for approvers/resolvers/SSD for further information. The IMT Lead is responsible for all communications with the Requestor. IMT Leads telephone extension Name of the request originator Requestors telephone extension Requesting Department Person or group whose needs and requirements drive the change; receives the final output(s) that the change produces; provides change requirements and funding. (May be the requesting department) Primary Stakeholders telephone number (if person) Requestors desired target date for implementing the change Type of Change being Requested: To replace (a software program) with a more recently released, enhanced version; To replace (a hardware device) with one that provides better performance. A change to a program or system intended to permanently cure a bug (defect/difficulty). Often a fix for one bug inadvertantly introduces new bugs, hence the need for careful forethought and testing. The modification of a hardware/software product, after delivery, to correct faults, to improve performance or other attributes, or to adapt the product to a changed environment. Identity and resolution of a hardware/software deviation or departure from the normal or common order, form, or rule - one that is peculiar, irregular, abnormal, or difficult to classify. The adaptation of hardware/software to increase the probability of
Page 2 of 3
revision 1.f 7/1/2011
CHANGE REQUEST
Explanation of Proposed Change Business Drivers System Drivers Business Impact System Impact Benefit Statement
Primary Deliverables (Scope) Other Stakeholders Client Resources Needed Account# Orig Budget Aprvd Budget Actual Cost
achieving desired outcomes and to better meet the needs of IMT customers. A brief description of the desired change; what it does and does not include. Business factors that contribute to the need for the requested change Technology factors that contribute to the need for the requested change Business operations/departments which may be affected by the requested change. Hardware/Software which may be affected by the requested change Tangible/Intangible advantages of implementing change (cost savings/avoidance; performance/process improvement; satisfy strategic goal; etc.) What the Requestor expects to be delivered as a result of the implementation of the change. Anyone who may be impacted/ have a vested interest in the success of the change. Client staff needed/available to help promote the successful implementation of the change. The financial account (budget) to which any/all charges will be applied Initial budget dollars available/approved to implement change Approved budget dollars available to implement change Actual cost to implement change
Page 3 of 3
revision 1.f 7/1/2011