IT Change Management Policy



Similar documents
The Newcastle upon Tyne Hospitals NHS Foundation Trust. IT Change Management Policy and Process

Subject: Information Technology Configuration Management Manual

The ITIL v.3. Foundation Examination

Service Support. Change

Service Transition. ITIL is a registered trade mark of AXELOS Limited.. The Swirl logo is a trade mark of AXELOS Limited.. 1

UMHLABUYALINGANA MUNICIPALITY IT CHANGE MANAGEMENT POLICY

CHG-11-G-001 Does the tool use ITIL 2011 Edition process terms and align to ITIL 2011 N/A. Edition workflows and process integrations?

ITIL Introducing service transition

Roles within ITIL V3. Contents

SFJ EFSM14 Manage the performance of teams and individuals to achieve objectives

Page 1 of 8. Any change, which meets the following criteria, will be managed using IM/IT Change Management Process.

1 What does the 'Service V model' represent? a) A strategy for the successful completion of all service management projects

Issue 1.0. UoG/ILS/IS 001. Information Security and Assurance Policy. Information Security and Compliance Manager

ISO :2005 Requirements Summary

ITIL 2011 Lifecycle Roles and Responsibilities UXC Consulting

ITIL Version 3.0 (V.3) Service Transition Guidelines By Braun Tacon

ITIL Example change management procedure

Corporate ICT Change Management

Free ITIL v.3. Foundation. Exam Sample Paper 1. You have 1 hour to complete all 40 Questions. You must get 26 or more correct to pass

Information security policy

Data Governance Policy. Staff Only Students Only Staff and Students. Vice-Chancellor

NHS Business Services Authority Information Security Policy

University of Waikato Change Management Process

ITIL Example emergency change management procedure

Information Security Policy. Document ID: 3809 Version: 1.0 Owner: Chief Security Officer, Security Services

BMC Software Consulting Services Fermilab Computing Division Incident Management Policy

ITIL applied to Network Operations

POLICY CONTRACT MANAGEMENT POLICY POLICY STATEMENT

hi Information Technologies Change Management Standard

Institutional Data Governance Policy

Which statement about Emergency Change Advisory Board (ECAB) is CORRECT?

ITIL V3 Foundation Certification - Sample Exam 1

XXX000YY Certificate IV in Government Security

Information Security: Business Assurance Guidelines

1 Why should monitoring and measuring be used when trying to improve services?

Data Governance Policy. Version October 2015

Foundation. Summary. ITIL and Services. Services - Delivering value to customers in the form of goods and services - End-to-end Service

3. Ensure the management of information is compliant with legislative requirements to maximise the benefits and minimise risks;

Victorian Government Information and Communication Technology (ICT) Governance

Release Management for BMC Remedy IT Service Management version 7.0 WHITE PAPER

Overview TECHIS Carry out risk assessment and management activities

White Paper Case Study: How Collaboration Platforms Support the ITIL Best Practices Standard

Wright State University Information Security

Rowan University Data Governance Policy

Master Data Management Architecture

ICAICT704A Direct ICT in a supply chain

OH&S MANAGEMENT SYSTEM CHECKLIST - AS 4801:2001 (STATUS A = Acceptable; N = Not Acceptable; N/A = Not Applicable)

The ITIL v.3 Foundation Examination

INFORMATION GOVERNANCE AND SECURITY 1 POLICY DRAFTED BY: INFORMATION GOVERNANCE LEAD 2 ACCOUNTABLE DIRECTOR: SENIOR INFORMATION RISK OWNER

University of Liverpool

PHASE 9: OPERATIONS AND MAINTENANCE PHASE

ITIL & PROCESSES. Basic Training

NOTTINGHAMSHIRE OFFICE OF THE POLICE AND CRIME JOB DESCRIPTION. Project Manager ECINS Development and Implementation 1 year project

Records Management Security of University Records Procedures

BUSINESS CONTINUITY MANAGEMENT POLICY

Location of the job: CFO Revenue Assurance

INS Problem Management Manual

WHITE PAPER IT SERVICE MANAGEMENT IT SERVICE DESIGN 101

The PNC Financial Services Group, Inc. Business Continuity Program

