Friday 11 July 2008

Declaring an IT Safety service function

I proceed on my merry way reviewing the problem management section in MOF! Table 1, Support Accountability and Its Attendant Role Types, is actually a very good table.
It actually states correctly that there might be multiple root causes to a problem. I wonder if this was premeditated as immediately above this table it states wrongly that a problem has a singular root cause.
The table clearly has a delegation of roles between dealing with incidents and problems. This is good as incidents have to be resolved as quickly as possible, while with problems it is not possible to give time periods. Incidents are solved on deadlines, problems are not.
Interesting enough, MOF groups incident management and problem management together into a problem management service function. ITIL always distinguishes between the two separately, but this consolidation makes sense as long as people don’t become confused and use the terms incident and problem interchangeably. The confusion between the terms is a major process flaw in many companies. For this reason, it is my opinion that this service function has been incorrectly named. Instead of the problem management function it should be called the IT Safety service function.
I work in IT Safety. I like the sound of that!

2 comments:

  1. IT Safety. LMFAO :-D

    Wait til you see Introduction to Real ITSM!

    ReplyDelete
  2. Thanks for visiting these humble pages, skep. We don't have many visitors in this obscure neck of the Kalahari.
    As my friend Timon would say, you can never be safe enough, a lesson you learn pretty quickly when encountering an unexpected Cobra in your bolt hole.

    ReplyDelete