<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.itskeptic.org"  xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
 <title>The IT Skeptic - problem</title>
 <link>http://www.itskeptic.org/taxonomy/term/157/0</link>
 <description></description>
 <language>en</language>
<item>
 <title>ITSM incident and problem: two names for three things </title>
 <link>http://www.itskeptic.org/content/itsm-incident-and-problem-two-names-three-things</link>
 <description>&lt;p&gt;Debate around &lt;a h ref=&quot;http://www.itskeptic.org/taxonomy/term/184&quot;&gt;the definitions of Incident&lt;/a&gt; and Problem never seems to end.&lt;br /&gt;
Here&#039;s my take on the fundamental issue that fuels the endless arguments: we have two entities trying to do three jobs.&lt;/p&gt;
&lt;p&gt;When a service breaks, we have to deal with three things in support:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/content/itsm-incident-and-problem-two-names-three-things&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/content/itsm-incident-and-problem-two-names-three-things#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/2374</wfw:commentRss>
 <pubDate>Fri, 25 Jul 2014 10:59:19 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">2374 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Measuring problem management</title>
 <link>http://www.itskeptic.org/content/measuring-problem-management</link>
 <description>&lt;p&gt;How best to measure your Problem Management practice?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/content/measuring-problem-management&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/content/measuring-problem-management#comments</comments>
 <category domain="http://www.itskeptic.org/topic/measurement">measurement</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/2347</wfw:commentRss>
 <pubDate>Sat, 01 Feb 2014 01:07:33 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">2347 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>ITSM in Cherry Valley</title>
 <link>http://www.itskeptic.org/content/itsm-cherry-valley</link>
 <description>&lt;p&gt;I&#039;m getting lots of positive feedback about &lt;a href=&quot;http://www.theitsmreview.com/author/robengland/&quot; target=&quot;_blank&quot;&gt;my series of articles for The ITSM Review&lt;/a&gt;, which use a train crash in Cherry Valley, Illinois as a case study for understanding incident and problem management.  (It is part of a wider theme of my articles for The ITSM Review using railroad examples for service management).&lt;/p&gt;
&lt;p&gt;It always mystifies me that people (and ITIL) don&#039;t grok this simple model: incident management is about users, problem management is about causes.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/content/itsm-cherry-valley&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/content/itsm-cherry-valley#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/118">ITSM</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/2238</wfw:commentRss>
 <pubDate>Sun, 17 Feb 2013 16:51:30 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">2238 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>How ITIL gets Incident vs Problem wrong</title>
 <link>http://www.itskeptic.org/content/how-itil-gets-incident-vs-problem-wrong</link>
 <description>&lt;p&gt;In ITIL, we don&#039;t separate Incidents from Problems properly.  This causes a muddy and confused definition of both.  Join me as I try one more time to make this clear.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/content/how-itil-gets-incident-vs-problem-wrong&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/content/how-itil-gets-incident-vs-problem-wrong#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/topic/itil">ITIL</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/2167</wfw:commentRss>
 <pubDate>Mon, 06 Aug 2012 20:08:26 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">2167 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Riddle me this: matching ITIL theory to the real world</title>
 <link>http://www.itskeptic.org/riddle-me-matching-itil-theory-real-world</link>
 <description>&lt;p&gt;Calling all you ITIL theorists, philosophers, pontificators and pundits.  Marty is back: our follower from the real world, trying to make sense of ITIL on its home grounds, the operations of big iron batch computing.  Marty asks what happens after a service is restored? What does ITIL call the function of undoing the damage done while a service was unavailable?  I have a view - of course - but I&#039;m going to stay quiet - for a while- and hear what everyone else thinks.  So have at it.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/riddle-me-matching-itil-theory-real-world&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/riddle-me-matching-itil-theory-real-world#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/topic/itil">ITIL</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/2081</wfw:commentRss>
 <pubDate>Fri, 21 Oct 2011 19:53:12 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">2081 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>ITIL Problem versus Risk</title>
 <link>http://www.itskeptic.org/itil-problem-versus-risk</link>
 <description>&lt;p&gt;It was one of the great ITSM philosophers, Jan van Bon who first explained to me that Problem Management is but a special case of Risk Management.&lt;/p&gt;
