RETURN TO MAIN Implementing a Change Control Procedure Within Your Firm Presented by: TOBI M. HALL SYSTEMS OPERATIONS MANAGER SHOOK, HARDY & BACON L.L.P.

Slides:



Advertisements
Similar presentations
Reliability Center Data Request Task Force Report WECC Board Meeting April 2009.
Advertisements

SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Software Quality Assurance Plan
1 Program Management Practice Program Management Portal: Contract Management and the Client © 2011, 2013 IBM Corporation.
MIGRATION MIGR-09. How to Run Your Next Implementation... Don't Let It Run You! Patricia Johnson Senior Systems Consultant Strategic Systems Group, Inc.
Jack Schmidt and Mark Kaletka Fermilab NLIT 2009.
Prepared by the Virginia Department of Criminal Justice Services PTCC …the future of case management DCJS presents:
The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
Test Execution and Defect management. 2 Module Objectives Introduction to Test Execution Checklist of Test Execution Defect management Defect Classification.
Project management Topic 3 Directing a project. Overview of processes Authorise Initiation Authorisation for Initiation Stage Authorise the Project Contract.
ITIL: Service Transition
Project Cost Management Estimation Budget Cost Control
I-AM Request Presented by Carol Williams Manager, Security and Accounts Management, Information Technologies Wednesday, May 13, 2009.
Managing the Information Technology Resource Jerry N. Luftman
Best Practices – Overview
Strategic Information Initiatives Week 4 Project Planning Frank Coker, MBA, CMC President Information Systems Management, Inc. (a consulting firm – since.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
ECM Project Roles and Responsibilities
Remedyforce Value Enablement Kit – Change Management
Program Management Practice Program Management Portal: Contract Management and the Client © 2011, 2015 IBM Corporation 1.
Remedy, a BMC Software company Change Management Maximize Speed and Minimize Risk in the Change Process.
Problem Management Overview
ITIL: Why Your IT Organization Should Care Service Support
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Change Advisory Board COIN v1.ppt Change Advisory Board ITIL COIN June 20, 2007.
Release & Deployment ITIL Version 3
Fundamental of Software Project Management
Security Guide for Interconnecting Information Technology Systems
Module 3 Develop the Plan Planning for Emergencies – For Small Business –
Information Services, Griffith University Problem Management Implementation Service Desk Project Phase 2 Project
Technology Services Employee Help Desk Overview. I need you to stop by my office on next Thursday the 20 th and load Adobe Pro 2014 on my laptop. There.
Name Class.  Review of Implementation Process  Identify Critical Success Factors  Define Change Management (big picture)  Define Role of Corporate.
BUSINESS PLUG-IN B15 Project Management.
SERVICE MANAGER 9.2 CHANGE PRESENTATION JUNE 2011.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Event Management & ITIL V3
Software Project Management
SacProNet An Overview of Project Management Techniques.
2006 CMBG Conference Sam Melton Supervisor, Configuration Management Brunswick Nuclear Plant Progress Energy June 11-14, 2006 Richmond, VA CM04 Facility.
Service Management for CERN Change Management Acceptance Meeting Geneva, Jochen Beuttel.
1 Local Readiness Team Lead Kick-Off Meeting May 16, 2007.
Executive Summary Target Deployment – January 4, 2005 Actual Deployment – December 22, 2004.
TESTING SERVICES Overview Testing Accommodations is a collaborative process between the DRC student, the Professor, and DRC. COMMUNICATION IS ESSENTIAL.
JPAS Release Implementation date: 31 March 2007 Developed by the JPAS Industry Team 30 March 2007.
Banner Leave Report, Request, and Approval BAS Forum April 11, 2007.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Access to OASIS Evelyn Pidgeon OASIS Security Administrator.
Change Request TUNE IT! Hi! My name is Ed Dubrawski, PMP and a member of the Program Management Center of Excellence Advisory Council. The purpose of.
State of Georgia Release Management Training
1 ERCOT Retail Release Overview. 2 How Are Changes Managed? Retail Testing Business Teams Development Teams Release Management Management of: Migration.
1 TenStep Project Management Process ™ PM00.5 PM00.5 Project Management Preparation for Success * Manage Scope *
Staff Assessment Technology Services Department Palmyra Area School District.
The Planning Phase Recognize the problem MIS steering committee 7. ManagerSystems analyst Define the problem Set system objectives Identify system constraints.
® MTAC Workgroup #121 Improving the ACS TM / OneCode ACS ® System MTAC Update – February 19, 2009 Postal Workgroup Leader:Industry Workgroup Leader: Lisa.
STRATEGY IMPLEMENTATION Chapter 7. FUNCTIONAL STRATEGIES These are made up of day to day decisions made at the operating level of the firm, often performed.
Kick Off Call Account Name Date. © 2013 Citrix | Confidential – Do Not Distribute Agenda Team Introductions Discovery Fact Sheet/Apps & Features Implementation.
Important acronyms AO = authorizing official ISO = information system owner CA = certification agent.
ITIL Project Change Management Workshop 7 February 2007
USDA 2016 Financial Management Training Transforming Shared Services Change Management Presented by Ron Gros.
Powerpoint Templates Page 1 Powerpoint Templates Project Angels Martin L. Harbolt PMP, CSM.
Non-Tenure Track (NTT) Appointment Process (Preparer Edition) Version 1.0 Presented by the Office of Organizational Research and Data Management School.
ITIL: Service Transition
IT Development Initiative: Status and Next Steps
Project Charter General Information Project Title Date
ITIL: Why Your IT Organization Should Care Service Support
ITIL: Why Your IT Organization Should Care Service Support
ITIL: Why Your IT Organization Should Care Service Support
Presentation transcript:

RETURN TO MAIN Implementing a Change Control Procedure Within Your Firm Presented by: TOBI M. HALL SYSTEMS OPERATIONS MANAGER SHOOK, HARDY & BACON L.L.P.

RETURN TO MAIN FORMAT WHY? Why do I want to have a change control system? HOW? How do I set it up and how is it managed?

RETURN TO MAIN WHY Provides a consistent process for implementing changes that impact your user community Fulfills requirements from your clients Provides tracking of all system changes Promotes communication between departments

RETURN TO MAIN HOW Develop a process that works both for your system owners and your user community Get buy in from middle and executive management Define in writing the Terms, Roles and Procedures

RETURN TO MAIN TERMS System Change Any alteration to firm-managed information technology hardware, software or operating system configurations, and any alteration in standards for desktop hardware, software or image configuration.

RETURN TO MAIN TERMS Planned System Change A system change that does not resolve a system outage condition. Emergency System Change A system change that restores an inoperative system to working order.

RETURN TO MAIN TERMS Change Request Status Change requests are categorized by status. A change request may assigned one of seven potential statuses Denied – The change is not acceptable. Pending approval – The change request has been prepared for the change management team and is awaiting approval. Approved – The change request has been approved by the change management team. The change is scheduled to occur within a specific time frame. Completed – The change has been successfully implemented. Overdue – The change has missed its scheduled implementation date. The change request must be resubmitted before the change may be implemented. Resubmitted for approval – The change was previously approved, but required a schedule or scope change. This change status acts as a pending approval change until the change management team grants approval. Emergency – This change took place to resolve an outage situation. This type of change acts as a pending approval change until the change management team grants approval.

RETURN TO MAIN ROLES System Change Owner Person accountable for overseeing a system change request Change Management Team Group of supervisors and managers who are responsible for approving or denying a system change request. Help Desk Responsible for notification to the user community of any changes that may impact their day-to-day work.

RETURN TO MAIN PROCEDURE

RETURN TO MAIN PROCEDURE

RETURN TO MAIN OPEN DISCUSSION QUESTIONS????