1 / 11

Implementing a Change Control Procedure Within Your Firm

Implementing a Change Control Procedure Within Your Firm. Presented by: TOBI M. HALL SYSTEMS OPERATIONS MANAGER SHOOK, HARDY & BACON L.L.P. FORMAT. WHY? Why do I want to have a change control system? HOW? How do I set it up and how is it managed?. WHY.

varden
Download Presentation

Implementing a Change Control Procedure Within Your Firm

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. FORMAT • WHY? Why do I want to have a change control system? • HOW? How do I set it up and how is it managed?

  3. 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

  4. 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

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. PROCEDURE

  10. PROCEDURE

  11. OPEN DISCUSSION QUESTIONS????

More Related