MODULE CURRICULUM DOCUMENT

information Records Management Checklist business people security preservation accountability Foreword Introduction Purpose of the checklist

The ITIL Foundation Examination

ITIL Introduction and Overview & ITIL Process Map

POSITION PROFILE Support Officer, ICT. Position Summary. Position Statement. Corporate Vision. Constructive Culture ICT.

The PNC Financial Services Group, Inc. Business Continuity Program

Head of Information & Communications Technology Responsible work team: ICT Security. Key point summary... 2

Records Management Self-Evaluation Guide

Scotland s Commissioner for Children and Young People Records Management Policy

ITSM. Maturity Assessment

Third Party Security Requirements Policy

Service Support Kasse Initiatives, LLC. ITIL Configuration Management - 1. version 2.0

Ref. Ares(2014) /05/2014. l(5)vodafone.com>

The Value of ITIL to IT Audit

Information Governance Management Framework

BCS Specialist Certificate in Change Management Syllabus

LEEDS BECKETT UNIVERSITY. Information Security Policy. 1.0 Introduction

Risk Management Policy

Risk Management & Business Continuity Manual

Information Strategy

The ITIL v.3. Foundation Examination

EXIN.Passguide.EX0-001.v by.SAM.424q. Exam Code: EX Exam Name: ITIL Foundation (syllabus 2011) Exam

CONSTRUCTION HEALTH AND SAFETY, AND INJURY PREVENTION Research and develop accident and incident investigation procedures on construction sites

CITY UNIVERSITY OF HONG KONG Change Management Standard

Risk Management Policy

Ulster University Standard Cover Sheet

How To Manage A Service Transition

INFORMATION MANAGEMENT STRATEGIC FRAMEWORK GENERAL NAT OVERVIEW

Queensland recordkeeping metadata standard and guideline

CMS Policy for Configuration Management

Transcription:

Date of effect 24 November 2011 Approval Vice Chancellor Documents replaced by this N/A policy Procedures and/or guidelines supporting this policy A. Introduction Purpose IT Change Management Policy 1. The purpose of this policy is to communicate the University s requirement that changes to IT (information, application and infrastructure) architecture must be managed efficiently and effectively, using standardised methods and procedures. Definition 2. Change management is the process responsible for controlling the lifecycle of all changes. The primary objective of change management is to enable beneficial changes to be made with minimum disruption to IT Services (ITIL v3) and end users. Goals 3. The goals of the Change Management process are to: Ensure that standardised methods and procedures are used for the efficient and prompt handling of all Changes, in order to minimise the impact of Change-related Incidents upon service quality, and consequently improve the day-to-day operations of the organisation. The Change Management process is especially important in ensuring only authorised change is made to the production environment. Respond to the University s changing business requirements while maximising value and reducing incidents, disruption and re-work. Respond to the requests for change that will align the IT services with the University s business needs. Scope 4. This policy covers the release of any new services or a service change to the University s IT architecture. 5. Changes include additions, deletions and modifications to any IT architecture resource. Referenced from Best Practice for Service Support ITIL The Key to Managing IT Services Page 1

6. The University s IT architecture includes, but is not limited to, hardware, software, operating systems, data and voice network and applications. Legislation 7. This policy is governed by the University of Canberra (University Facilities) Amendment Statute 2006 and the University Facilities (Information and Communication Technology Network) Rules 2006. B. Principles 8. IT Service and infrastructure changes shall have clearly defined and documented scope. 9. All requests for change shall be recorded and classified, e.g., standard, normal, enhancements and emergency/fast track standard. Requests for changes shall be assessed for their risk, impact and business benefit. 10. The change management process shall include the manner in which the change shall be reversed or remedied if unsuccessful. 11. Changes shall be approved and then checked, and shall be implemented in a controlled manner. 12. Details of changes will be communicated to all stakeholders on a regular basis. 13. There shall be a procedure to handle the authorisation and implementation of emergency changes. 14. The scheduled implementation dates of changes shall be used as the basis for change and release scheduling. A schedule that contains details of all the changes approved for implementation and their proposed implementation dates shall be maintained and communicated to relevant parties. 15. There shall be clear accountabilities for the authorisation and implementation of all changes. 16. There shall be an appropriate administrative separation of authorisation and implementation roles for each change, relating to the risk associated with the change. 17. Change Advisory Board (CAB) meetings shall be held regularly with attendees from ITM and relevant business units. Page 2

