Home » Incident & Problem Management: What you need! » Recent Articles:

Incident & Problem Management Process – What You Need!

You must have both INCIDENT MANAGEMENT and PROBLEM MANAGEMENT if you want to reduce the cost of Incidents and their impact on the business..

  1.  Incident Management and Problem Management must be integrated.
  2.  Problem  Management
    1. Allows you to actively reduce the occurrence of Incidents.
  3.  Incident Management
    1. Identifies and captures incident data, quantifies business impact and cost
    2. Is the foundation for Problem Management (Data collected during Incident Management enables effective Problem Management.)   >>>Incident Management Tool 
    3.  Allows you to actively reduce the effort that is spent on Incidents.
      1. Lessons-Learned
      2. Consistent Processes
      3. Cross-Training
      4. Knowledge-base of well-documented resolutions
    4. For effective Incident Management, you also must have Service Level Agreements.
      1. Develop service goals for response and resolution completion
      2. Develop service goals for reducing the number and severity of incidents Continue reading “Incident & Problem Management Process – What You Need!” »

Our Sponsors

IT Support Services Comments

  • Connor: Absolutely agree with alosmt everything you wrote. And about time there was a voice of dissent as I’ve been alone in the wilderness for too long! ITIL v2 was pretty good as a framework but then ...
  • pudin: Spot on. ITIL is a load of old Tripe. ITIL is a fwremaork but it is common sense. We have stopped all ITIL training.Peer to Peer learning and focus groups have delivered better and more measurable ...
  • Woo: Stopping in for a quick hi to Mary and Lesli. Great intirveew! I didn't even know we're supposed to count our WIPs. Guess I need to pull out the ol' file.Kudos to the parents/grandparen...
  • Bob Anderson: Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the ...
  • Bob Anderson: Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Compute...

ITIL V3 Application Support Q & A

If you have any question on the blog content or have some specific question on how ITSM & ITIL can dramatically improve performance and reduce the cost of your Application Support service "Ask Bob"
Question :
Answer :
Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Computer World on "How to create Meaningful IT Support SLA's"  use this link...
Question :
Answer :
Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the folks who developed the original CMM  were not really initially inter...
Question :
Answer :
Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you want to be "proactive" in stopping this practice" you must capture bu...
Question :
Answer :
Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, and how many technical support calls from users you get and the average...
Question :
Answer :
Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on their own without any instruction to do so and it affects other user...