Problem Management SDG teamIT Problem Management Process 2009 Client Services Authors: M. Begley & R. Crompton, Client Services.

Slides:



Advertisements
Similar presentations
SERVICE MANAGER 9.2 PROBLEM MANAGEMENT TRAINING JUNE 2011.
Advertisements

[Organisation’s Title] Environmental Management System
Child Safeguarding Standards
A A A N C N U I N F O R M A T I O N T E C H N O L O G Y : IT OPERATIONS 1 Problem Management Jim Heronime, Manager, ITSM Program Tanya Friehauf-Dungca,
Supporting people with a learning disability Introduction to Project Management Presenter: Steve Raw FInstLM, FCMI.
Corrective & Preventive Action Programme l Corrective and preventive action managed by one programme l Closely linked to the internal audit programme l.
Root Cause Analysis Procedure (IMSP525) Training
Best Practices – Overview
10.5 Report Performance The process of collecting and distributing performance information, including status reports, progress measurements and forecasts.
Management Responsibility Procedure Tutorial. Introduction to Management Responsibility In this presentation we will discuss how to write a procedure.
1 Change Management FOR University Medical Group Saint Louis University Click this icon for Audio.
OHSAS 18001: Occupational health and safety management systems - Specification Karen Lawrence.
Problem Management Overview
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 12 Integration Management Practising a common, coordinated.
ASPEC Internal Auditor Training Version
Project Planning Day 2 An Old Adage: Fail to Plan... and You Plan to Fail!
Planning. SDLC Planning Analysis Design Implementation.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
Quality Representative Training Version
The Business Continuity Plan Chris Owens/Annette Mercer Public Health Knowsley MBC Local Pharmaceutical Committee 18 June 2014.
RST processes Session 6 Presentation 3. A framework for RST processes Establishing an RST Membership Terms of reference Work programme (schedule, agenda,
Change Advisory Board COIN v1.ppt Change Advisory Board ITIL COIN June 20, 2007.
Effectively applying ISO9001:2000 clauses 5 and 8
What is Business Analysis Planning & Monitoring?
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
COMPGZ07 Project Management Presentations Graham Collins, UCL
What if you suspect a security incident or software vulnerability? What if you suspect a security incident at your site? DON’T PANIC Immediately inform:
INFSO-RI Enabling Grids for E-sciencE Incident Response Policies and Procedures Carlos Fuentes
[Facility Name] [Presenter Name] [Date]. Objectives 2 After this session, you will be able to 1. describe Root Cause Analysis (RCA) and Plan-Do-Study-Act.
Information Services, Griffith University Problem Management Implementation Service Desk Project Phase 2 Project
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
NCSX Management Overview Hutch Neilson, NCSX Project Manager NCSX Conceptual Design Review Princeton, NJ May 23, 2002.
What if you suspect a security incident or software vulnerability? What if you suspect a security incident at your site? DON’T PANIC Immediately inform:
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.
Monitor & Control Risks 1 MEC-4. What is Monitoring & Controlling Risks? 2 » Monitoring & Controlling Risks is the process of: implementing Risk Response.
Hazards Identification and Risk Assessment
ISO NON-CONFORMANCE, CORRECTIVE AND PREVENTIVE ACTION.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Introducing Project Management Update December 2011.
(Project) RISK MANAGEMENT PROCESS SEPTEMBER 5, 2008.
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Monitor & Control Risks 1 MEC-4. What is Monitoring & Controlling Risks? 2 » Monitoring & Controlling Risks is the process of: implementing Risk Response.
1 City of Shelby Wastewater Treatment Division Becomes State’s Second Public Agency to Implement a Certified Environmental Management System CERTIFICATION.
Report Performance Monitor & Control Risk Administer Procurement MONITORING & CONTROLLING PROCESS.
ITIL Project Change Management Workshop 7 February 2007
A Quick Overview of ITIL
TechStambha PMP Certification Training
[Project Name] Post-Mortem
PROJECT NAME POST-MORTEM
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Mastering Change Control
Guidance notes for Project Manager
Market Trials Working Group
RST processes Session 5 Presentation 2.
Pre-Concept Approval Forum – a guide v1.0
Week Ten – IT Audit Reporting
[Project Name] Post-Mortem Presentation Template
Project Name Post-Mortem
How to conduct Effective Stage-1 Audit
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
Speaker’s Name, SAP Month 00, 2018
Business Planning Meeting Periodic Business Review
Marketing Planning Meeting Periodic Marketing Review
Presentation transcript:

Problem Management SDG teamIT Problem Management Process 2009 Client Services Authors: M. Begley & R. Crompton, Client Services

Problem Management Process SDG Problem Management Process Goals of Problem Management Minimise the frequency and impact of IT problems on the business Initiate actions to correct each situation Find the root cause of Incidents Prevent the recurrence of Incidents Both reactive and proactive

Problem Management Process SDG Problem Management Process Incident Management Problem Management Identifying Root Cause Preventing Re-occurrence Pro-active prevention of incidents Restoring service as quickly as possible Difference between Incident & Problem Management

Problem Management Process Severity 1, 2 & 3 Incidents (Major Incidents) Raising a Problem Record Service Improvement Plan/ Re-occurring Incident/Problem identified by IT or Business

Problem Management Process Ongoing Management of Problems The Problem Owner (CSM or PSM) is responsible for the following: Ensuring the Problem Record on Assyst is Updated. The Problem record has an accurate ‘Update Due Date’. All relevant Support Teams are aware of the Problem Priority. The Problem is fully progressed until Closure, including when closure criteria has been met. TRACS codes are created and closed as and when required. Chairing meetings (including Post Incident Reviews), assigning actions and ensuring actions are completed.

Problem Management Process Post Incident Review The purpose of the Post-Incident Review is to: Learn from recent events in a deliberate effort to improve future performance. Review and Evaluate strategic, tactical, and task-level operations/decisions made during any incident Understand & Document quality improvements to be made When should a Post Incident Review be Held? Whenever Requested by any member of Shop Direct Group Inputs (Documents): Timeline of Events (Incident Log) Any current written procedures Agenda Mandatory Attendees: CSM for affected area (Chair) Duty Manager Technical Services Rep Shift Manager Production Support Manager Service Desk Management Output: A Report with appropriate actions, distributed to teamIT Management, should be sent out that covers: What we will keep doing? What will we stop doing? What will we start doing? The actions should be managed through to completion using Problem Management

Problem Management Process A Problem should only be closed when the following has been established: Closing Problems An explanation of the cause, symptoms and impact of the problem. There is a tactical fix used to resume service. Details of a more strategic fix or change to stop this happening again. High level resource estimates and/or capital expenditure for the strategic fix/change. An idea of suitable timescales to implement.

Problem Management Process Risk Register The purpose of the Risk Register is to: clearly identify risks and measures being taken to mitigate or reduce them What the Risk Register is NOT there to do: its not about putting risks in a register and forgetting about them; its about identifying and managing those risks, particularly those that present the biggest challenge in management terms What is on the Risk Register? Any risk that has been identified by SDG, including mitigation, potential impact, sign off details and when the risk will next be reviewed When is it updated? The Risk Register is updated Monthly or whenever a new risk is identified Where can it be found? On the teamIT Intranet or contact the Client Services Team

Problem Management Process Schedules Daily High Severity Problems are tracked in the Daily Service Review (DSR) Weekly Weekly Updates, detailing Problems that are overdue an update and Problems that require updating in the next 7 days, are sent to the Client Services Team on Fridays Monthly The Client Services Team meet on a Monthly basis to discuss every open Problem, detailing progress, priorities and any resource problems Monthly Meetings are held between the Client Services Team Manager and Problem Lead Client Services Manager to discuss Open & Closed Problems. Governance

Problem Management Process IT Daily Service Review Minutes Monthly Problem Report presented to: Infrastructure Board IT Management IT Services Management Business Service Reviews held by Client Service Managers Daily Operations Call Management Information