C. Relevant information Context 18. This policy fits within the University s IT Infrastructure Library (ITIL) service management framework (Service Transition Responsibilities 19. Responsibilities for implementing this policy are set out below:. Policy owner: Head ITM Policy custodian: Head ITM, Director Customer Services Group and Director Infrastructure and Information Management Policy contact: Change and Release Manager 20. The University of Canberra Change Management Roles and Responsibilities document provides full details of roles and responsibilities in relation to Change Management. 21. Suppliers of goods and services pertaining to the University s IT Architecture have the responsibility for following the prescribed ITM change management process and procedures. 22. Suppliers of externally hosted services are responsible and accountable for informing the University of its role and responsibilities in the suppliers change management process. 23. Where an externally hosted service is hybrid (contains service components owned/managed by the University) the supplier s and the University s ITM change management processes will work collaboratively during service transition. 24. All staff and end-users of the University s the IT architecture including all corporate IT applications have a responsibility for Change Management: End-User/Functional User has responsibility for submitting a change request, including appropriate authorisation and participation in the testing. Business System Owner has the responsibility for ensuring that the change process is followed for all business systems. ITM Staff Technical Role has responsibility for following the prescribed change management processes and procedures. Change Advisory Board has responsibility for advising the Change and Release Manager in the assessment, prioritisation and scheduling of changes. Change Manager - has responsibility for approving changes to the IT architecture. Emergency CAB has responsibility for reviewing/approving high urgency, high impact emergency changes (required in less than 24 hours). ITM Management has overall governance responsibility for overseeing the change management policy and processes. This includes, but is not limited to, policy dissemination, process enforcement, grievance and final approval for those changes requiring escalation by the CAB. Page 3

Audit and Evaluation 25. The Change Management process will be reviewed and assessed on an annual basis by Head ITM for compliance with the policy. Other related documents 26. Documents related to this policy are: Archives Act 1983 Freedom of Information Act 1982 Privacy Act 1988 Evidence Act 1995 Electronic Transaction Act 1999 Crimes Act 1914 Telecommunications (Interception and Access) Act 1979 Enterprise Architecture Principles Policy Data Management Strategy Business Intelligence Strategy Enterprise Content Management Strategy Glossary 27. The following definitions are relevant to this policy: Term Change Change Advisory Board (CAB) Change Manager Corporate IT Application Emergency Change Advisory Board (ECAB) ITIL Release Suppliers Definition A Change is defined as any addition, deletion and/or modification to an IT resource and may be characterised as permanent, transitory or remedial. A dynamically formed group of functional experts, who assist in assessing, prioritising and scheduling changes. Authorises and documents changes to the IT infrastructure and components in order to minimise disruption on operational services. All applications that support the business of the University. A smaller subset of CAB (including a Director of ITM) who are responsible for reviewing/approving high urgency, high impact emergency changes. Information Technology Infrastructure Library provides a best practice framework for the delivery of managed IT services. ITIL definition: A collection of hardware, software, documentation, processes or other components required to implement one or more approved Changes to IT Services. Third parties responsible for the supply of services and/or goods for the delivery of IT services. Page 4

Information for Policy Database [The following table is not part of the policy. It is to be sent as a separate document to the UC Policy Database administrator.] Policy number Policy status New Review date 31 December 2015 Central Registry file no. 2010/4244 Relevant UC Statute(s) and Rule(s) University of Canberra (University Facilities) Amendment Statute 2006 University Facilities (Information and Communication Technology Network) Rules 2006. Other relevant legislation Archives Act 1983 Freedom of Information Act 1982 Privacy Act 1988 Evidence Act 1995 Electronic Transaction Act 1999 Crimes Act 1914 Telecommunications (Interception and Access) Act 1979 Policy database grouping Accessibility Custodian Contact position Keywords Public access IT, Information Technology, change, change management, IT architecture Page 5