&lt;p&gt;In a purist theoretical sense he is right, but on a practical level I think the distinction is useful.  It is certainly entrenched.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/itil-problem-versus-risk&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/itil-problem-versus-risk#comments</comments>
 <category domain="http://www.itskeptic.org/topic/itil">ITIL</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/146">risk</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/1307</wfw:commentRss>
 <pubDate>Wed, 23 Mar 2011 08:44:45 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">1307 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Problem detection is everyone&#039;s duty</title>
 <link>http://www.itskeptic.org/problem-detection-everyones-duty</link>
 <description>&lt;p&gt;When a train rolls by, the guys on shovels and brooms, track gangs, crews on the ground, crews on other trains, clerks, station-masters, everyone stops and watches the train and waves to the crew on board.  Lazy?  Hell no.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/problem-detection-everyones-duty&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/problem-detection-everyones-duty#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/1621</wfw:commentRss>
 <pubDate>Mon, 26 Apr 2010 08:27:43 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">1621 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Shit happens, or how I learned to love the incident</title>
 <link>http://www.itskeptic.org/shit-happens-or-how-i-learned-love-incident</link>
 <description>&lt;p&gt;Complex systems are by definition broken.  They will always break and sometimes they will break when everybody did what they are supposed to.  Fixing the problem won&#039;t necessarily reduce the risk of another incident.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/shit-happens-or-how-i-learned-love-incident&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/shit-happens-or-how-i-learned-love-incident#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/1799</wfw:commentRss>
 <pubDate>Mon, 08 Feb 2010 09:43:04 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">1799 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>We should create the problem record right up front in an incident</title>
 <link>http://www.itskeptic.org/we-should-create-problem-record-right-front-incide</link>
 <description>&lt;p&gt;A &lt;a href=&quot;http://www.itskeptic.org/bokked&quot; target=&quot;_blank&quot;&gt;BOKKED&lt;/a&gt; post three months ago drew a lot of attention.  It was about the &lt;a href=&quot;http://www.itskeptic.org/itil-v3-service-operation-disconnect-between-incid&quot; target=&quot;-blank&quot;&gt;disconnect between Incident and Problem Management&lt;/a&gt; in ITIL V3 Service Operation.  [See also the ITIL Wizard &lt;a href=&quot;http://www.itskeptic.org/should-every-major-incident-produce-problem-record&quot;&gt;stirring the pot about Major Incidents&lt;/a&gt;]  I&#039;ve just discovered a response to that post which has popped my brain with its simplicity and clarity&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/we-should-create-problem-record-right-front-incide&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/we-should-create-problem-record-right-front-incide#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/topic/itil">ITIL</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/1779</wfw:commentRss>
 <pubDate>Mon, 28 Dec 2009 08:55:02 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">1779 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>ITIL V3 Service Operation disconnect between Incident and Problem Management</title>
 <link>http://www.itskeptic.org/itil-v3-service-operation-disconnect-between-incid</link>
 <description>&lt;p&gt;There seems to be a major disconnect between ITIL V3 Incident and Problem Management.  &lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/itil-v3-service-operation-disconnect-between-incid&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/itil-v3-service-operation-disconnect-between-incid#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/68">Service Operation</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/78">Inconsistent within book</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/topic/itil">ITIL</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/61">V3</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/1620</wfw:commentRss>
 <pubDate>Mon, 07 Sep 2009 08:40:26 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">1620 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Say it ain&#039;t so!! ITIL V3 Incident and Problem processes do not determine the affected service</title>
 <link>http://www.itskeptic.org/say-it-aint-so-itil-v3-incident-and-problem-proces</link>
 <description>&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/so-42-incident-management-process-never-determines&quot;&gt;This BOKKE&lt;/a&gt; (body of knowledge known error) has been posted for a day or so, hundreds of views.   I was sure someone would say &quot;no you idiot, service impact analysis is right here&quot; but not one.  It seems to be true.  &lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/say-it-aint-so-itil-v3-incident-and-problem-proces&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/say-it-aint-so-itil-v3-incident-and-problem-proces#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/topic/itil">ITIL</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/186">service</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/61">V3</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/1592</wfw:commentRss>
 <pubDate>Wed, 12 Aug 2009 03:15:17 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">1592 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Incidents overwhelm problems</title>
 <link>http://www.itskeptic.org/incidents-overwhelm-problems</link>
 <description>&lt;p&gt;Problems suffer from the important/urgent dilemma.  They are very important but struggle to get attention &lt;strong&gt;in the less mature shops&lt;/strong&gt; over the incoming bombardment of incidents.&lt;/p&gt;
&lt;p&gt;This is over simplistic but cute&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/incidents-overwhelm-problems&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/incidents-overwhelm-problems#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/184">incident</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/158">Realitsm</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/1323</wfw:commentRss>
 <pubDate>Sun, 01 Mar 2009 21:49:51 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">1323 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Defining terms in Root Cause Analysis - let&#039;s be clear what we mean</title>
 <link>http://www.itskeptic.org/node/708</link>
 <description>&lt;p&gt;We have &lt;a href=&quot;http://www.itskeptic.org/node/707&quot;&gt;a great discussion going&lt;/a&gt; regarding Root Cause.  As usual so much comes down to precise definition of terms.  What does Root Cause mean?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/node/708&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/node/708#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/285">root cause</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/708</wfw:commentRss>
 <pubDate>Sun, 27 Jul 2008 22:35:12 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">708 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Root Cause Analysis can&#039;t be done by machines</title>
 <link>http://www.itskeptic.org/node/707</link>
 <description>&lt;p&gt;Vendors are making a fuss about their Root Cause Analysis (RCA) features in their tools.  People Process Things once again: who says Root Cause is in the technology?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.itskeptic.org/node/707&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.itskeptic.org/node/707#comments</comments>
 <category domain="http://www.itskeptic.org/taxonomy/term/157">problem</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/285">root cause</category>
 <category domain="http://www.itskeptic.org/taxonomy/term/147">technology</category>
 <wfw:commentRss>http://www.itskeptic.org/crss/node/707</wfw:commentRss>
 <pubDate>Sat, 26 Jul 2008 03:51:27 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">707 at http://www.itskeptic.org</guid>
</item>
</channel>
</rss>
